Default constructor, and is present only to support virtual function table export. This member is internal and not intended use.

Activates a CCBS request on a call that has failed due to remote user busy It will complete once the activate request has been confirmed by the network

Specifies which User-To-User Signalling service(s) the phone should request to activate.

This function member can be used before a call has started or during a call (for UUS3 only).

In order to use UUS the calling subscriber must have the UUS supplementary service provisioned by the network provider and the network must have the capability of supporting the UUS service.

Use of this function member is only applicable to a phone whose UUS caps (TMobileCallUUSCaps) are set to support the required UUS service. The KCapsSetupUUS1Implicit flag allows the calling user to activate the UUS service implicitly by sending the UUI embedded within the call set-up message. The UUS Service 1 can also be activated explicitly. The UUS Services 2 and 3 can only be activated by means of an explicit request. Service 2 can only be activated when initiating an outgoing call, whereas Service 3 can also be activated during the call.

If UUS Service 1 is being requested, then the iUUI field of TMobileCallUUSRequestV1 will contain any UUI data to send with the call set-up message.

If the call has not started yet, the TSY is expected to save the request information until it receives the next Dial request. In this case ActivateUUS should complete with KErrNone if the TSY supports the requested UUS or KErrNotSupported if the TSY can not fulfill the request for the next Dial. Once the Dial request is received, the phone will send the SETUP request to the network and include the UUS service activation request. A number of outcomes are possible once the phone has sent the SETUP message.

If the network does not support UUS or the caller is not subscribed to UUS and the service is mandatory for the call, the network will send a DISCONNECT or RELEASE message. The Dial request will complete with the error received from the network. (KErrGsmCCResourceNotAvailable or KErrGsmCCRequestedFacilityNotSubscribed).

If the network does not support UUS but the service is not mandatory, the network will still proceed with the call but without UUI, and the Dial request will complete with KErrNone when the call is connected.

If the network does support UUS then the remote user will be alerted to the UUS service activation.

If the remote user accepts the UUS service activation, the network will proceed with the call and the Dial request will complete with KErrNone when the call is connected.

If the remote user rejects the UUS service activation and the service is mandatory for the call, the network will send a DISCONNECT or RELEASE message and the Dial request will complete with the error received from the network (KErrGsmCCFacilityRejected).

If the remote user rejects the UUS service activation and the service is not mandatory, the network will still proceed with the call and the Dial request will complete with KErrNone when the call is connected.

Once the call is connected, clients can check the call's UUS capabilities to see which UUS services are active.

If this function member is used to activate the UUS Service 3 during a call then the connection with the remote side has already been established. In order to use this function member during the call the activating subscriber must have the UUS supplementary service 3 provisioned by the network provider and the network must have the capability of supporting the UUS service 3. Once the ActivateUUS() request is posted, the phone will send the FACILITY request to the network and include the UUS service activation request. A number of outcomes are possible once the phone has sent the FACILITY message.

If the network does not support UUS the call will remain connected but no UUI transmission is possible and the ActivateUUS() request will complete with the error returned by the network (KErrGsmCCResourceNotAvailable or KErrGsmCCRequestedFacilityNotSubscribed).

If the network does support UUS then the remote user will be alerted to the UUS service activation

If the remote user accepts the UUS service activation, the ActivateUUS() request will complete with KErrNone and then UUI can be transferred.

If the remote user rejects the UUS service activation, the ActivateUUS() request will complete with the error returned by the network (KErrGsmCCFacilityRejected) and no UUI can be transferred.

Use: RTelSubSessionBase::CancelAsyncRequest(EMobileCallActivateUUS) to cancel a previously placed asynchronous ActivateUUS() request.

Waits for an incoming call and answers it when it arrives - asynchronous. The function also answers calls which are ringing when it is invoked.

This method is intended to be used by the EtelISV API

Enables the client to answer an incoming call and send UUI to the calling party at the same time.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallAnswerWithUUI) to cancel a previously placed asynchronous AnswerIncomingCallWIthUUI() request.

Rejects an incoming multimedia call, but offers fallback to voice. The aCallParams is now the alternative TMobileCallParamsV1 , because the call is no longer data. The aCallName is now the name of the new voice call created to handle the fallback to voice.

This name is used then by the client to open the voice call by name. The TSY returns the name of the new voice call object in aName parameter for the Client to open.

Allows a client to deflect an incoming call that is still in the EStatusRinging state.

The destination of the deflected call is determined by the aDeflectType parameter. If this parameter equals EDeflectSuppliedNumber then the destination address is given in the aDestination parameter. If call deflection is possible then it will be reflected in that call's dynamic capabilities, i.e. the KCapsDeflect bit of TMobileCallControlCaps will be set.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallDeflect) to cancel a previously placed asynchronous Deflect() request.

Dial the number specified in aTelNumber using the call parameters specified in aCallParams. This API differs from the standard RCall::Dial method to allow the TSY to know that the dial request is resulting from Call Control.

When a client wishes to dial a call (using one of the other dial APIs such as RCall::Dial ) and Call Control is being used, the dial request is passed to the Call Control which can then modify the call parameters originally specified by the client. The SAT engine then issues a second dial request to make the actual call using the new modified parameters. When making this second request, this API should be used to indicate to the TSY that this call results from Call Control. Call parameter classes RMobileCall::TMobileCallParamsV7 and RMobileCall::TMobileHscsdCallParamsV2 (and in future one of their derived classes) allow the call originator to be specified.

The API RMobileCall::GetMobileCallInfo with RMobileCall::TMobileCallInfoV7 also allows a client to get information regarding the originator of a call.

Error codes returned by this API from the TSY/Etelmm via aStatus are:

This API is policed by both Platform Security capabilities and SID and can only be called by the SAT engine.

On hardware, the API can be called by providing the SID of the SAT engine in ETel.iby file found in A patchable constant KSatEngineSid is used for defining the SID value of the SAT engine.

For example, add the following line to ETel.iby: patchdata etel.dll 0x12345678

On emulator, the API can be called by providing the SID of the SAT engine in epoc.ini file found at

To do this, add the following line to .ini etel_KSatEngineSid <SID>

For example: etel_KSatEngineSid 0x12345678

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallDialCallControl) to cancel a previously placed asynchronous DialCallControl() request.

Places an emergency call request.

It is advised that the client opens a call object during system initialization and reserves it for an emergency call. This will guarantee that it will not leave with a KErrOutOfMemory, which could happen if the client had to open a new call to make the emergency call.

The TSY should make sure that any needed resource for an emergency call is created at initialization and set aside in the event of a DialEmergencyCall() request. Upon receiving a DialEmergencyCall() request, the TSY should ask the ETel server if the client is a priority client, using the following call to the server: CCallBase::CheckPriorityClient().

DialEmergencyCall is designated a "priority client" request, which means that if a client that is known to the server as a priority client calls this, the server will guarantee that it will not leave with KErrOutOfMemory. However, a non-priority client may call it without this guarantee.

This function member is similar to the standard Dial() function member in that it will initiate a call set-up. The emergency call object will follow the standard call states.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallDialEmergencyCall) to cancel a previously placed asynchronous DialEmergencyCall() request.

Attempts to establish a connection using the telephone number specified. This is an asynchronous method and is intended for use by the EtelISV API

The mode of the connection, i.e. whether it is a data or fax connection, is determined by whether the RCall object has been opened from a data line or a fax line.

This method is similar to RCall::Dial() , with two exceptions. Functionally, RMobileCall::DialISV() is given lower capabilities than RCall::Dial() 's NetworkServices + NetworkControl. The second difference is up to the TSY developer; a TSY may chose to distinguish between a CTelephony (i.e. ETel3rdParty) RMobileCall::DialISV() and an RCall::Dial() originated dial request. Although it would also be correct for a TSY to treat the two in the same way; the choice is left to the TSY writer and the use cases they can envisage.

Giving this method a lower PlatSec capability requirement means that it is more easily accessible to the third party developers. Also, RCall::Dial() is intended for use by the Phone Application alone, thus, the higher RCall capability settings may also provide it with some form of protection. Thus, this can be viewed as an attempt to restrict RCall::Dial() to the Phone Application.

The two different forms of dialling should be seen as a way of filtering the more important calls, requested by the high priority Phone Application/UI, from those requested by other applications. The TSY can use this filtering of call requests, perhaps to use different or dedicated channels for each IPC, prioritise one over the other (e.g. in the case of limited channels), etc..

Dials the number specified by aTelNumber.

The number used for dialling is not checked against those in the Fixed Dialling Number list even if the FDN service is enabled. Null CallParams are applied.

Dials the number specified by aTelNumber.

The number used for dialling is not checked against those in the Fixed Dialling Number list even if the FDN service is enabled.

Gets the current values of the HSCSD parameters of an active mobile HSCSD call.

Gets the mobile call's call control and event capabilities.

Gets the current status of a mobile call.

Gets the current data call capabilities. The data capabilities provide clients with knowledge of which data call parameter values they can then set-up or negotiate for this call.

Gets the minimum and maximum RLP parameter ranges supported by the phone for the specified RLP version.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallGetMobileDataCallRLPRange)with to cancel a previously placed asynchronous GetMobileDataCallRLPRange() request.

Gets the current instance of the UUS capabilities of the call. This function member can be used before making the call to find out which UUS the phone supports, or during the call to find out which UUS are active for the current call.

Requests a private communication to the remote party of one call within a conference call. The rest of the conference call will be put on hold while the user and the selected remote party go "one-to-one". It can be called by any client that has a handle on this call (i.e. not necessarily the client that first opened and dialed or answered the call). The action is only valid if the MS is in GSM mode, the selected call is a voice call and it is a member of an ongoing conference call. If "one-to-one" is possible then it will be reflected in that call's dynamic capabilities, i.e. the KCapsOneToOne bit of TMobileCallControlCaps will be set.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallGoOneToOne) to cancel a previously placed asynchronous GoOneToOne() request.

This overloaded RCall::HangUp() function member enables the client to send a UUS1 data at the call release.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallHangupWithUUI) to cancel a previously placed asynchronous HangupWithUUI() request.

Puts a call on hold.

It will complete when the network confirms that the call is in the hold state. It can be called by any client that has a handle on this call (i.e. not necessarily the client that first opened and dialed or answered the call). The action is only valid if the call is a voice call and if there are no other calls already on hold. If call hold is possible then it will be reflected in that call's dynamic capabilities, i.e. the KCapsHold bit of TMobileCallControlCaps will be set.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallHold) to cancel a previously placed asynchronous Hold() request.

This notification completes when an alternating call successfully switches call mode.

Use: RTelSubSessionBase::CancelAsyncRequest(EMobileCallNotifyAlternatingCallSwitch) to cancel a previously placed asynchronous NotifyAlternatingCallSwitch() request.

Notification completes when there has been a change of call control audio tone event.

Allows the client to be notified when various call events occur.

These events may be generated locally (i.e. from within the ME) or remotely (by the remote connected party). The request completes when an event occurs. Upon completion, the aEvent parameter will return the event type.

The call (and line) status will be changed to reflect any events detected locally or remotely.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallNotifyCallEvent) to cancel a previously placed asynchronous NotifyCallEvent() request.

This notification completes when the mobile call's HSCSD parameters change.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallNotifyHscsdInfoChange)to cancel a previously placed asynchronous NotifyHscsdInfoChange() request.

This notification completes when the mobile call's call control and event capabilities change.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallNotifyMobileCallCapsChange) to cancel a previously placed asynchronous NotifyMobileCallCapsChange() request.

Allows a client to be notified when the call changes state.

The request completes when the call changes state, the new state being passed in the aStatus parameter.

Use RTelSubSessionBase::CancelAsyncRequest(TEMobileCallNotifyMobileCallStatusChange) to cancel a previously placed asynchronous NotifyMobileCallStatusChange() request.

Allows clients to be notified of a change in the call's data capabilities.

The data capabilities of a call can change if the phone changes mode before the call moves out of the idle state.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallNotifyMobileDataCallCapsChange) to cancel a previously placed asynchronous NotifyMobileDataCallCapsChange() request.

This notification completes when the network confirms whether privacy is on or off for this call.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallNotifyPrivacyConfirmation) to cancel a previously placed asynchronous NotifyPrivacyConfirmation() request.

Allows the client to be notified of any change in the remote party information.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallNotifyRemotePartyInfoChange) to cancel a previously placed asynchronous NotifyRemotePartyInfoChange() request.

Allows the client to be notified when the CDMA network has confirmed the traffic channel type requested during call set-up or during call connection.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallNotifyTrafficChannelConfirmation) to cancel a previously placed asynchronous NotifyTrafficChannelConfirmation() request.

Notifies the clients of changes to the UUS capabilities of the phone.

The UUS capabilities are most likely to change when the call starts.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallNotifyUUSCapsChange) to cancel a previously placed asynchronous NotifyUUSCapsChange() request.

Notifies the client if a Multimedia call falls back to a voice call due to inability in network or terminating end to comply with the Multimedia request.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallNotifyVoiceFallback) to cancel a previously placed asynchronous NotifyVoiceFallback() request.

Enables the client to receive the next incoming UUI message from the remote user.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallReceiveUUI) to cancel a previously placed asynchronous ReceiveUUI() request.

Allows a client to specify that it does not wish to set-up a CCBS request on a failed call setup.

When the user is presented with the option of activating a CCBS request to a remote busy number, if the user chooses not to bother then this API function member can be used by the client application to inform the TSY of this user decision.

This enables the TSY to inform the network immediately that the CCBS possibility is not going to be used and therefore stop all relevant timers. If the client application calls neither ActivateCCBS() or RejectCCBS() when the call control capability KCapsCCbsActivate is set, the possibility of activating CCBS will eventually time-out and the associated call control capability will disappear.

Resumes a call that is on hold.

It will complete when the network confirms that the call is in the active state. It can be called by any client that has a handle on this call (i.e. not necessarily the client that first opened and dialed or answered the call). This action is only valid if there are no other calls already active. If call resume is possible then it will be reflected in that call's dynamic capabilities, i.e. the KCapsResume bit of TMobileCallControlCaps will be set.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallResume) to cancel a previously placed asynchronous Resume() request.

Sends a UUI message for UUS2 and UUS3 services to the remote user either during the call set-up or during the actual call. The client must supply the message data within the aUUI parameter.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallSendUUI) to cancel a previously placed asynchronous SendUUI() request.

Sets the call's dynamic HSCSD parameters.

This request can be used before call set-up starts or during call connection. If the call is not a HSCSD call then KErrNotSupported is returned.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallSetDynamicHscsdParams) to cancel a previously placed asynchronous SetDynamicHscsdParams() request.

Causes the phone to request a new privacy setting for this call.

This setting will over-ride (for this call only), the phone's default privacy setting.

The function member is synchronous for two reasons. Firstly because the phone may not be able to request the new setting immediately if the call has not started yet. Secondly, the CDMA network only sends confirmation of a successful privacy setting and will not respond if it is unable to service the request. This means a client needs to request a privacy setting but then not assume the setting is active until "notify privacy confirmation" completes.

Sets a new value for the traffic channel setting of a mobile call.

The function member is synchronous for two reasons. Firstly because the phone may not be able to request the new setting immediately if the call has not started yet. Secondly, the CDMA network only sends confirmation of a successful traffic channel allocation and will not respond if it is unable to service the request. This means a client needs to request a traffic channel type but then not assume the channel is allocated until "notify traffic channel confirmation" completes.

Swaps a connected call to its opposite state, either active or on hold.

This function member will complete either when the call has successfully moved to the opposite state or if the action failed due to some reason. It can be called by any client that has a handle on this call (i.e. not necessarily the client that first opened and dialed or answered the call).

This action is possible under two circumstances:

There is just one active or held single call. This implies that there are no other calls already in the state to which the client wishes to move this call to. The client will call Swap on this call and if it is active it will move to the held state and if it is held it will move to the active state.

There are two single calls, one currently active and one on hold. This function member therefore swaps the active call with the held call, simultaneously placing the active call on hold and resuming the held call.

In the first circumstance, an active call's dynamic capabilities will contain the KCapsHold and KCapsSwap bits set. A held calls' dynamic capabilities will contain the KCapsResume and KCapsSwap bits set. In the second circumstance, both the active and held call's dynamic capabilities will contain just the KCapsSwap bit set. The above function member is applicable to both single and conference calls. If there is a single call and a conference call then the client can call Swap on either the single call or the conference call. The action will still move both the single call and the conference call to their opposite states.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallSwap) to cancel a previously placed asynchronous Swap() request.

Switches an alternating call to its opposite call mode.

Use RTelSubSessionBase::CancelAsyncRequest(TEMobileCallSwitchAlternatingCall) to cancel a previously placed asynchronous SwitchAlternatingCall() request.

Allows a client to transfer a call so that the remote party of one call ends up connected to the remote party of another call while this user drops out of both calls. For call transfer to be possible, the phone must have one call on hold and another call either connected or still ringing at the remote end. If call transfer is possible then it will be reflected in the affected call's dynamic capabilities, i.e. the KCapsTransfer bit of TMobileCallControlCaps will be set.

Use RTelSubSessionBase::CancelAsyncRequest(EMobileCallTransfer) to cancel a previously placed asynchronous Transfer() request.

Bearer Capability Repeat Indicator.

TMobileCallParamsV7 RSat::TBCRepeatIndicator

The originator of a call.

RSat::TCallParamOrigin

Describes the state of the icon.

TIconId RSat::TIconQualifier

The Air interface user rate.

Modes: GSM/WCDMA.

Supported Air Interface User Rates.

Call Asymmetry preferences.

Modes: GSM/WCDMA

TMobileHscsdCallParamsV1

The call asymmetry capabilities.

Modes: GSM/WCDMA

TMobileCallDataCapsV1

Contains audio tone events.

List of 3GPP defined supervisory audio tones taken from technical specification 3GPP TS 22.001 v4.0.0 Annex F.

This enumeration is based on the signal information element specified in Table 10.5.130/3GPP TS 24.008 v5.15.0

Mobile call control capabilites.

Modes: Common

The call set-up requested data protocol.

Modes: GSM/WCDMA

List of supported values of the <speed> parameter returned in response to AT+CBST=?

Not applicable to CDMA mode

TMobileDataCallParamsV1

The call set-up requested quality of service (QoS).

Modes: GSM/WCDMA

TMobileDataCallParamsV1

Maps to list of supported <ce> returned in response to AT+CBST=?

Not applicable to CDMA mode.

TMobileCallDataCapsV1

The call set-up requested RLP version.

TMobileDataCallParamsV1

The call setup requested data services.

Modes: Common

TMobileDataCallParamsV1

In GSM mode, maps to list of supported <name> returned in response to AT+CBST=? In CDMA mode, maps to supported service options.

Modes: COMMON

TMobileCallDataCapsV1

The call setup requested data speed.

TMobileDataCallParamsV1

In GSM mode, maps to list of supported speeds returned in response to AT+CBST=?. In CDMA mode, maps to data rates supported by supported service options.

TMobileCallDataCapsV1

The V.42bis parameters used in the call set-up of a V.42bis data call.

TMobileDataCallParamsV1

The type of call deflection requested.

Deflect()

The direction of the mobile call.

Modes: Common

TMobileCallRemotePartyInfoV1

The mobile call events.

Modes: Common

Mobile call events capabilities.

Modes: Common

Caller Id restriction settings.

Modes: Common

TMobileCallParamsV1

Determines which fields in the class are valid.

TMobileCallInfoV1

Multicall Operation set-up.

Mode: WCDMA

The mobile call parameter extension IDs.

Modes: Common

The supported Call RLP versions.

Modes: GSM/WCDMA

TMobileCallDataCapsV1

Remote party Identity status.

Modes: Common

TMobileCallRemotePartyInfoV1

Describes the possible call states.

Call traffic channels.

Modes: CDMA 9.5

The call channel coding used.

Modes: GSM/WCDMA

HSCSD coding capabilities.

Modes: GSM/WCDMA

The UUS capabilities of the call.

Modes: GSM/WCDMA.

UUS Service requests.

Modes: GSM/WCDMA

The supported V42bis options.

Modes: GSM/WCDMA

TMobileCallDataCapsV1

A buffer to hold an alpha identifier.

TMobileCallParamsV7 TMobileCallInfoV7 RSat::TAlphaIdBuf

Packaging typedef for TAudioToneV3 class.

TCcp ( Capability configuration parameters ) is an 8-bit data buffer that contains the bearer capabilities as coded in ETSI 24.008(Ver 04.11 2003-06) and defined in ETSI 31.111. It is 15 bytes long as it does not include the IEI (Information Element Identity).

TMobileCallParamsV7 RSat::TCcp

A typedef'd packaged TEtel3rdPartyMobileCallParamsV1 for passing through a generic API function member.

A typedef'd packaged TMobileCallCapsV1 for passing through a generic API function member.

A typedef'd packaged TMobileCallDataCapsV1 for passing through a generic API function member.

A typedef'd packaged TMobileCallHscsdInfoV1 for passing through a generic API function member.

A typedef'd packaged TMobileCallHscsdInfoV7 for passing through a generic API function member.

A typedef'd packaged TMobileCallHscsdInfoV8 for passing through a generic API function member.

A typedef'd packaged TMobileCallInfoV1 for passing through a generic API function member.

A typedef'd packaged TMobileCallParamsV1 for passing through a generic API function member.

A typedef'd packaged TMobileCallParamsV1 for passing through a generic API function member.

A typedef'd packaged TMobileCallParamsV7 for passing through a generic API function member.

A typedef'd packaged TMobileCallRemotePartyInfoV1 for passing through a generic API function member.

Buffer for the UUI element.

A typedef'd packaged TMobileCallUUSRequestV1 for passing through a generic API function member.

A typedef'd packaged TMobileDataCallParamsV1 for passing through a generic API function member.

A typedef'd packaged TMobileDataCallParamsV2 for passing through a generic API function member.

A typedef'd packaged TMobileDataCallParamsV8 for passing through a generic API function member.

A typedef'd packaged TMobileDataRLPRangesV1 for passing through a generic API function member.

A typedef'd packaged TMobileHscsdCallParamsV1 for passing through a generic API function member.

A typedef'd packaged TMobileHscsdCallParamsV2 for passing through a generic API function member.

A typedef'd packaged TMobileHscsdCallParamsV7 for passing through a generic API function member.

A typedef'd packaged TMobileHscsdCallParamsV8 for passing through a generic API function member.

A buffer to hold the sub-address of a telephone number.

KSubAddressMaxSize RSat::TSubAddress