Supported CS1 INAP Operations

Call Control Framework (CCF) supports Capability Set 1 (CS1) Intelligent Network Application Protocol (INAP) operations for call charging scenarios.

For the following operations, there are no protocol differences between CS1 and CAP2:
  • ActivityTest
  • Cancel
  • Continue
  • DisconnectForwardConnection
  • Received Information
  • ReleaseCall
  • RequestReportBCSMEvent
  • ResetTimer
  • SpecializedResourceReport

For more information about these operations, see the discussions about supported CAP operations between the MSC and CCF, and supported CAP operations between CCF and the MSC.

Differences between the CS1 and CAP protocols for the following operations are noted in the following sections:

ApplyCharging and ApplyChargingReport

The CS1 definitions for the ApplyCharging and ApplyChargingReport operations do not specify most of the contents of these operations, and operators must define the contents themselves. CCF provides support for operator-defined CS1 ApplyCharging and ApplyChargingReport operations by converting CAP ApplyCharging operations to CS1, and CS1 ApplyChargingReport operations to CAP. For information about defining CS1 ApplyCharging and ApplyChargingReport operations, see the discussion about custom ApplyCharging and ApplyChargingReport operations.

AssistRequestInstructions

CCF supports AssistRequestInstructions operations sent from the IVR. Supported AssistRequestInstructions Parameters lists the parameters used in AssistRequestInstructions operations and indicates whether CCF supports them. Parameters are listed in the order in which they appear in the specification documents.

Table 1. Supported AssistRequestInstructions Parameters
AssistRequestInstructions Parameter Protocol Versions Supported
correlationID CAP2, CAP3, CAP4, CS1 Yes
iPAvailable CS1 Yes
iPSSPCapabilities CAP2, CAP3, CAP4, CS1 Yes (optional for CS1 but required for CAP)
extensions CAP2, CAP3, CAP4, CS1 No

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.
Table 2. Supported CallInformationReport Parameters
CallInformationReport Parameter Protocol Versions Supported
requestedInformationList CAP2, CAP3, CAP4, CS1 Yes
extensions - No
legID CAP2, CAP3, CAP4 Not supported in CS1

CallInformationRequest

CCF sends CallInformationRequest operations to request specific call information for a single call party. The result is returned in a CallInformationReport operation at the end of the call or call party connection. Supported CallInformationRequest Parameters lists the parameters used in CallInformationRequest operations and indicates whether CCF supports them.
Note: The CAP1 protocol does not support CallInformationRequest operations.
Table 3. Supported CallInformationRequest Parameters
CallInformationRequest Parameter Protocol Versions Supported
requestedInformationTypeList CAP2, CAP3, CAP4, CS1 Yes
extensions - No
legID CAP2, CAP3, CAP4 Not supported for CS1

Connect

CCF sends Connect operations to request the MSC to perform call processing actions, for example, to route a call to a specific destination or to influence other call set-up information. Supported Connect Parameters lists the parameters used in Connect operations and indicates whether CCF supports them.

Table 4. Supported Connect Parameters
Connect Parameter Protocol Versions Supported
destinationRoutingAddress CAP1, CAP2, CAP3, CAP4, CS1 Yes
alertingPattern CAP2, CAP3, CAP4, CS1 No
correlationID CS1 -
cutAndPaste CS1 -
originalCalledPartyID CAP1, CAP2, CAP3, CAP4, CS1 Yes
routeList CS1 -
scfID CS1 -
serviceInteractionIndicators CS- No
serviceInteractionIndicatorsTwo CAP3, CAP4 No
callingPartyNumber CS1 No
callingPartysCategory CAP1, CAP2, CAP3, CAP4, CS1 Yes
redirectingPartyID CAP1, CAP2, CAP3, CAP4, CS1 Yes
redirectionInformation CAP1, CAP2, CAP3, CAP4, CS1 Yes
genericNumbers CAP1, CAP2, CAP3, CAP4 Not supported for CS1
suppressionOfAnnouncement CAP1, CAP2, CAP3, CAP4 Not supported for CS1
oCSIApplicable CAP1, CAP2, CAP3, CAP4 Not supported for CS1
na-Info CAP2 No
naCarrierInformation CAP2 No
- naOliInfo CAP2 No
- naChargeNumber CAP2 No
Carrier CAP3, CAP4 No
- carrierSelectionField CAP3, CAP4 No
- carrierID CAP3, CAP4 No
naOliInfo CAP3, CAP4 No
chargeNumber CAP3, CAP4 No
cug_Interlock CAP3, CAP4 No
cug_OutgoingAccess CAP3, CAP4 No
bor-InterrogationRequested CAP4 No
legToBeConnected CAP4 Yes
extensions CAP3 No

ConnectToResource

CCF can send a ConnectToResource request to the MSC to connect a call to a specialized resource function (SRF), such as an IVR. Supported ConnectToResource Parameters lists the parameters used in ConnectToResource operations and indicates whether CCF supports them.

Note: For ConnectToResource operations and EstablishTemporaryConnection operations, only the bothwayThroughConnectionInd sub-field of the serviceInteractionIndicatorsTwo parameter is supported. All the other serviceInteractionIndicatorsTwo sub-fields are not supported.
Table 5. Supported ConnectToResource Parameters
ConnectToResource Parameter Protocol Versions Supported
resourceAddress CAP2, CAP3, CAP4, CS1 Yes
extensions CAP2, CAP3, CAP4, CS1 No
serviceInteractionIndicators CS1 Yes
serviceInteractionIndicatorsTwo CAP2, CAP3, CAP4 Not supported for CS1
callSegmentId CAP4 Not supported for CS-1

EstablishTemporaryConnection

CCF can send an EstablishTemporaryConnection request to the MSC to create a temporary connection to a resource, such as an IVR, for example to play an announcement or to collect user information.
Note: The CAP1 protocol does not support EstablishTemporaryConnection operations.

Supported EstablishTemporaryConnection Parameters lists the parameters used in EstablishTemporaryConnection operations and indicates whether CCF supports them.

Note: For ConnectToResource operations and EstablishTemporaryConnection operations, only the bothwayThroughConnectionInd sub-field of the serviceInteractionIndicatorsTwo parameter is supported. All the other serviceInteractionIndicatorsTwo sub-fields are not supported.
Table 6. Supported EstablishTemporaryConnection Parameters
EstablishTemporaryConnection Parameter Protocol Versions Supported
assistingSSPIPRoutingAddress CAP2, CAP3, CAP4, CS1 Yes
correlationID CAP2, CAP3, CAP4, CS1 Yes
scfID CAP2, CAP3, CAP4, CS1 Yes
extensions CAP2, CAP3, CAP4, CS1 No
serviceInteractionIndicators CS1 No
serviceInteractionIndicatorsTwo CAP2, CAP3, CAP4 No
- bothwayThroughConnectionInd CAP2, CAP3, CAP4 Yes
carrier CAP3 No
- carrierSelectionField CAP3, CAP4 No
- carrierID CAP3, CAP4 No
naOliInfo CAP3, CAP4 No
ChargeNumber

chargeNumber

CAP3

CAP4

Yes
callSegmentID CAP4 Yes

FurnishChargingInformation

The contents of the FurnishChargingInformation are undefined in CS1, and must be specified by the operator. CCF provides support for sending operator-defined FurnishChargingInformation operations. For information about defining custom FurnishChargingInformation operations, see the discussion about sending FurnishChargingInformation.

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.

Table 7. Supported InitialDP Parameters
InitialDP Parameter Protocol Versions Supported
serviceKey CAP1, CAP2, CAP3, CAP4, CS1 Yes
calledPartyNumber CAP1, CAP2, CAP3, CAP4, CS1 Yes
callingPartyNumber CAP1, CAP2, CAP3, CAP4, CS1 Yes
callingPartysCategory CAP1, CAP2, CAP3, CAP4, CS1 Yes
cgEncountered CAP3, CAP4, CS-1 No
iPSSPCapabilities CAP2, CAP3, CAP4, CS1 Yes
locationNumber CAP1, CAP2, CAP3, CAP4, CS1 Yes
originalCalledPartyID CAP1, CAP2, CAP3, CAP4, CS1 Yes
extensions CAP2, CAP3, CAP4, CS1 No
highLayerCompatibility CAP1, CAP2, CAP3, CAP4 Yes
additionalCallingPartyNumber CAP1, CAP2, CAP3, CAP4, CS1 Yes
forwardCallindicators CS1 -
bearerCapability CAP1, CAP2, CAP3, CAP4, CS1 Yes
eventTypeBCSM CAP1, CAP2, CAP3, CAP4, CS1 Yes
redirectingPartyID CAP1, CAP2, CAP3, CAP4, CS1 Yes
redirectionInformation CAP1, CAP2, CAP3, CAP4, CS1 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