8.73 Monitor of current calls +CMCCS

27.0073GPPAT command set for User Equipment (UE)Release 18TS

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

Table 8.73-1: +CMCCS parameter command syntax

Command	Possible response(s)
+CMCCS=[<n>]	when <n>=1 and command successful: +CMCCS: (list of supported <x>s)
+CMCCS?	+CMCCS: <n>
+CMCCS=?	+CMCCS: (list of supported <n>s)

Description

This command activates or deactivates a call monitoring function in the ME. When this function is activated in the ME, the ME informs about events for calls with unsolicited result codes.

The purpose of the call monitoring function is to:

1) gather relevant information for the detected calls in a TE; and

2) make it possible for the TE to display call state information for ongoing calls.

The unsolicited result code+CMCCSI is used for basic call information.

+CMCCSI: <ccidx>,<dir>,<neg_status_present>,<neg_status>,<SDP_md>,<cs_mode>,<ccstatus>,<mpty>,<numbertype>,<ton>,<number>,<exittype>,<exitcause>

The unsolicited result code +CMCCSI is provided when <n>=2. For an originating call, the parameters <numbertype>, <ton> and <number> in +CMCCSI provide the number (line identity) information which has been dialled with +CDU or ATD. For a terminating call, the parameters <numbertype>, <ton> and <number> in +CMCCSI provide the number (line identity) information of the calling user.

The unsolicited result codes +CMCCSS<x> / +CMCCSSEND are used for supplementary service related information.

+CMCCSS1: <ccidx>,<dir>,<service>
[+CMCCSS2: <numbertype>,<ton>,<number>]
[+CMCCSS3: <CLI_validity>]
[+CMCCSS4: <name>]
[+CMCCSS5: <subaddr>,<satype>]
[+CMCCSS6: <priority>]
[+CMCCSS7: <CUG_index>]
[+CMCCSS8: <eCNAM_meta>]
+CMCCSSEND

The unsolicited result codes +CMCCSS<x> / +CMCCSSEND are used for supplementary service related information and are reported when <n>=3. For every supplementary service related event, the unsolicited result codes +CMCCSS<x> shall be given in consecutive order, and the sequence of unsolicited result codes shall be terminated by +CMCCSSEND. It is manufacturer specific when and if this additional service reporting will be issued. Whenever a service event is to be reported using these unsolicited result codes, the codes +CMCCSS1 and +CMCCSSEND are mandatory. +CMCCSS1 contains essential information that is always needed (for example <ccidx>) and +CMCCSSEND indicates the end of this particular set of unsolicited result codes. The other unsolicited result codes (+CMCCSS2 to +CMCCSSn) are optional, intended to provide information related to a given service. E.g. for the supplementary service CNAP, the unsolicited result code +CMCCSS4 (containing <name>) may be issued. It is implementation specific which of the unsolicited result codes +CMCCSS<x> / +CMCCSSEND that are supported and provided to the TE. The unsolicited result codes should be provided to the TE as soon as the information is available in the ME. The parameters <numbertype>, <ton> and <number> in +CMCCSS2 are, if applicable, normally the line identity information that is related to the parameter <service>.

NOTE 1: For situations where ringing is applicable, the unsolicited result codes +CMCCSS<x> / +CMCCSSEND are typically returned after the first RING (or +CRING: <type>; refer clause "Cellular result codes +CRC") result code sent from TA to TE.

A subset of the information provided by the call monitoring function can be provided by the command +CLCCS.

When the unsolicited result code +CMCCSI report that the <ccstatus>=1 (Idle), the call identification number is reset and the call identification number <ccidx> can be used by new calls. The logic for reuse of the parameter <ccidx> is implementation specific.

Read command returns the current value of <n>.

Test command returns the values supported as a compound value.

Defined values

<n>: integer type

0 The call monitoring function is disabled

1 List the unsolicited result codes +CMCCSS<x> that are supported by the TE. The supported values for <x> are reported as a compound value, e.g. a TE supporting +CMCCSS1, +CMCCSS2 and +CMCCSS5 will report +CMCCS: (1,2,5) or +CMCCS: (1-2,5)

2 The call monitoring function is enabled for basic call information (unsolicited result code +CMCCSI)

3 The call monitoring function is enabled for basic call information and supplementary service information (unsolicited result codes +CMCCSI and +CMCCSS<x> / +CMCCSSEND)

<x>: integer type. <x> is the suffix in the unsolicited result codes +CMCCSS<x>.

<ccidx>: integer type. Call identification number as described in 3GPP TS 22.030 [19] clause 6.5.5.1. This number can be used in +CHLD command operations. Value range is from 1 to N. N, the maximum number of simultaneous call control processes is implementation specific. The call identification number must not be reused until the unsolicited result code +CMCCSI has indicated that the <ccstatus>=1 (Idle).

<dir>: integer type

0 mobile originated (MO) call

1 mobile terminated (MT) call

<neg_status_present>: integer type. Indicates whether parameter <neg_status> has any valid information.

0 No valid information in parameter <neg_status>. Parameter <neg_status> is set to zero.

1 Valid information in parameter <neg_status>.

<neg_status>: integer type as defined in the +CCMMD command.

0 The parameter <neg_status> has no valid content. Parameter <SDP_md> is set to an empty string ("").

1 The <SDP_md> parameter describes the active media in the call.

2 The <SDP_md> parameter describes a proposed but not yet active new set of media for the call.

3 A proposed new set of media for the call was accepted by the remote party. The <SDP_md> parameter describes the accepted media by the remote party. The accepted media can be same as proposed new set of media or a subset of proposed media.

4 A proposed new set of media for the call was rejected by the remote party. The <SDP_md> parameter will be set to an empty string ("").

<SDP_md>: string type represented with IRA characters. Media description as per the +CDEFMP command. This parameter shall not be subject to conventional character conversion as per +CSCS. This parameter will be an empty string ("") if the call has no multimedia content.

<cs_mode>: integer type (bearer/teleservice). Applicable to CS calls only.

0 no relevant information about bearer/teleservice

1 voice

2 data

3 fax

4 voice followed by data, voice mode

5 alternating voice/data, voice mode

6 alternating voice/fax, voice mode

7 voice followed by data, data mode

8 alternating voice/data, data mode

9 alternating voice/fax, fax mode

255 unknown

<ccstatus>: integer type Indicating the state of the call.

1 Idle

2 Calling (MO); the call setup has been started

3 Connecting (MO); the call is in progress

4 Alerting (MO): an alert indication has been received

5 Alerting (MT); an alert indication has been sent

6 Active; the connection is established

7 Released; an outgoing (MO) call is released.

8 Released; an incoming (MT) call is released

9 User busy

10 User determined user busy

11 Call waiting (MO)

12 Call waiting (MT)

13 Call hold (MO)

14 Call hold (MT)

<mpty>: integer type

0 call is not one of multiparty (conference) call parties

1 call is one of multiparty (conference) call parties

<numbertype>: integer type. Indicating type of information in parameter <number>.

0 No valid information in parameter <number>. <number> shall then be set to empty string ("").

1 Number in <number> according to URI including the prefix specifying the URI type (see command +CDU). Parameter <ton> has no relevant information and is set to zero.

2 Number in <number> according to one of the formats supported by 3GPP TS 24.008 [8] clause 10.5.4.7)

<ton>: type of number in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7). The parameter is also set to zero when it has no meaningful content, e.g. when <numbertype>=1.

<number>: string type phone number in format specified by <numbertype>. The used character set should be the one selected with command select TE character set +CSCS. When no number is available, <number> shall be set to empty string ("").

<exittype>: integer type. Indicating type of information in parameter <exitcause>.

0 No valid information in parameter <exitcause>

1 Cause in <exitcause> according to 3GPP TS 24.008 [8], Annex H

2 Cause in <exitcause> according to 3GPP TS 24.229 [89], Annex A.2.1.4.1

<exitcause>: integer type. Additional information provided if relevant. If there is no relevant cause to report, or if <exittype>=0 the exitcause is set to 0 (<exitcause>=0).

<service>: integer type. Indication of the indicated (supplementary) service. It is vendor specific which of the services that are provided. The related unsolicited result codes +CMCCSS<x> are provided as applicable for a given <service>, e.g. the +CMCCSS5: <subaddr>,<satype> can be omitted when it is not relevant for the service, but can also be omitted if this information is not provided for a relevant service or if a vendor does not support parameters <subaddr> and <satype>.

0 No service

1 Originating identification presentation – CLIP / OIP, refer 3GPP TS 22.081 [3] and 3GPP TS 24.607 [119]
CLIP / OIP specific information can be provided in:
+CMCCSI (in parameters <numbertype>, <ton> and <number>)
Additional CLIP / OIP specific information can be provided in:
+CMCCSS1 (in parameter <service>)
+CMCCSS3 (in parameter <CLI_validity>, typically used when no <number> is available)
+CMCCSS5 (in parameters <subaddr> and <satype>, when applicable)

2 Originating identification restriction – CLIR / OIR, refer 3GPP TS 22.081 [3] and 3GPP TS 24.607 [119]

3 Terminating identification presentation – COLP / TIP, refer 3GPP TS 22.081 [3] and 3GPP TS 24.608 [120]
COLP / TIP specific information can be provided in:
+CMCCSI (in parameters <numbertype>, <ton> and <number>)
Additional COLP / TIP specific information can be provided in:
+CMCCSS1 (in parameter <service>)
+CMCCSS5 (in parameters <subaddr> and <satype>, when applicable)

4 Terminating identification restriction – COLR / TIR, refer 3GPP TS 22.081 [3] and 3GPP TS 24.608 [120]

5 Called line presentation – CDIP
Additional CDIP specific information can be provided in:
+CMCCSS1 (in parameter <service>)
+CMCCSS2 (in parameters <numbertype>, <ton> and <number>)
+CMCCSS5 (in parameters <subaddr> and <satype>, when applicable)

NOTE 2: The command +CDIP does not explicitly specify what "multiple called numbers" it is intended to support. +CMCCS can therefore not be more specific. The CDIP service in +CMCCS is therefore intended for manufacturers who already have chosen a manufacturer specific way to support +CDIP and needs to extend or replace +CDIP with support for SIP URIs. For manufacturers who do not already support the command +CDIP, the useage of the CDIP service in +CMCCS is deprecated.

6 Calling name presentation – CNAP, refer 3GPP TS 22.096 [93]
Additional CNAP specific information can be provided in:
+CMCCSS1 (in parameter <service>)
+CMCCSS4 (in parameter <name>)

7 Communication deflection – CD, refer 3GPP TS 22.072 [31] and 3GPP TS 24.604 [132]

8 Communication forwarding unconditional – CFU, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132]

9 Communication forwarding on busy user – CFB, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132]

10 Communication forwarding on no reply – CFNR, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132]

11 Communication forwarding on subscriber not reachable – CFNRc, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132]

12 Communication forwarding on not logged-in – CFNL, refer 3GPP TS 24.604 [132]

13 Communication diversion notification – CDIVN, refer 3GPP TS 24.604 [132]

14 Communication waiting – CW, refer 3GPP TS 22.083 [5] and 3GPP TS 24.615 [137]
Additional CW specific information can be provided in:
+CMCCSS1 (in parameter <service>)
+CMCCSS6 (in parameter <priority>)

15 Communication hold – HOLD, refer 3GPP TS 22.083 [5] and 3GPP TS 24.610 [135]

16 Conference – MPTY / CONF, refer 3GPP TS 22.084 [22] and 3GPP TS 24.605 [133]

17 Explicit communication transfer – ECT, refer 3GPP TS 22.091 [30] and 3GPP TS 24.629 [139]

18 Completion of communications to busy subscriber – CCBS, refer 3GPP TS 22.093 [123] and 3GPP TS 24.642 [140]

19 Completion of communications by no reply – CCNR, refer 3GPP TS 24.642 [140]

20 Communication barring of all outgoing calls – BAOC, refer 3GPP TS 22.088 [6] and 3GPP TS 24.611 [136]

21 Communication barring of all international outgoing calls except those directed to the home PLMN country – BOIC-exHC, refer 3GPP TS 22.088 [6] and 3GPP TS 24.611 [136]

22 Communication barring of all incoming calls – BAIC, refer 3GPP TS 22.088 [6] and 3GPP TS 24.611 [136]

23 Communication barring of incoming calls when roaming outside the home PLMN country – BIC-Roam, refer 3GPP TS 22.088 [6] and 3GPP TS 24.611 [136]

24 All barring services, refer 3GPP TS 22.030 [19]

25 All outgoing barring services, refer 3GPP TS 22.030 [19]

26 All incoming barring services, refer 3GPP TS 22.030 [19]

27 Anonymous communication rejection – ACR, refer 3GPP TS 22.088 [6] and 3GPP TS 24.611 [136]

28 Advice of charge – AOC, refer 3GPP TS 22.085 [21] and 3GPP TS 24.654 [121]

29 Message waiting indication – MWI, refer 3GPP TS 24.606 [134]

30 Malicious communication identification, all outgoing calls – MCID, refer 3GPP TS 24.616 [l38]

31 Unstructured supplementary service data – USSD, refer 3GPP TS 22.090 [23] and 3GPP TS 24.390 [131]

32 Customized alerting tones – CAT, refer 3GPP TS 24.182 [127]

33 Customized ringing signal – CRS, refer 3GPP TS 24.183 [128]

34 Flexible alerting – FA, refer 3GPP TS 24.239 [129]

35 Personal network management – PNM, refer 3GPP TS 24.259 [130]

36 User-to-user signalling service 1 – UUS 1, refer 3GPP TS 22.087 [58] and 3GPP TS 24.229 [89]

37 User-to-user signalling service 2 – UUS 2, refer 3GPP TS 22.087 [58]

38 User-to-user signalling service 3 – UUS 3, refer 3GPP TS 22.087 [58]

39 All user-to-user signalling services, refer 3GPP TS 22.087 [58]

40 Follow me – FM, refer 3GPP TS 22.094 [124]

41 Multiple subscriber profile – MSP, refer 3GPP TS 22.097 [125]

42 Multicall – MC, refer 3GPP TS 22.135 [126]

43 enhanced multi‑level precedence and pre-emption service – eMLPP, refer 3GPP TS 22.067 [54]

44 Closed user group – CUG, refer 3GPP TS 22.085 [21] and 3GPP TS 24.654 [121]
Additional CUG specific information can be provided in:
+CMCCSS1 (in parameter <service>)
+CMCCSS7 (in parameter <CUG_index>)

45 enhanced calling name – eCNAM, refer to 3GPP TS 24.196 [163] and 3GPP TS 22.173 [164].
eCNAM specific information can be provided in:
+CMCCSS1 (in parameter <service>)
Additional eCNAM specific information can be provided in:
+CMCCSS4 (in parameter <name>)
+CMCCSS8 (in parameter <eCNAM_meta>, when available)

256 – 511 Reserved for vendor specific services

<CLI_validity>: integer type. This parameter can provide details why <number> does not contain a calling party BCD number (refer 3GPP TS 24.008 [8] clause 10.5.4.30). The parameter is not relevant for MO call types.

0 CLI valid

1 CLI has been withheld by the originator (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Reject by user")

2 CLI is not available due to interworking problems or limitations of originating network (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Interaction with other service")

3 CLI is not available due to calling party being of type payphone (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Coin line/payphone")

4 CLI is not available due to other reasons (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Unavailable")

When CLI is not available (<CLI_validity>=2, <CLI_validity>=3 or <CLI_validity>=4), <number> shall be an empty string ("") and <ton> value will not be significant. The parameter <numbertype> will be set to 0. Nevertheless, TA may return the recommended value 128 for <ton> (TON/NPI unknown in accordance with 3GPP TS 24.008 [8] clause 10.5.4.7).

When CLI has been withheld by the originator, (<CLI validity>=1) and the CLIP is provisioned with the "override category" option (refer 3GPP TS 22.081 [3] and 3GPP TS 23.081 [40]), <number> and <ton> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available. The parameter <numbertype> shall be set as applicable.

<name>: string type up to 80 characters long string containing the calling name.

<subaddr>: string type subaddress of format specified by <satype>.

<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8) or RFC 4715 [122] appendix A.

<priority>: integer type indicating the eMLPP priority level of the call, values specified in 3GPP TS 22.067 [54].

<CUG_index>: string type. The parameter sets the CUG index for this <CUG_pointer>.

"0" … "32767" CUG index

"" no CUG index, indicated by empty string. Preferential CUG taken from subscriber data.

<eCNAM_meta>: string type up to 1000 characters long. The string contains additional information about the caller (such as language, location or results of analytics and verification of the caller – refer to 3GPP TS 24.196 [158] clause 4.5.3.3 about additional information in Call-Info header fields).

NOTE 3: The eCNAM metadata can also include graphics (e.g., logos and symbols). Manufacturer specifc commands are needed to upload such information.

Implementation

Optional.