Making a RAS Call by Using RIL

  • Article

A version of this page is also available for

Windows Embedded CE 6.0 R3

4/8/2010

To use RIL when making a RAS call, the cellular TSP and the RIL driver complete the following steps:

  1. TAPI calls the RIL_SetBearerServiceOptions function with a pointer to RILBEARERSVCINFO structure to set the bearer service options according to the RASDEVINFO structure. The following list shows the typical values for RILBEARERSVCINFO:

    • RIL_SPEED_9600_V32
    • RIL_BSVCNAME_DATACIRCUIT_ASYNC_UDI_MODEM
    • RIL_BSVCCE_NONTRANSPARENT

    The return value should be RIL_RESULT_OK.

  2. TAPI then calls RIL_Dial with the parameters set to "T14255551212", RIL_CALLTYPE_DATA, and RIL_DIALOPT_NONE.

  3. The RIL driver generates a RIL_NOTIFY_DATASVCNEGOTIATED notification with lpData pointing to a RILSERVICEINFO structure set to asynchronous non-transparent. At this point, the system ignores this notification.

  4. The RIL driver generates a RIL_NOTIFY_CONNECT notification with lpData pointing to a RILCONNECTINFO structure with the dwCallType member set to RIL_CALLTYPE_DATA and the dwBaudRate member set to 9600 (or the actual rate of connection).

  5. The driver returns RIL_RESULT_OK for the dial command with lpData = NULL.

  6. RAS opens the data port and starts the Point-to-Point Protocol (PPP) negotiation.

  7. TAPI calls RIL_GetCallList to verify that the call is active. This step may occur multiple times. The return value should be RIL_RESULT_OK with lpData pointing a RILCALLINFO structure with the following values.

    Member Value

    dwID

    1

    dwDirection

    RIL_CALLDIR_OUTGOING

    dwStatus

    RIL_CALLSTAT_ACTIVE

    dwType

    RIL_CALLTYPE_DATA

    dwMultiparty

    RIL_CALL_SINGLEPARTY

    raAddress

    "14255551212"

Requirements

Windows Embedded CE Windows Embedded CE 6.0 and later

See Also

Other Resources

RIL Call Overview