Supported CAP Operations Between the MSC and CCF
Call Control Framework (CCF) supports CAMEL Application Part (CAP) protocol operations for voice calls and SMS that are sent to CCF from the Mobile Switching Center (MSC).
The following operations are supported:
CCF supports the following result returned for the PromptAndCollectUserInformation operation:
The available parameters for each operation, an indication of whether CCF supports them, and the available CAP protocol versions, are listed in the following tables. Parameters are listed in the order in which they appear in the specification documents.
ActivityTest Response
MATRIXX Engine periodically sends ActivityTest operations for non-chargeable voice calls that are being monitored (through CallInformationRequest operations) to find out whether calls are still active. The results are returned in the ActivityTest response. No parameters are sent in ActivityTest operations and responses.
ApplyChargingReport
The ApplyChargingReport operation returns the results of an earlier ApplyCharging operation for a chargeable voice call or SMS. Supported ApplyChargingReport Parameters lists the parameters used in
ApplyChargingReport operations and indicates whether CCF supports them.
Note: The CAP1 protocol does not support ApplyChargingReport operations.
| ApplyChargingReport Parameter | CAP Protocol Version | Supported |
|---|---|---|
| CallResult.timeInformation | CAP2, CAP3, CAP4 | Yes |
| - timeIfNoTariffSwitch | CAP2, CAP3, CAP4 | Yes |
| - timeIfTariffSwitch | CAP2, CAP3, CAP4 | No |
| - - timeSinceLastTariffSwitch | CAP2, CAP3, CAP4 | No |
| - - tariffSwitchInterval | CAP2, CAP3, CAP4 | No |
| CallResult.callReleasedAtTcpExpiry | CAP3 | Yes |
| CallResult.extensions | CAP3 | No |
| CallResult.aChChargingAddress | CAP4 | No |
| partyToCharge | CAP2, CAP3, CAP4 | No |
| CallActive | CAP2, CAP3, CAP4 | Yes |
CallInformationReport
The CallInformationReport operation returns specific call information for a single call party as requested by MATRIXX Engine in an earlier CallInformationRequest operation. The report is sent at the end of the call or
call party connection. Supported CallInformationReport Parameters lists the
parameters used in CallInformationReport operations and indicates whether CCF supports them.
Note: The CAP1 protocol does not support CallInformationReport operations.
| CallInformationReport Parameter | CAP Protocol Version | Supported |
|---|---|---|
| requestedInformationList | CAP2, CAP3, CAP4 | Yes |
| extensions | - | No |
| legID | CAP2, CAP3, CAP4 | Yes |
EntityReleased
The EntityReleased operation, sent by the MSC, provides information about the release of a
logical entity (Call Segment or BCSM) caused by an exception or an error. Supported EntityReleased Parameters lists the parameters used in EventReportBCSM
operations and indicates whether CCF supports them.
Note: The CAP1 protocol does not
support EntityReleased operations.
| EntityReleased Parameter | CAP Protocol Version | Supported |
|---|---|---|
| CSFailure | CAP4 | Yes |
| - callSegmentID | CAP4 | Yes |
| - cause | CAP4 | Yes |
| BCSMFailure | CAP4 | Yes |
| - legID | CAP4 | Yes |
| - cause | CAP4 | Yes |
EventReportBCSM
EventReportBCSM operations are sent in response to a call related event requested earlier by MATRIXX Engine through a RequestReportBCSMEvent operation. Supported EventReportBCSM Parameters lists the parameters used in EventReportBCSM operations and indicates whether CCF supports them.
| EventReportBCSM Parameter | CAP Protocol Version | Supported |
|---|---|---|
| eventTypeBCSM | CAP1, CAP2, CAP3, CAP4 | Yes |
| eventSpecificInformationBCSM | CAP1, CAP2, CAP3, CAP4 | Yes |
| legID | CAP1, CAP2, CAP3, CAP4 | Yes |
| miscCallInfo | CAP1, CAP2, CAP3, CAP4 | Yes |
| extensions | - | No |
EventReportSMS
EventReportSMS operations are sent in response to an SMS related event requested earlier by MATRIXX Engine through a
RequestReportSMSEvent operation. Supported EventReportSMS Parameters lists
the parameters used in EventReportSMS operations and indicates whether CCF supports them.
Note: EventReportSMS operations are available only in CAP3 and CAP4. The CAP1 and CAP2
protocols do not support SMS operations.
| EventReportSMS Parameter | CAP Protocol Version | Supported |
|---|---|---|
| eventTypeSMS | CAP3, CAP4 | Yes |
| – sms-CollectedInfo | CAP3, CAP4 | Yes |
| – o-smsFailure | CAP3, CAP4 | Yes |
| – o-smsSubmission | CAP3, CAP4 | Yes |
| – sms-DeliveryRequested | CAP4 | Yes |
| – t-smsFailure | CAP4 | Yes |
| – t-smsDelivery | CAP4 | Yes |
| eventSpecificInformationSMS | CAP3, CAP4 | Yes |
| – o-smsFailureSpecificInfo | CAP3, CAP4 | Yes |
| – o-smsSubmissionSpecificInfo | CAP3, CAP4 | Yes |
| – t-smsFailureSpecificInfo | CAP4 | Yes |
| – t-smsDeliverySpecificInfo | CAP4 | Yes |
| miscCallInfo | CAP3, CAP4 | Yes |
| extensions | - | No |
InitialDP
InitialDP operations are sent at the beginning of a voice call. InitialDP operations contain call set-up information. Supported InitialDP Parameters lists the parameters used in InitialDP operations and indicates whether CCF supports them.
| InitialDP Parameter | CAP Protocol Version | Supported |
|---|---|---|
| serviceKey | CAP1, CAP2, CAP3, CAP4 | Yes |
| calledPartyNumber | CAP1, CAP2, CAP3, CAP4 | Yes |
| callingPartyNumber | CAP1, CAP2, CAP3, CAP4 | Yes |
| callingPartysCategory | CAP1, CAP2, CAP3, CAP4 | Yes |
| cgEncountered | CAP3, CAP4 | No |
| iPSSPCapabilities | CAP2, CAP3, CAP4 | Yes |
| locationNumber | CAP1, CAP2, CAP3, CAP4 | Yes |
| originalCalledPartyID | CAP1, CAP2, CAP3, CAP4 | Yes |
| extensions | CAP2, CAP3, CAP4 | No |
| highLayerCompatibility | CAP1, CAP2, CAP3, CAP4 | Yes |
| additionalCallingPartyNumber | CAP1, CAP2, CAP3, CAP4 | Yes |
| bearerCapability | CAP1, CAP2, CAP3, CAP4 | Yes |
| eventTypeBCSM | CAP1, CAP2, CAP3, CAP4 | Yes |
| redirectingPartyID | CAP1, CAP2, CAP3, CAP4 | Yes |
| redirectionInformation | CAP1, CAP2, CAP3, CAP4 | Yes |
| Cause | CAP3, CAP4 | Yes |
| serviceInteractonIndicatosTwo | CAP3, CAP4 | No |
| carrier | CAP3 | No |
| cug-Index | CAP3, CAP4 | No |
| cug-Interlock | CAP3, CAP4 | No |
| cug_OutgoingAccess | CAP3, CAP4 | No |
| iMSI | CAP1, CAP2, CAP3, CAP4 | Yes |
| subscriberState | CAP1, CAP2, CAP3, CAP4 | Yes |
| locationInformation | CAP1, CAP2, CAP3, CAP4 | Yes |
| ext-basicServiceCode | CAP1, CAP2, CAP3, CAP4 | Yes |
| callReferenceNumber | CAP1, CAP2, CAP3, CAP4 | Yes |
| mscAddress | CAP1, CAP2, CAP3, CAP4 | Yes |
| calledPartyBCDNumber | CAP1, CAP2, CAP3, CAP4 | Yes |
| timeAndTimezone | CAP2, CAP3, CAP4 | Yes |
| gsm-ForwardingPending | CAP2, CAP3 | Yes |
| callForwardingSS-Pending | CAP4 | No |
| initialDPArgExtension | CAP2, CAP3, CAP4 | Yes |
InitialDPSMS
InitialDPSMS operations are sent at the beginning of an SMS. InitialDPSMS operations contain
SMS set-up information. Supported InitialDPSMS Parameters lists the parameters used in InitialDPSMS
operations and indicates whether CCF supports them.
Note: InitialDPSMS operations
are available only in CAP3 and CAP4. The CAP1 and CAP2 protocols do not support
SMS operations.
| InitialDPSMS Parameter | CAP Protocol Version | Supported |
|---|---|---|
| serviceKey | CAP3, CAP4 | Yes |
| destinationSubscriberNumber | CAP3, CAP4 | Yes |
| callingPartyNumber | CAP3, CAP4 | Yes |
| eventTypeSMS | CAP3, CAP4 | Yes |
| iMSI | CAP3, CAP4 | Yes |
| locationInformationMSC | CAP3, CAP4 | Yes |
| locationInformationGPRS | CAP3, CAP4 | Yes |
| sMSCAddress | CAP3, CAP4 | Yes |
| timeAndTimezone | CAP3, CAP4 | Yes |
| tPShortMessageSubmissionInfo | CAP3 | Yes |
| tPShortMessageSpecificInfo | CAP4 | Yes |
| tPProtocolIdentifier | CAP3, CAP4 | Yes |
| tPDataCodingScheme | CAP3, CAP4 | Yes |
| tPValidityPeriod | CAP3, CAP4 | Yes |
| extensions | CAP3, CAP4 | No |
| smsReferenceNumber | CAP3, CAP4 | Yes |
| mscAddress | CAP3, CAP4 | Yes |
| sgsn-Number | CAP3, CAP4 | Yes |
| ms-Classmark2 | CAP4 | No |
| gPRSMSClass | CAP4 | No |
| iMEI | CAP4 | Yes |
| calledPartyNumber | CAP3, CAP4 | Yes. Used by the MT SMS service. The MO SMS service uses the destinationSubscriberNumber. |
ReceivedInformationArg Results
The information collected from the subscriber following a PromptAndCollectUserInformation operation is returned in the ReceivedInformationArg results. Supported ReceivedInformation Parameters lists the ReceivedInformationArg results parameters and indicates whether CCF supports them.
| ReceivedInformationArg Parameter | CAP Protocol Version | Supported |
|---|---|---|
| digitsResponse | CAP2, CAP3, CAP4 | Yes |