Architecture

This section provides the architectural relationship between the packet data telephony classes.

Packet data telephony provides additional interface to the basic telephony interfaces. The Packet data API takes the client requests and passes the request to the telephony server. The server passes the request to the telephony device driver the .TSY module. The TSY module manages the communications with the telephony hardware.

Description

The packet telephony classes are R classes. The R classes communicate with the telephony server. All the R classes are derived from RTelSubSessionBase. RTelSubSessionBase manages a sub-session to the telephony server.

The following section outlines the packet telephony classes:

  • RPacketContext defines the context of a connection to the packet switched service. The client applications can configure, change and activate a context. A context is the configuration for a packet switched connection.

    For more information, see Packet Context.

  • RPacketService enables the client applications to control a packet switched connection. The client applications can attach and remove the phone to the packet network. The client applications can also get the packet network capabilities.

    For more information, see Packet Service.

  • RPacketQoS encapsulates the functions to configure QoS options for a particular context.

    For more information, see Packet Quality of Service.

The packet networks offered access to are:

  • GPRS Release 97/98

  • CDMA and CDMA2000

  • GPRS/UMTS Release 99 and UMTS Release 4