## 9.3 Messages for circuit-switched call control

04.083GPPMobile radio interface Layer 3 specificationRelease 1998TS

Table 9.54/3GPP TS 04.08 summarizes the messages for circuit-switched call control.

Table 9.54/3GPP TS 04.08: Messages for circuit-mode connections call control

 Call establishment messages: Reference ALERTING 9.3.1 CALL CONFIRMED 1) 9.3.2 CALL PROCEEDING 9.3.3 CONNECT 9.3.5 CONNECT ACKNOWLEDGE 9.3.6 EMERGENCY SETUP 1) 9.3.8 PROGRESS 9.3.17 SETUP 9.3.23 Call information phase messages: Reference MODIFY 1) 9.3.13 MODIFY COMPLETE 1) 9.3.14 MODIFY REJECT 1) 9.3.15 USER INFORMATION 9.3.31 Call clearing messages: Reference DISCONNECT 9.3.7 RELEASE 9.3.18 RELEASE COMPLETE 9.3.19 Messages for supplementary service control Reference FACILITY 9.3.9 HOLD 1) 9.3.10 HOLD ACKNOWLEDGE 1) 9.3.11 HOLD REJECT 1) 9.3.12 RETRIEVE 1) 9.3.20 RETRIEVE ACKNOWLEDGE 1) 9.3.21 RETRIEVE REJECT 1) 9.3.22 Miscellaneous messages Reference CONGESTION CONTROL 9.3.4 NOTIFY 9.3.16 START DTMF 1) 9.3.24 START DTMF ACKNOWLEDGE 1) 9.3.25 START DTMF REJECT 1) 9.3.26 STATUS 9.3.27 STATUS ENQUIRY 9.3.28 STOP DTMF 1) 9.3.29 STOP DTMF ACKNOWLEDGE 1) 9.3.30

NOTE: Not supported by Blue Book ITU-T Recommendation Q.931.

#### 9.3.1.1 Alerting (network to mobile station direction)

This message is sent by the network to the calling mobile station to indicate that the called user alerting has been initiated.

See table 9.55/3GPP TS 04.08.

Significance: global

Direction: network to mobile station

Table 9.55/3GPP TS 04.08: ALERTING message content (network to mobile station direction)

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Alerting Message type M V 1 message type 10.4 1C Facility Facility O TLV 2-? 10.5.4.15 1E Progress indicator Progress indicator O TLV 4 10.5.4.21 7E User-user User-user O TLV 3-131 10.5.4.25
##### 9.3.1.1.1 Facility

This information element may be used for functional operation of supplementary services.

##### 9.3.1.1.2 Progress indicator

This information element may be included by the network:

– in order to pass information about the call in progress, e.g., in the event of interworking; and/or

– to make the mobile station attach the user connection for speech.

##### 9.3.1.1.3 User-user

This information element may be included by the network if the called remote user included a user-user information element in the ALERTING message.

#### 9.3.1.2 Alerting (mobile station to network direction)

This message is sent by the called mobile station to the network, to indicate that the called user alerting has been initiated.

See table 9.55a/3GPP TS 04.08.

Significance: global

Direction: mobile station to network

Table 9.55a/3GPP TS 04.08: ALERTING message content (mobile station to network direction)

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Message type

M

V

1

message type

10.4

1C

Facility

Facility

O

TLV

2-?

10.5.4.15

7E

User-user

User-user

O

TLV

3-131

10.5.4.25

7F

SS version

SS version indicator

O

TLV

2-3

10.5.4.24

##### 9.3.1.2.1 Facility

This information element may be used for functional operation of supplementary services.

##### 9.3.1.2.2 User-user

This information element may be included when the called mobile station wants to return information to the calling remote user.

##### 9.3.1.2.3 SS version

This information element shall not be included if the facility information element is not present in this message.

This information element shall be included or excluded as defined in 3GPP TS 04.10. This information element should not be transmitted unless explicitly required by 3GPP TS 04.10.

### 9.3.2 Call confirmed

This message is sent by the called mobile station to confirm an incoming call request.

See table 9.56/3GPP TS 04.08.

Message type: CALL CONFIRMED

Significance: local

Direction: mobile station to network

Table 9.56/3GPP TS 04.08: CALL CONFIRMED message content

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Call confirmed

Message type

M

V

1

message type

10.4

D-

Repeat Indicator

Repeat Indicator

C

TV

1

10.5.4.22

04

Bearer capability 1

Bearer capability

O

TLV

3-15

10.5.4.5

04

Bearer capability 2

Bearer capability

O

TLV

3-15

10.5.4.5

08

Cause

Cause

O

TLV

4-32

10.5.4.11

15

CC Capabilities

Call Control Capabilities

O

TLV

3

10.5.4.5a

#### 9.3.2.1 Repeat indicator

The repeat indicator information element shall be included if bearer capability 1 information element and bearer capability 2 IE are both included in the message.

#### 9.3.2.2 Bearer capability 1 and bearer capability 2

The bearer capability 1 information element shall be included if and only if at least one of the following six cases holds:

– the mobile station wishes another bearer capability than that given by the bearer capability 1 information element of the incoming SETUP message;

– the bearer capability 1 information element is missing or not fully specified in the SETUP message;

• the bearer capability 1 information element received in the SETUP message is accepted and the "radio channel requirement" of the mobile station is other than "full rate support only mobile station";

– the bearer capability 1 information element received in the SETUP message indicates speech and is accepted and the mobile station supports CTM text telephony;

– the bearer capability 1 information element received in the SETUP message indicates speech and is accepted and the mobile station supports other speech versions than GSM version 1;

– the bearer capability 1 information element received in the SETUP message included the "fixed network user rate" parameter.

When the bearer capability 1 information element is followed by the bearer capability 2 IE in the SETUP, the above rules apply to both bearer capability 1 IE and bearer capability 2 IE. Except those cases identified in 3GPP TS 07.01, if either bearer capability needs to be included, both shall be included.

Furthermore, both bearer capability information elements may be present if the mobile station wishes to reverse the order of occurrence of the bearer capability information elements (which is referred to in the repeat indicator information element, see sub-clause 10.5.4.22) in cases identified in 3GPP TS 07.01.

#### 9.3.2.3 Cause

This information element is included if the mobile station is compatible but the user is busy.

#### 9.3.2.4 CC Capabilities

This information element may be included by the mobile station to indicate its call control capabilities.

### 9.3.3 Call proceeding

This message is sent by the network to the calling mobile station to indicate that the requested call establishment information has been received, and no more call establishment information will be accepted.

See table 9.57/3GPP TS 04.08.

Message type: CALL PROCEEDING

Significance: local

Direction: network to mobile station

Table 9.57/3GPP TS 04.08: CALL PROCEEDING message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Call proceeding Message type M V 1 message type 10.4 D- Repeat Indicator Repeat Indicator C TV 1 10.5.4.22 04 Bearer capability 1 Bearer capability O TLV 3-15 10.5.4.5 04 Bearer capability 2 Bearer capability O TLV 3-15 10.5.4.5 1C Facility Facility O TLV 2-? 10.5.4.15 1E Progress indicator Progress indicator O TLV 4 10.5.4.21 8- Priority granted Priority Level O TV 1 10.5.1.11

#### 9.3.3.1 Repeat indicator

This information element is included if and only if bearer capability 1 IE and bearer capability 2 IE are both contained in the message.

#### 9.3.3.2 Bearer capability 1 and bearer capability 2

The bearer capability 1 information element is included if the network has to specify at least one of the negotiable parameters described in 3GPP TS 07.01, or if the bearer capability 1 information element received in the SETUP message included the "fixed network user rate" parameter.

When the bearer capability 1 information element is followed by the bearer capability 2 IE in the SETUP, the above rule applies to both bearer capability 1 IE and bearer capability 2 IE. Except those cases identified in 3GPP TS 07.01, if either bearer capability needs to be included, both shall be included.

#### 9.3.3.3 Facility

This information element may be used for functional operation of supplementary services.

#### 9.3.3.4 Progress Indicator

This information element may be included:

– in order to pass information about the call in progress e.g. in the event of interworking; and/or

– to make the MS attach the user connection for speech.

#### 9.3.3.5 Priority granted

The priority field is provided by the network in the case that eMLPP is used and the priority assigned by the network is not the same as that requested by the mobile station.

### 9.3.4 Congestion control

This message is sent by the network to indicate the establishment or termination of flow control on the transmission of USER INFORMATION messages.

See table 9.58/3GPP TS 04.08.

Message type: CONGESTION CONTROL

Significance: local (note)

Direction: network to mobile station

Table 9.58/3GPP TS 04.08: CONGESTION CONTROL message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Congestion control Message type M V 1 message type 10.4 Congestion level Congestion level M V 1/2 10.5.4.12 Spare half octet Spare half octet M V 1/2 10.5.1.8 08 Cause Cause O TLV 4-32 10.5.4.11

NOTE: This message has local significance, but may carry information of global significance.

#### 9.3.4.1 Cause

This information element is included if the user to user information has been discarded as a result of the congestion situation.

### 9.3.5 Connect

#### 9.3.5.1 Connect (network to mobile station direction)

This message is sent by the network to the calling mobile station to indicate call acceptance by the called user.

See table 9.59/3GPP TS 04.08.

Message type: CONNECT

Significance: global

Direction: network to mobile station

Table 9.59/3GPP TS 04.08: CONNECT message content(network to mobile station direction)

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Connect Message type M V 1 message type 10.4 1C Facility Facility O TLV 2-? 10.5.4.15 1E Progress indicator Progress indicator O TLV 4 10.5.4.21 4C Connected number Connected number O TLV 3-14 10.5.4.13 4D Connected subaddress Connected subaddress O TLV 2-23 10.5.4.14 7E User-user User-user O TLV 3-131 10.5.4.25
##### 9.3.5.1.1 Facility

This information element may be used for functional operation of supplementary services.

##### 9.3.5.1.2 Progress indicator

This information element may be included by the network:

– in order to pass information about the call in progress e.g. in the event of interworking; and/or

– to make the MS attach the user connection for speech.

##### 9.3.5.1.3 User-user

This information element may be included by the network if the remote user awarded the call included a user- user information element in the CONNECT message.

#### 9.3.5.2 Connect (mobile station to network direction)

This message is sent by the called mobile station to the network to indicate call acceptance by the called user.

See table 9.59a/3GPP TS 04.08.

Message type: CONNECT

Significance: global

Direction: mobile station to network

Table 9.59a/3GPP TS 04.08: CONNECT message content (mobile station to network direction)

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Connect Message type M V 1 message type 10.4 1C Facility Facility O TLV 2-? 10.5.4.15 4D Connected subaddress Connected subaddress O TLV 2-23 10.5.4.14 7E User-user User-user O TLV 3-131 10.5.4.25 7F SS version SS version indicator O TLV 2-3 10.5.4.24
##### 9.3.5.2.1 Facility

This information element may be used for functional operation of supplementary services.

##### 9.3.5.2.2 User-user

This information element is included when the answering mobile station wants to return user information to the calling remote user.

##### 9.3.5.2.3 SS version

This information element shall not be included if the facility information element is not present in this message.

This information element shall be included or excluded as defined in 3GPP TS 04.10. This information element should not be transmitted unless explicitly required by 3GPP TS 04.10.

### 9.3.6 Connect acknowledge

This message is sent by the network to the called mobile station to indicate that the mobile station has been awarded the call. It shall also be sent by the calling mobile station to the network to acknowledge the offered connection.

See table 9.60/3GPP TS 04.08.

Message type: CONNECT ACKNOWLEDGE

Significance: local

Direction: both

Table 9.60/3GPP TS 04.08: CONNECT ACKNOWLEDGE message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Connect acknowledge Message type M V 1 message type 10.4

### 9.3.7 Disconnect

#### 9.3.7.1 Disconnect (network to mobile station direction)

This message is sent by the network to indicate that the end-to-end connection is cleared.

See table 9.61/3GPP TS 04.08.

Message type: DISCONNECT

Significance: global

Direction: network to mobile station

Table 9.61/3GPP TS 04.08: DISCONNECT message content (network to mobile station direction)

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Disconnect

Message type

M

V

1

message type

10.4

Cause

Cause

M

LV

3-31

10.5.4.11

1C

Facility

Facility

O

TLV

2-?

10.5.4.15

1E

Progress indicator

Progress indicator

O

TLV

4

10.5.4.21

7E

User-user

User-user

O

TLV

3-131

10.5.4.25

7B

Allowed actions $(CCBS)$

Allowed actions

O

TLV

3

10.5.4.26

##### 9.3.7.1.1 Facility

This information element may be used for functional operation of supplementary services, such as the user-user service.

##### 9.3.7.1.2 Progress indicator

This information element is included by the network to make the MS attach the user connection for speech and react in a specific way during call clearing (see sub-clause 5.4.4).

##### 9.3.7.1.3 User-user

This information element may be included by the network when the remote user initiates call clearing and included a user-user information element in the DISCONNECT message.

##### 9.3.7.1.4 Allowed actions $(CCBS)$

This information element may be included by the network to inform the MS about further possible reactions.

#### 9.3.7.2 Disconnect (mobile station to network direction)

This message is sent by the mobile station to request the network to clear an end-to-end connection.

See table 9.61a/3GPP TS 04.08.

Message type: DISCONNECT

Significance: global

Direction: mobile station to network

Table 9.61a/3GPP TS 04.08: DISCONNECT message content (mobile station to network direction)

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Disconnect Message type M V 1 message type 10.4 Cause Cause M LV 3-31 10.5.4.11 1C Facility Facility O TLV 2-? 10.5.4.15 7E User-user User-user O TLV 3-131 10.5.4.25 7F SS version SS version indicator O TLV 2-3 10.5.4.24
##### 9.3.7.2.1 Facility

This information element may be used for functional operation of supplementary services, such as the user-user service.

##### 9.3.7.2.2 User-user

This information element is included when the mobile station initiates call clearing and wants to pass user information to the remote user at call clearing time.

##### 9.3.7.2.3 SS version

This information element shall not be included if the facility information element is not present in this message.

This information element shall be included or excluded as defined in 3GPP TS 04.10. This information element should not be transmitted unless explicitly required by 3GPP TS 04.10.

### 9.3.8 Emergency setup

This message is sent from the mobile station to initiate emergency call establishment.

See table 9.62/3GPP TS 04.08.

Message type: EMERGENCY SETUP

Significance: global

Direction: mobile station to network

Table 9.62/3GPP TS 04.08: EMERGENCY SETUP message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Emergency setup Message type M V 1 message type 10.4 04 Bearer capability Bearer capability O TLV 3-9 10.5.4.5

#### 9.3.8.1 Bearer capability

If the element is not included, the network shall by default assume speech and select full rate speech version 1. If this information element is included, it shall indicate speech, the appropriate speech version(s) and have the appropriate value of radio channel requirement field.

This information element shall be included by an ME supporting CTM text telephony.

### 9.3.9 Facility

#### 9.3.9.1 Facility (network to mobile station direction)

This message is sent by the network to the mobile station to request or acknowledge a supplementary service. The supplementary service to be invoked and its associated parameters are specified in the facility information element.

See table 9.62a/3GPP TS 04.08.

Message type: FACILITY

Significance: local (note 1)

Direction: network to mobile station

Table 9.62a/3GPP TS 04.08: FACILITY message content (network to mobile station direction)

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Facility Message type M V 1 message type 10.4 Facility (note 2) Facility M LV 1-? 10.5.4.15

NOTE 1: This message has local significance; however, it may carry information of global significance.

NOTE 2: The facility information element has no upper length limit except that given by the maximum number of octets in a L3 message, see 3GPP TS 04.06.

#### 9.3.9.2 Facility (mobile station to network direction)

This message is sent by the mobile station to the network to request or acknowledge a supplementary service. The supplementary service to be invoked and its associated parameters are specified in the facility information element.

See table 9.62b/3GPP TS 04.08.

Message type: FACILITY

Significance: local (note 1)

Direction: mobile station to network

Table 9.62b/3GPP TS 04.08: FACILITY message content (mobile station to network direction)

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Facility Message type M V 1 message type 10.4 Facility (note 2) Facility M LV 1-? 10.5.4.15 7F SS version SS version indicator O TLV 2-3 10.5.4.24

NOTE 1: This message has local significance; however, it may carry information of global significance.

NOTE 2: The facility information element has no upper length limit except that given by the maximum number of octets in a L3 message, see 3GPP TS 04.06.

##### 9.3.9.2.1 SS version

This information element shall be included or excluded as defined in 3GPP TS 04.10. This information element should not be transmitted unless explicitly required by 3GPP TS 04.10.

### 9.3.10 Hold

This message is sent by the mobile user to request the hold function for an existing call.

See table 9.62c/3GPP TS 04.08 for the content of the HOLD message.

For the use of this message, see 3GPP TS 04.10.

Message type: HOLD

Significance: local

Direction: mobile station to network

Table 9.62c/3GPP TS 04.08: HOLD message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Hold Message type M V 1 message type 10.4

### 9.3.11 Hold Acknowledge

This message is sent by the network to indicate that the hold function has been successfully performed.

See table 9.62d/3GPP TS 04.08 for the content of the HOLD ACKNOWLEDGE message.

For the use of this message, see 3GPP TS 04.10.

Message type: HOLD ACKNOWLEDGE

Significance: local

Direction: network to mobile station

Table 9.62d/3GPP TS 04.08: HOLD ACKNOWLEDGE message content

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Hold Acknowledge

Message type

M

V

1

message type

10.4

### 9.3.12 Hold Reject

This message is sent by the network to indicate the denial of a request to hold a call.

See table 9.62e/3GPP TS 04.08 for the content of the HOLD REJECT message.

For the use of this message, see 3GPP TS 04.10.

Message type: HOLD REJECT

Significance: local

Direction: network to mobile station

Table 9.62e/3GPP TS 04.08: HOLD REJECT message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Hold Reject Message type M V 1 message type 10.4 Cause 10.5.4.11 M LV 3-31

### 9.3.13 Modify

This message is sent by the mobile station to the network or by the network to the mobile station to request a change in bearer capability for a call.

See table 9.63/3GPP TS 04.08.

Message type: MODIFY

Significance: global

Direction: both

Table 9.63/3GPP TS 04.08: MODIFY message content

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Modify

Message type

M

V

1

message type

10.4

Bearer capability

Bearer capability

M

LV

2-14

10.5.4.5

7C

Low layer comp.

Low layer comp.

O

TLV

2-15

10.5.4.18

7D

High layer comp.

High layer comp.

O

TLV

2-5

10.5.4.16

A3

Reverse call setup

Reverse call setup

O

T

1

direction

direction

10.5.4.22a

#### 9.3.13.1 Low layer compatibility

This information element shall be included if it was included in the initial SETUP message.

#### 9.3.13.2 High layer compatibility

This information element shall be included if it was included in the initial SETUP message.

#### 9.3.13.3 Reverse call setup direction

This information element is included or omitted in the mobile to network direction according to the rules defined in sub-clause 5.3.4.3.1.

### 9.3.14 Modify complete

This message is sent by the mobile station to the network or by the network to the mobile station to indicate completion of a request to change bearer capability for a call.

See table 9.64/3GPP TS 04.08.

Message type: MODIFY COMPLETE

Significance: global

Direction: both

Table 9.64/3GPP TS 04.08: MODIFY COMPLETE message content

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Modify complete

Message type

M

V

1

message type

10.4

Bearer capability

Bearer capability

M

LV

2-14

10.5.4.5

7C

Low layer comp.

Low layer comp.

O

TLV

2-15

10.5.4.18

7D

High layer comp.

High layer comp.

O

TLV

2-5

10.5.4.16

A3

Reverse call setup

Reverse call setup

O

T

1

direction

direction

10.5.4.22a

#### 9.3.14.1 Low layer compatibility

This information element shall be included if it was included in the initial SETUP message.

#### 9.3.14.2 High layer compatibility

This information element shall be included if it was included in the initial SETUP message.

#### 9.3.14.3 Reverse call setup direction

This information element is included or omitted according to the rules defined in sub-clause 5.3.4.3.2.

### 9.3.15 Modify reject

This message is sent by the mobile station to the network or by the network to the mobile station to indicate failure of a request to change the bearer capability for a call.

See table 9.65/3GPP TS 04.08.

Message type: MODIFY REJECT

Significance: global

Direction: both

Table 9.65/3GPP TS 04.08: MODIFY REJECT message content

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Modify reject

Message type

M

V

1

message type

10.4

Bearer capability

Bearer capability

M

LV

2-14

10.5.4.5

Cause

Cause

M

LV

3-31

10.5.4.11

7C

Low layer comp.

Low layer comp.

O

TLV

2-15

10.5.4.18

7D

High layer comp.

High layer comp.

O

TLV

2-5

10.5.4.16

#### 9.3.15.1 Low layer compatibility

This information element shall be included if it was included in the initial SETUP message.

#### 9.3.15.2 High layer compatibility

This information element shall be included if it was included in the initial SETUP message.

### 9.3.16 Notify

This message is sent either from the mobile station or from the network to indicate information pertaining to a call, such as user suspended.

See table 9.66/3GPP TS 04.08.

Message type: NOTIFY

Significance: access

Direction: both

Table 9.66/3GPP TS 04.08: NOTIFY message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Notify Message type M V 1 message type 10.4 Notification indicator Notification indicator M V 1 10.5.4.20

### 9.3.17 Progress

This message is sent from the network to the mobile station to indicate the progress of a call in the event of interworking or in connection with the provision of in-band information/patterns.

See table 9.67/3GPP TS 04.08.

Message type: PROGRESS

Significance: global

Direction: network to mobile station

Table 9.67/3GPP TS 04.08: PROGRESS message content

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Progress

Message type

M

V

1

message type

10.4

Progress indicator

Progress indicator

M

LV

3

10.5.4.21

7E

User-user

User-user

O

TLV

3-131

10.5.4.25

#### 9.3.17.1 User-user

This information element is included when the PROGRESS message is sent by the network when the call has been cleared by the remote user before it reached the active state to indicate that the remote user wants to pass user information at call clearing time.

### 9.3.17a CC-Establishment $(CCBS)$

A mobile station that does not support the "Network initiated MO call" option shall treat this message as a message with message type not defined for the PD.

This message is sent from the network to the mobile station to provide information on the call that the mobile station should attempt to establish.

See Table 9.67a/3GPP TS 04.08.

Message type: CC-ESTABLISHMENT

Significance: local

Direction: network to mobile station

Table 9.67a/3GPP TS 04.08: CC-Establishment message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 CC-Establishment Message type M V 1 message type 10.4 Setup container Container M LV 3-n 10.5.4.22a

NOTE: From the 4th IE onwards the message is coded in the same way as the SETUP message in MS to network direction from the 4th IE onwards.

#### 9.3.17a.2 Setup container

This information element contains the contents of a SETUP message (Mobile Station to Network).

### 9.3.17b CC-Establishment confirmed $(CCBS)$

A Network that does not support the "Network initiated MO call" option shall treat this message as a message with message type not defined for the PD.

This message is sent by the mobile station to the network to indicate the requested channel characteristics for the call which may be initiated by the mobile station.

See Table 9.67b/3GPP TS 04.08.

Message type: CC-ESTABLISHMENT CONFIRMED

Significance: local

Direction: mobile station to network

Table 9.67b/3GPP TS 04.08: CC-ESTABLISHMENT CONFIRMED message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 CC-Establishment confirmed Message type M V 1 message type 10.4 D- Repeat Indicator Repeat Indicator C TV 1 10.5.4.22 04 Bearer capability 1 Bearer capability M TLV 3-10 10.5.4.5 04 Bearer capability 2 Bearer capability O TLV 3-10 10.5.4.5 08 Cause Cause O TLV 4-32 10.5.4.11

#### 9.3.17b.1 Repeat indicator

The repeat indicator information element shall be included if bearer capability 1 information element and bearer capability 2 IE are both included in the message.

#### 9.3.17b.2 Bearer capability 1 and bearer capability 2

If, in any subsequent SETUP message to be sent on this transaction the bearer capability 1 information element is to be followed by the bearer capability 2 IE, then the bearer capability 2 IE shall be included in this message.

#### 9.3.17b.9 Cause

This information element is included if the mobile station is compatible but the user is busy.

### 9.3.18 Release

#### 9.3.18.1 Release (network to mobile station direction)

This message is sent, from the network to the mobile station to indicate that the network intends to release the transaction identifier, and that the receiving equipment shall release the transaction identifier after sending RELEASE COMPLETE.

See table 9.68/3GPP TS 04.08.

Message type: RELEASE

Significance: local (note)

Direction: network to mobile station

Table 9.68/3GPP TS 04.08: RELEASE message content (network to mobile station direction)

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Release Message type M V 1 message type 10.4 08 Cause Cause O TLV 4-32 10.5.4.11 08 Second cause Cause O TLV 4-32 10.5.4.11 1C Facility Facility O TLV 2-? 10.5.4.15 7E User-user User-user O TLV 3-131 10.5.4.25

NOTE: This message has local significance; however, it may carry information of global significance when used as the first call clearing message.

##### 9.3.18.1.1 Cause

This information element shall be included if this message is used to initiate call clearing.

##### 9.3.18.1.2 Second cause

This information element may be included under the conditions described in sub-clause 5.4.4.1.2.3 "Abnormal cases" (Clearing initiated by the network).

##### 9.3.18.1.3 Facility

This information element may be included for functional operation of supplementary services.

##### 9.3.18.1.4 User-user

This information element may be included in the network to mobile station direction, when the RELEASE message is used to initiate call clearing, in order to transport user-user information from the remote user.

#### 9.3.18.2 Release (mobile station to network direction)

This message is sent from the mobile station to the network to indicate that the mobile station intends to release the transaction identifier, and that the receiving equipment shall release the transaction identifier after sending RELEASE COMPLETE.

See table 9.68a/3GPP TS 04.08.

Message type: RELEASE

Significance: local (note)

Direction: mobile station to network direction

Table 9.68a/3GPP TS 04.08: RELEASE message content (mobile station to network direction)

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Release Message type M V 1 message type 10.4 08 Cause Cause O TLV 4-32 10.5.4.11 08 Second cause Cause O TLV 4-32 10.5.4.11 1C Facility Facility O TLV 2-? 10.5.4.15 7E User-user User-user O TLV 3-131 10.5.4.25 7F SS version SS version indicator O TLV 2-3 10.5.4.24

NOTE: This message has local significance; however, it may carry information of global significance when used as the first call clearing message.

##### 9.3.18.2.1 Cause

This information element shall be included if this message is used to initiate call clearing.

##### 9.3.18.2.2 Second cause

This information element may be included under the conditions described in sub-clause 5.4.3.5 "Abnormal cases" (Clearing initiated by the mobile station).

##### 9.3.18.2.3 Facility

This information element may be included for functional operation of supplementary services.

##### 9.3.18.2.4 User-user

This information element is included when the RELEASE message is used to initiate call clearing and the mobile station wants to pass user information to the remote user at call clearing time.

##### 9.3.18.2.5 SS version

This information element shall not be included if the facility information element is not present in this message.

This information element shall be included or excluded as defined in 3GPP TS 04.10. This information element should not be transmitted unless explicitly required by 3GPP TS 04.10.

### 9.3.18a Recall $(CCBS)$

A mobile station that does not support the "Network initiated MO call" option shall treat this message as a message with message type not defined for the PD.

This message is sent from the network to the mobile station to initiate the sending of the SETUP message. In addition it provides information for user notification.

See Table 9.68b/3GPP TS 04.08.

Message type: RECALL

Significance: local

Direction: network to mobile station

Table 9.68b/3GPP TS 04.08: Recall message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Recall Message type M V 1 message type 10.4 Recall Type Recall Type M V 1 10.5.4.21a Facility Facility M LV 2-n 10.5.4.15

#### 9.3.18a.1 Recall Type

The purpose of the recall type information element is to describe the reason for the recall.

#### 9.3.18a.2 Facility

The information element shall be included for functional operation of supplementary services.

### 9.3.19 Release complete

#### 9.3.19.1 Release complete (network to mobile station direction)

This message is sent from the network to the mobile station to indicate that the network has released the transaction identifier and that the mobile station shall release the transaction identifier.

See table 9.69/3GPP TS 04.08.

Message type: RELEASE COMPLETE

Significance: local (note)

Direction: network to mobile station direction

Table 9.69/3GPP TS 04.08: RELEASE COMPLETE message content (network to mobile station direction)

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Release complete Message type M V 1 message type 10.4 08 Cause Cause O TLV 4-32 10.5.4.11 1C Facility Facility O TLV 2-? 10.5.4.15 7E User-user User-user O TLV 3-131 10.5.4.25

NOTE: This message has local significance; however, it may carry information of global significance when used as the first call clearing message.

##### 9.3.19.1.1 Cause

This information element shall be included if the message is used to initiate call clearing.

##### 9.3.19.1.2 Facility

This information element may be included for functional operation of supplementary services.

##### 9.3.19.1.3 User-user

This information element is included in the network to mobile station direction, when the RELEASE COMPLETE message is used to initiate call clearing, in order to transport user-user information from the remote user.

#### 9.3.19.2 Release complete (mobile station to network direction)

This message is sent from the mobile station to the network to indicate that the mobile station has released the transaction identifier and that the network shall release the transaction identifier.

See table 9.69a/3GPP TS 04.08.

Message type: RELEASE COMPLETE

Significance: local (note)

Direction: mobile station to network direction

Table 9.69a/3GPP TS 04.08: RELEASE COMPLETE message content (mobile station to network direction)

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Release complete Message type M V 1 message type 10.4 08 Cause Cause O TLV 4-32 10.5.4.11 1C Facility Facility O TLV 2-? 10.5.4.15 7E User-user User-user O TLV 3-131 10.5.4.25 7F SS version SS version indicator O TLV 2-3 10.5.4.24

NOTE: This message has local significance; however, it may carry information of global significance when used as the first call clearing message.

##### 9.3.19.2.1 Cause

This information element shall be included if the message is used to initiate call clearing.

##### 9.3.19.2.2 Facility

This information element may be included for functional operation of supplementary services.

##### 9.3.19.2.3 User-user

This information element is included in the mobile station to network direction when the RELEASE COMPLETE message is used to initiate call clearing and the mobile station wants to pass user information to the remote user at call clearing time.

##### 9.3.19.2.4 SS version.

This information element shall not be included if the facility information element is not present in this message.

This information element shall be included or excluded as defined in 3GPP TS 04.10. This information element should not be transmitted unless explicitly required by 3GPP TS 04.10.

### 9.3.20 Retrieve

This message is sent by the mobile user to request the retrieval of a held call.

See table 9.69b/3GPP TS 04.08 for the content of the RETRIEVE message.

For the use of this message, see 3GPP TS 04.10.

Message type: RETRIEVE

Significance: local

Direction: mobile station to network

Table 9.69b/3GPP TS 04.08: RETRIEVE message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Retrieve Message type M V 1 message type 10.4

### 9.3.21 Retrieve Acknowledge

This message is sent by the network to indicate that the retrieve function has been successfully performed.

See table 9.69c/3GPP TS 04.08 for the content of the RETRIEVE ACKNOWLEDGE message.

For the use of this message, see 3GPP TS 04.10.

Message type: RETRIEVE ACKNOWLEDGE

Significance: local

Direction: network to mobile station

Table 9.69c/3GPP TS 04.08: RETRIEVE ACKNOWLEDGE message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Retrieve Acknowledge Message type M V 1 message type 10.4

### 9.3.22 Retrieve Reject

This message is sent by the network to indicate the inability to perform the requested retrieve function.

See table 9.69d/3GPP TS 04.08 for the content of the RETRIEVE REJECT message.

For the use of this message, see 3GPP TS 04.10.

Message type: RETRIEVE REJECT

Significance: local

Direction: network to mobile station

Table 9.69d/3GPP TS 04.08: RETRIEVE REJECT message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Retrieve Reject Message type M V 1 message type 10.4 Cause 10.5.4.11 M LV 3-31

### 9.3.23 Setup

#### 9.3.23.1 Setup (mobile terminated call establishment)

This message is sent by the network to the mobile station to initiate a mobile terminated call establishment.

See table 9.70/3GPP TS 04.08.

Message type: SETUP

Significance: global

Direction: network to mobile station

Table 9.70/3GPP TS 04.08: SETUP message content (network to mobile station direction)

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Setup

Message type

M

V

1

message type

10.4

D-

BC repeat indicator

Repeat indicator

C

TV

1

10.5.4.22

04

Bearer capability 1

Bearer capability

O

TLV

3-15

10.5.4.5

04

Bearer capability 2

Bearer capability

O

TLV

3-15

10.5.4.5

1C

Facility

Facility

O

TLV

2-?

10.5.4.15

1E

Progress indicator

Progress indicator

O

TLV

4

10.5.4.21

34

Signal

Signal

O

TV

2

10.5.4.23

5C

Calling party BCD

Calling party BCD num.

O

TLV

3-14

number

10.5.4.9

5D

Calling party sub-

O

TLV

2-23

10.5.4.10

5E

Called party BCD

Called party BCD num.

O

TLV

3-19

number

10.5.4.7

6D

Called party sub-

O

TLV

2-23

10.5.4.8

74

Redirecting party BCD number

Redirecting party BCD num.

10.5.4.21a

O

TLV

3-19

75

10.5.4.21b

O

TLV

2-23

D-

LLC repeat indicator

Repeat indicator

O

TV

1

10.5.4.22

7C

Low layer

Low layer comp.

O

TLV

2-15

compatibility I

10.5.4.18

7C

Low layer

Low layer comp.

C

TLV

2-15

compatibility II

10.5.4.18

D-

HLC repeat indicator

Repeat indicator

O

TV

1

10.5.4.22

7D

High layer

High layer comp.

O

TLV

2-5

compatibility i

10.5.4.16

7D

High layer

High layer comp.

C

TLV

2-5

compatibility ii

10.5.4.16

7E

User-user

User-user

O

TLV

3-35

10.5.4.25

8-

Priority

Priority Level

O

TV

1

10.5.1.11

19

O

TLV

3

10.5.4.26

##### 9.3.23.1.1 BC repeat indicator

The BC repeat indicator information element is included if and only if bearer capability 1 information element and bearer capability 2 IE are both present in the message.

##### 9.3.23.1.2 Bearer capability 1 and bearer capability 2

The bearer capability 1 information element may be omitted in the case where the mobile subscriber is allocated only one directory number for all services (ref.: 3GPP TS 09.07). The bearer capability 2 IE is missing at least if the bearer capability 1 IE is missing.

##### 9.3.23.1.3 Facility

This information element may be included for functional operation of supplementary services.

##### 9.3.23.1.4 Progress indicator

This information element is included by the network

– in order to pass information about the call in progress e.g. in the event of interworking; and/or

– to make the MS attach the user connection for speech.

##### 9.3.23.1.4a Called party BCD number

For all bands except for PCS1900, the maximum length of this IE sent by the network shall be 13 octets

Included in the Network-to-mobile station direction if the calling user includes a called party subaddress information element in the SETUP message.

##### 9.3.23.1.6 LLC repeat indicator

The LLC repeat indicator information element is included if and only if both following conditions hold:

– The BC repeat indicator IE is contained in the message.

– The low layer compatibility I IE is contained in the message.

If included, the LLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE.

##### 9.3.23.1.7 Low layer compatibility I

Included in the network-to-mobile station direction if the calling user specified a low layer compatibility.

##### 9.3.23.1.8 Low layer compatibility II

Included if and only if the LLC repeat indicator information element is contained in the message.

##### 9.3.23.1.9 HLC repeat indicator

The HLC repeat indicator information element is included if and only both following conditions hold:

– The BC repeat indicator IE is contained in the message.

– The high layer compatibility i IE is contained in the message.

If included, the HLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE.

##### 9.3.23.1.10 High layer compatibility i

Included in the network-to-mobile station direction if the calling user specified a high layer compatibility.

##### 9.3.23.1.11 High layer compatibility ii

Included if and only if the HLC repeat indicator information element is contained in the message.

##### 9.3.23.1.12 User-user

May be included in the network to called mobile station direction when the calling remote user included a user-user information element in the SETUP message.

##### 9.3.23.1.13 Redirecting party BCD number

May be included in the network to called mobile station direction when the call has been redirected.

May be included in the network to called mobile station direction when the calling remote user included a called party subaddress in the SETUP message and the call has been redirected

##### 9.3.23.1.15 Priority

May be included by the network to indicate the priority of the incoming call if eMLPP is used.

##### 9.3.23.1.16 Alert $(Network Indication of Alerting in the MS )$

May be included by the network to give some indication about alerting (category or level). If supported in the MS, this optional indication is to be used by the MS as specified in 3GPP TS 02.07.

#### 9.3.23.2 Setup (mobile originating call establishment)

This message is sent from the mobile station to the network to initiate a mobile originating call establishment.

See table 9.70a/3GPP TS 04.08.

Message type: SETUP

Significance: global

Direction: mobile station to network

Table 9.70a/3GPP TS 04.08: SETUP message content (mobile station to network direction)

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Setup

Message type

M

V

1

message type

10.4

D-

BC repeat indicator

Repeat indicator

C

TV

1

10.5.4.22

04

Bearer capability 1

Bearer capability

M

TLV

3-16

10.5.4.5

04

Bearer capability 2

Bearer capability

O

TLV

3-16

10.5.4.5

1C

Facility(simple recall alignment)

Facility

O

TLV

2-

10.5.4.15

5D

Calling party sub-

O

TLV

2-23

10.5.4.10

5E

Called party BCD

Called party BCD num.

M

TLV

3-43

number

10.5.4.7

6D

Called party sub-

O

TLV

2-23

10.5.4.8

D-

LLC repeat indicator

Repeat indicator

O

TV

1

10.5.4.22

7C

Low layer

Low layer comp.

O

TLV

2-15

compatibility I

10.5.4.18

7C

Low layer

Low layer comp.

O

TLV

2-15

compatibility II

10.5.4.18

D-

HLC repeat indicator

Repeat indicator

O

TV

1

10.5.4.22

7D

High layer

High layer comp.

O

TLV

2-5

compatibility i

10.5.4.16

7D

High layer

High layer comp.

O

TLV

2-5

compatibility ii

10.5.4.16

7E

User-user

User-user

O

TLV

3-35

10.5.4.25

7F

SS version

SS version indicator

O

TLV

2-3

10.5.4.24

A1

CLIR suppression

CLIR suppression

C

T

1

10.5.4.11a

A2

CLIR invocation

CLIR invocation

C

T

1

10.5.4.11b

15

CC capabilities

Call Control Capabilities

O

TLV

3

10.5.4.5a

1D

Facility $(CCBS)$

Facility

O

TLV

2-?

10.5.4.15

1B

Facility (recall alignment

Facility

O

TLV

2-?

Not essential) $(CCBS)$

10.5.4.15

##### 9.3.23.2.1 BC repeat indicator

The BC repeat indicator information element is included if and only if bearer capability 1 IE and bearer capability 2 IE are both present in the message.

##### 9.3.23.2.2 Facility

The information element may be included for functional operation of supplementary services.

Three different codings of this IE exist, for further details see 3GPP TS 04.10.

##### 9.3.23.2.3 LLC repeat indicator

The LLC repeat indicator information element is included if and only if both following conditions hold:

– The BC repeat indicator IE is contained in the message.

– The low layer compatibility I IE is contained in the message.

If included, the LLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE.

##### 9.3.23.2.4 Low layer compatibility I

The information element is included in the MS-to-network direction when the calling MS wants to pass low layer compatibility information to the called user.

##### 9.3.23.2.5 Low layer compatibility II

Included if and only if the LLC repeat indicator information element is contained in the message.

##### 9.3.23.2.6 HLC repeat indicator

The HLC repeat indicator information element is included if and only if both following conditions hold:

– The BC repeat indicator IE is contained in the message.

– The high layer compatibility i IE is contained in the message.

If included, the HLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE.

##### 9.3.23.2.7 High layer compatibility i

The information element is included when the calling MS wants to pass high layer compatibility information to the called user.

##### 9.3.23.2.8 High layer compatibility ii

Included if and only if the HLC repeat indicator information element is contained in the message.

##### 9.3.23.2.9 User-user

The information element is included in the calling mobile station to network direction when the calling mobile station wants to pass user information to the called remote user.

##### 9.3.23.2.10 SS version

This information element shall not be included if the facility information element is not present in this message.

This information element shall be included or excluded as defined in 3GPP TS 04.10. This information element should not be transmitted unless explicitly required by 3GPP TS 04.10.

##### 9.3.23.2.11 CLIR suppression

The information element may be included by the MS (see 3GPP TS 04.81). If this information element is included the CLIR invocation IE shall not be included.

##### 9.3.23.2.12 CLIR invocation

The information element may be included by the MS (see 3GPP TS 04.81). If this information element is included the CLIR suppression IE shall not be included.

##### 9.3.23.2.13 CC Capabilities

This information element may be included by the mobile station to indicate its call control capabilities.

### 9.3.23a Start CC $(CCBS)$

A Network that does not support the "Network initiated MO call" option shall treat this message as a message with message type not defined for the PD.

This message is sent by the mobile station to the network to open a Call Control transaction which the network has requested the mobile station to open.

See Table 9.70b/3GPP TS 04.08.

Message type: START CC

Significance: local

Direction: mobile station to network

Table 9.70b/3GPP TS 04.08: START CC message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Start CC Message type M V 1 message type 10.4 15 CC Capabilities Call Control Capabilities O TLV 3 10.5.4.5a

#### 9.3.23a.1 CC Capabilities

This information element may be included by the mobile station to indicate its call control capabilities

### 9.3.24 Start DTMF

This message is sent by the mobile station to the network and contains the digit the network should reconvert back into a DTMF tone which is then applied towards the remote user.

See table 9.71/3GPP TS 04.08.

Message type: START DTMF

Significance: local

Direction: mobile station to network

Table 9.71/3GPP TS 04.08: START DTMF message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Start DTMF Message type M V 1 message type 10.4 2C Keypad facility Keypad facility M TV 2 10.5.4.17

### 9.3.25 Start DTMF Acknowledge

This message is sent by the network to the mobile station to indicate the successful initiation of the action requested by the START DTMF message (conversion of the digit contained in this message into a DTMF tone).

See table 9.72/3GPP TS 04.08.

Message type: START DTMF ACKNOWLEDGE

Significance: local

Direction: network to mobile station

Table 9.72/3GPP TS 04.08: START DTMF ACKNOWLEDGE message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Start DTMF acknowledge Message type M V 1 message type 10.4 2C Keypad facility Keypad facility M TV 2 10.5.4.17

This information element contains the digit corresponding to the DTMF tone that the network applies towards the remote user.

### 9.3.26 Start DTMF reject

This message is sent by the network to the mobile station, if the network can not accept the START DTMF message.

See table 9.73/3GPP TS 04.08.

Message type: START DTMF REJECT

Significance: local

Direction: network to mobile station

Table 9.73/3GPP TS 04.08: START DTMF REJECT message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Start DTMF reject Message type M V 1 message type 10.4 Cause Cause M LV 3-31 10.5.4.11

### 9.3.27 Status

This message is sent by the mobile station or the network at any time during a call to report certain error conditions listed in clause 8. It shall also be sent in response to a STATUS ENQUIRY message.

See table 9.74/3GPP TS 04.08.

Message type: STATUS

Significance: local

Direction: both

Table 9.74/3GPP TS 04.08: STATUS message content

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Status

Message type

M

V

1

message type

10.4

Cause

Cause

M

LV

3-31

10.5.4.11

Call state

Call state

M

V

1

10.5.4.6

24

Auxiliary states

Auxiliary states

O

TLV

3

10.5.4.4

#### 9.3.27.1 Auxiliary states

The information element is included if and only if the call state is "active" or "mobile originating modify" and any auxiliary state is different from "idle". For the definition of the auxiliary states see 3GPP TS 04.83 and 3GPP TS 04.84

### 9.3.28 Status enquiry

This message is sent by the mobile station or the network at any time to solicit a STATUS message from the peer layer 3 entity. Sending of STATUS message in response to a STATUS ENQUIRY message is mandatory.

See table 9.75/3GPP TS 04.08.

Message type: STATUS ENQUIRY

Significance: local

Direction: both

Table 9.75/3GPP TS 04.08: STATUS ENQUIRY message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Status enquiry Message type M V 1 message type 10.4

### 9.3.29 Stop DTMF

This message is sent by a mobile station to the network and is used to stop the DTMF tone sent towards the remote user.

See table 9.76/3GPP TS 04.08.

Message type: STOP DTMF

Significance: local

Direction: mobile station to network

Table 9.76/3GPP TS 04.08: STOP DTMF message content

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

Stop DTMF

Message type

M

V

1

message type

10.4

### 9.3.30 Stop DTMF acknowledge

This message is sent by the network to the mobile station to indicate that the sending of the DTMF tone has been stopped.

See table 9.77/3GPP TS 04.08.

Message type: STOP DTMF ACKNOWLEDGE

Significance: local

Direction: network to mobile station

Table 9.77/3GPP TS 04.08: STOP DTMF ACKNOWLEDGE message content

 IEI Information element Type / Reference Presence Format Length Call control Protocol discriminator M V 1/2 protocol discriminator 10.2 Transaction identifier Transaction identifier M V 1/2 10.3.2 Stop DTMF acknowledge Message type M V 1 message type 10.4

### 9.3.31 User information

This message is sent by the mobile station to the network to transfer information to the remote user. This message is also sent by the network to the mobile station to deliver information transferred from the remote user. This message is used if the user-to-user transfer is part of an allowed information transfer as defined in 3GPP TS 04.10.

See table 9.78/3GPP TS 04.08.

Message type: USER INFORMATION

Significance: access

Direction: both

Table 9.78/3GPP TS 04.08: USER INFORMATION message content

IEI

Information element

Type / Reference

Presence

Format

Length

Call control

Protocol discriminator

M

V

1/2

protocol discriminator

10.2

Transaction identifier

Transaction identifier

M

V

1/2

10.3.2

User Information

Message type

M

V

1

message type

10.4

User-user

User-user

M

LV

3-130

10.5.4.25

A0

More data

More data

O

T

1

10.5.4.19

#### 9.3.31.1 User-user

Some networks may only support a maximum length of 35 octets. Procedures for interworking are not currently defined and are for further study.

#### 9.3.31.2 More data

The information element is included by the sending user to indicate that another USER INFORMATION message pertaining to the same message block will follow.