A.8 InitiateCallAttempt operation

29.0783GPPCAMEL Application Part (CAP) specificationCustomised Applications for Mobile network Enhanced Logic (CAMEL) Phase XRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

On receipt of an InitiateCallAttempt operation, the GMSC/gsmSSF or VMSC/gsmSSF prepares to set up a new call leg in an existing call configuration, or to set up a new call, to the destination defined by the DestinationRoutingAddress parameter. The GMSC/gsmSSF or VMSC/gsmSSF does not send the ISUP IAM until it has received a ContinueWithArgument operation, which contains additional information needed to populate the parameters of the ISUP IAM.

For a new call leg in an existing call, except a NC call, all parameters which were received in the ISUP IAM and which were not replaced by parameters mapped from the InitiateCallAttempt or ContinueWithArgument operation, shall be treated (and propagated to the succeeding exchange) according to the normal procedures. The rule of copying ISUP parameters received from incoming leg to NP leg is valid also when the incoming leg no longer exists.

Table A.6 illustrates the mapping of parameters received in the InitiateCallAttempt operation to parameters sent in the ISUP IAM to the succeeding exchange.

Table A.6

CAP Operation InitiateCallAttempt (Note 1)	ISUP message IAM
DestinationRoutingAddress	Called party number
CallingPartyNumber	Calling party number
	Transmission medium requirement (Note 2) (Note 4)
	Access transport (Note 3) (Note 4)

NOTE 1: Optional parameters may be absent, i.e. they are mapped only if received.

NOTE 2: The transmission medium requirement parameter field shall be set to "speech".

NOTE 3: The "Bearer capability" and "High layer compatibility information" elements shall be filled in accordance with ETSI EN 300 403‑1 [25] for speech call.

NOTE 4: Only the minimum set of parameters indicating the fact that the call is a speech call is described here.

Annex B (normative):
Mapping between CAP and MAP and mapping between CAP and SM-CP

The Short Message signalling between the SMS-GMSC and the MSC or SGSN, for the transport of SM RP-DUs, is specified in 3GPP TS 29.002 [11]. The Short Message signalling between the MSC or SGSN and the MS, for the transport of SM RP-DUs, is specified in 3GPP TS 24.011 [10].