A.3 Generic Common Messages

34.229-13GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification

A.3.1 200 OK for other requests than REGISTER or SUBSCRIBE

Header/param

Cond

Value/remark

Rel

Reference

Status-Line

RFC 3261 [15]

SIP-Version

SIP/2.0

Status-Code

200

Reason-Phrase

OK

Via

RFC 3261 [15]

via-parm

same value as received in request

Record-Route

order of the parameters in this header must be like in the respective rows

RFC 3261 [15]

rec-route

A1

<sip:pcscf.other.com;lr>, <sip:scscf.other.com;lr>, <sip:orig@scscf.3gpp.org;lr>, <sip:SS P-CSCF address: protected server port of SS;lr>

A3

<sip:pcscf.other.com;lr>, <sip:scscf.other.com;lr>, <sip:orig@scscf.3gpp.org;lr>, <sip:SS P-CSCF address: unprotected server port of SS (optional);lr>

A2,A4,
A5

same value as received in the request (if present in the request)

Note: for requests other than INVITE it is not regulated if and what the UE writes into this header in a response.

A6

<sip:orig@ecscf.other.com;lr>, <sip:SS P-CSCF address:protected server port of SS;lr>

A7

<sip:orig@ecscf.other.com;lr>, <sip:SS P-CSCF address:unprotected server port of SS;lr>

A1 AND A23

not present

A2 AND A23

any value if present

From

RFC 3261 [15]

addr-spec

same value as received in request

tag

same value as received in request

To

RFC 3261 [15]

addr-spec

same value as received in request

tag

same value as received in request or any value added if missing from request

P-Asserted-Identity

A6

RFC 3325 [89]

addr-spec

A tel URI that can be recognized as valid emergency numbers if dialled by the user are specified in 3GPP TS 22.101 [39].
The emergency numbers 112 and 911 are stored on the ME, in accordance with 3GPP TS 22.101 [39]

uri-parameter

lr

Contact

A1,A2
A3,A4

RFC 3261 [15]
RFC 5627 [61]

addr-spec

A1,A3

px_IMS_CalleeContactUri

A2 AND NOT A9

SIP URI with IP address or FQDN and protected server port of UE

A4 AND NOT A9

SIP URI with IP address or FQDN and unprotected server port of UE

A2 AND A9

Public GRUU as obtained during registration as pub-gruu contact parameter of the 200 OK for REGISTER response

A4 AND A9

Public GRUU as obtained during registration as pub-gruu contact parameter of the 200 OK for REGISTER response

A1 AND A5

MO call has been established:
px_IMS_CalleeContactUri

MT call has been established:
contact address sent by SS in dialog creating INVITE

A2 AND A5

MO call has been established:
contact address sent by UE in dialog creating INVITE

MT call has been established:
contact address sent by UE in response to dialog creating INVITE (NOTE : The ‘transport’ url parameter may change, url parameters are not checked)

feature-param

A10

audio

A18 AND (A19 OR A20)

video

IR.94 [134]

A11 AND A14 AND (A15 OR A16)

audio

Call-ID

RFC 3261 [15]

callid

same value as received in request

Call-Info

A12

RFC 8147 [149]

cid URL

<cid:psap@3gpp.org>

Rel-14

purpose

EmergencyCallData.Control

CSeq

RFC 3261 [15]

value

same value as received in request

P-Access-Network-Info

A8

RFC 7315 [132]
RFC 7913 [154]

access-net-spec

A21

access network information and, if applicable, the cell ID

A22

access network information for NR, containing access-class parameter with value "3GPP-NR" or access-type parameter with value "3GPP-NR-FDD" or "3GPP-NR-TDD", and also containing the cell ID

Accept

A12

RFC 8147 [149]

media-range

application/sdp, application/pidf+xml, application/EmergencyCallData.Control+xml, application/emergencyCallData.eCall.MSD

Rel-14

Recv-Info

A12

RFC 8147 [149]

Info-package-type

emergencyCallData.eCall.MSD

Rel-14

Content-Type

A12

RFC 8147 [149]

media-type

multipart/mixed; boundary=boundary1

Rel-14

Content-Length

A10

RFC 3261 [15]

value

NOT A12

0

A12

length of message body

Message-body

A12

A13

—boundary1
Content-Type: application/EmergencyCallData.eCall.Control+xml
Content-ID: <psap@3gpp.org>
Content-Disposition: by-reference
<?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control">
<ack received="true" ref=" addr-spec of the Content-ID of MIME body part containing the MSD sent by the UE in INVITE"/>
</EmergencyCallData.control>
–boundary1

RFC 8147 [149]

A14

–boundary1
Content-Type: application/EmergencyCallData.eCall.Control+xml
Content-ID: <psap@3gpp.org>

Content-Disposition: by-reference
<?xml version="1.0" encoding="UTF-8"?>
<emergencyCallData.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control">
<ack received="false" ref=" addr-spec of the Content-ID of MIME body part containing the MSD sent by the UE in INVITE "/>
</EmergencyCallData.control>
–boundary1

RFC 8147 [149]

Condition

Explanation

A1

Response sent by SS for INVITE/UPDATE (IMS security, A.6a/2 TS 34.229-2 [5]))

A2

Response sent by UE for INVITE/UPDATE (IMS security, A.6a/2 TS 34.229-2 [5]))

A3

Response sent by SS for INVITE/UPDATE (GIBA, A.6a/1 TS 34.229-2 [5]))

A4

Response sent by UE for INVITE/UPDATE (GIBA, A.6a/1 TS 34.229-2 [5]))

A5

Any response sent by the UE within a dialog

A6

Response sent by SS for INVITE for emergency call or non-UE detectable emergency call

A7

Response sent by SS for INVITE for emergency call without emergency registration

A8

Any response sent by the UE within a dialog, except for CANCEL requests

A9

obtaining and using GRUUs in the Session Initiation Protocol (SIP) (A.4/53 3GPP TS 34.229-2 [5])

A10

Response sent by SS

A11

Response sent by UE

A12

Response sent by SS for INVITE for eCall over IMS session with either ACK or NACK

A13

Response sent by SS for INVITE for eCall over IMS session with ACK element = TRUE

A14

Response sent by SS for INVITE for eCall over IMS session with ACK element = FALSE

A15

UE supports audio media feature tag (A.12/56 3GPP TS 34.229-2 [5])

A16

UE uses E-UTRAN access and has received IMS voice over PS Session Supported Indication in the NAS ATTACH ACCEPT message as described in TS 24.301 [150], clauses 8.2.1 and 9.9.3.12A

A17

UE uses UTRAN/GERAN access and has received IMS voice over PS Session Supported Indication in the NAS ATTACH ACCEPT message as described in TS 24.008 [12], clauses 9.4.2 and 10.5.5.23

A18

UE supports video feature tag (A.12/32 3GPP TS 34.229-2 [5])

A19

Response sent by SS for INVITE

A20

Response sent by UE for INVITE

A21

UE uses E-UTRAN access (A.18/1 3GPP TS 34.229-2 [5])

A22

UE uses NR access (A.18/5 3GPP TS 34.229-2 [5])

A23

Response sent for re-INVITE within an established dialog

A.3.2 403 FORBIDDEN

Header/param

Cond

Value/remark

Rel

Reference

Status-Line

RFC 3261 [15]

SIP-Version

SIP/2.0

Status-Code

403

Reason-Phrase

Forbidden

Via

RFC 3261 [15]

via-parm

same value as received in the previous REGISTER message

To

RFC 3261 [15]

addr-spec

same value as received in the previous REGISTER message

tag

common to-tag (register)

From

RFC 3261 [15]

addr-spec

same value as received in the previous REGISTER message

Call-ID

RFC 3261 [15]

value

same value as received in the previous REGISTER message

CSeq

RFC 3261 [15]

value

same value as received in the previous REGISTER message

Content-Type

A1

RFC 3261 [15]

media-type

application/3gpp-ims+xml

Content-Length

RFC 3261 [15]

value

0

Message-body

A1

<?xml version="1.0" encoding="UTF-8"?>
<ims-3gpp version="1">
<alternative-service>
<type>emergency</type>
<action>anonymous-emergencycall</action>
<reason></reason>
</alternative-service>
</ims-3gpp>
(see NOTE 1)

RFC 3261 [15]

Condition

Explanation

A1

IMS emergency call for an anonymous emergency call

NOTE 1: This XML body is defined in Rel-14 TS 24.229 [10] and may be ignored by pre-Rel-14 UE.

A.3.3 202 Accepted

Header/param

Cond

Value/remark

Rel

Reference

Status-Line

RFC 3261 [15]

SIP-Version

SIP/2.0

Status-Code

202

Reason-Phrase

Accepted

Via

RFC 3261 [15]

via-parm

same value as received in request

From

RFC 3261 [15]

addr-spec

same value as received in request

tag

same value as received in request

To

RFC 3261 [15]

addr-spec

same value as received in request

tag

same value as received in request or common to-tag (message) added if missing from request

Call-ID

RFC 3261 [15]

callid

same value as received in request

CSeq

RFC 3261 [15]

value

same value as received in request

Content-Length

optional when sent by the UE

RFC 3261 [15]

value

0