|
|
Functions |
| TapiResult_t | TelTapiCallSetup (const TelCallSetupParams_t *pParams, unsigned int *pCallHandle, int *pRequestId) |
| | This function originates MO call setup. This is an asynchronous function. The function completes immediately and call setup proceeds in background.
|
Function Documentation
This function originates MO call setup. This is an asynchronous function. The function completes immediately and call setup proceeds in background.
- Sync (or) Async:
- This is an Asynchronous API.
- Important Notes:
- If call to TelTapiCallSetup() is successful, call handle and request ID are assigned by Telephony Server and returned to client by given Call Handle and Request Id parameters. MO call setup continues in background. There are multiple states involved in the call setup procedure. Upon request completion successful or not, various event notifications are sent to client along with data associated with event (Successful data or error information) based on the indication or response received at the Telephony Server.
- Setting up Emergency call
- when TelCallType_t is voice_call, voice call is setup unless dial_number parameter is an emergency number known to telephony FW (like 112 for all 2G and above, other numbers may operator specific or device configuration specific, so Telephony FW will read relevant SIM files and refer to internal configuration records). If an emergency number is passed and TelCallType_t is voice_call, Telephony FW shall setup emergency phone call.
- When TelCallType_t is emergency call, emergency call is always set up.
- Warning:
-
- Parameters:
-
| [in] | pParams |
- TelCallSetupParams_t contains the necessary parameters like supplementary information, the type of the call (whether it is a voice call or data call etc), identity mode option (Identity to be shown or hidden etc) and the Closed User Group (CUG) information for setting up the call.
|
| [out] | pCallHandle |
- Unique handle for referring the call
|
| [out] | pRequestId |
- Unique identifier for a particular request.
- Request Id value can be any value from 0 to 255 if the API is returned successfully
- -1 (INVALID_REQUEST_ID) will be sent in case of failure.
|
- Async Response Message:
- TAPI_EVENT_CALL_SETUP_CNF is sent to the application when the lower layers get the call originate response. Asynchronous return status is indicated by TelCallCause_t and call handle is sent in the event data.
- Pre Conditions:
-
- Post Conditions:
-
- Returns:
- Return Type (TapiResult_t)
- TAPI_API_SUCCESS - indicating that the operation has completed successfully.
- Else it will return failure and error code (Refer TapiResult_t)
- Prospective Clients:
- External Apps.
Generated on Mon Mar 31 01:01:00 2008 by
1.5.4
|