7.6 3GPP IM CN subsystem XML body

24.4033GPPIP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified]Release 7TISPANTS

7.6.1 General

This subclause contains the 3GPP IM CN Subsystem XML body in XML format. The 3GPP IM CN Subsystem XML shall be valid against the 3GPP IM CN Subsystem XML schema defined in table 7.7A.

Any SIP User Agent or proxy may insert or remove the 3GPP IM CN subsystem XML body or parts of it, as required, in any SIP message. The 3GPP IM CN subsystem XML body shall not be forwarded outside a 3GPP network.

The associated MIME type with the 3GPP IMS XML body is "application/3gpp-ims+xml".

7.6.2 Document Type Definition

The Document Type DefinitionXML Schema, according to XML syntax definitions, is defined in table 7.7A.

Table 7.7A: IM CN subsystem XML body, version 1 DTDXML Schema

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1">

<xs:complexType name="tIMS3GPP">

<xs:sequence>

<xs:choice>

<xs:element name="alternative-service" type="tAlternativeService"/>

<xs:element name="service-info" type="xs:string"/>

</xs:choice>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:attribute name="version" type="xs:decimal" use="required"/>

<xs:anyAttribute/>

</xs:complexType>

<xs:complexType name="tAlternativeService">

<xs:sequence>

<xs:element name="type" type="tType"/>

<xs:element name="reason" type="xs:string"/>

<xs:element name="action" type="tAction" minOccurs="0"/>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="tType">

<xs:sequence>

<xs:element name="emergency" minOccurs="0" maxOccurs="1">

<xs:complexType/>

</xs:element>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute/>

</xs:complexType>

<xs:complexType name="tAction">

<xs:sequence>

<xs:element name="emergency-registration" minOccurs="0" maxOccurs="1">

<xs:complexType/>

</xs:element>

<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

<xs:anyAttribute/>

</xs:complexType>

<xs:element name="ims-3gpp" type="tIMS3GPP"/>

</xs:schema>

<?xml version="1.0" ?>

<!– Draft DTD for the IMS XML body. –>

<!DOCTYPE ims-3gpp [

<!– ims-3gpp element: root element –>

<!ELEMENT ims-3gpp (

alternative-service?, service-info?)>

<!ATTLIST ims-3gpp version CDATA #REQUIRED>

<!– service-info element: The transparent data received from HSS for AS –>

<!ELEMENT service-info (#CDATA)>

<!– alternative-service: alternative-service used in emergency sessions –>

<!ELEMENT alternative-service (type, action?, reason)>

<!ELEMENT type (emergency)>

<!ELEMENT action (emergency-registration)>

<!ELEMENT reason (#PCDATA)>

]>

7.6.3 XML SchemaDTD description

This subclause describes the elements of the IMS Document Type Definition as defined in table 7.7A.

<ims-3gpp>: This is the root element of the IMS XML body. It shall always be present. The version described in the present document is 1XML instance documents of future versions of the XML Schema in table 7.7A shall be valid against the XML Schema in table 7.7A in this document. XML instance documents of the XML Schema in table 7.7A in the present document shall have a version attribute value, part of the ims-3gpp element, that is equal to the value of the XML Schema version described in the present document.

<service-info>: the transparent element received from the HSS for a particular trigger point are placed within this optional element.

<alternative-service>: in the present document, the alternative service is used as a response for an attempt to establish an emergency session within the IM CN subsystem. The element describes an alternative service where the call should success. The alternative service is described by the type of service information. A possible reason cause why an alternative service is suggested may be included.

The <alternative-service> element contains a <type> element that indicates the type of alternative service and an <action> element, an optional element.

The <type> element contains only the value "emergency" in the present document.

The <action> element contains only the value "emergency-registration" in the present document.

The <reason> element contains an explanatory text with the reason why the session setup has been redirected. A UE may use this information to give an indication to the user.

9 IP-Connectivity Access Network aspects when connected to the IM CN subsystem

9.2.2 Handling of the IP-CAN

The UE shall ensure that appropriate resources are available for the media flow(s) on the IP-CAN(s) related to a SIP-session. The means to ensure this is dependant on the characteristics for each IP-CAN, and is described separately for each IP-CAN in question.

GPRS is described in annex B. I-WLAN is described in annex D. xDSL is described in annex E. If a particular handling of the IP-CAN is needed for emergency calls, this is described in the annex for each access technology.

Annex A Profiles of IETF RFCs for 3GPP ETSI TISPAN usage

Editor’s note: IBCF related changes not added yet

NOTE: IBCF and emergency related changes have not been added yet. This will be reflected in future changes in tables e.g. A.3A, A.4 and A.162.

A.1.3 Roles

Table A.2: Roles

Item

Roles

Reference

RFC status

Profile status

1

User agent

[26]

o.1

o.1

2

Proxy

[26]

o.1

o.1

o.1: It is mandatory to support exactly one of these items.

NOTE: For the purposes of the present document it has been chosen to keep the specification simple by the tables specifying only one role at a time. This does not preclude implementations providing two roles, but an entirely separate assessment of the tables shall be made for each role.

Table A.3: Roles specific to this profile

Item

Roles

Reference

RFC status

Profile status

1

UE

5.1

n/a

o.1

2

P-CSCF

5.2

n/a

o.1

3

I-CSCF

5.3

n/a

o.1

3A

I-CSCF (THIG)

5.3

n/a

c1

4

S-CSCF

5.4

n/a

o.1

5

BGCF

5.6

n/a

o.1

6

MGCF

5.5

n/a

o.1

7

AS

5.7

n/a

o.1

7A

AS acting as terminating UA, or redirect server

5.7.2

n/a

c2

7B

AS acting as originating UA

5.7.3

n/a

c2

7C

AS acting as a SIP proxy

5.7.4

n/a

c2

7D

AS performing 3rd party call control

5.7.5

n/a

c2

8

MRFC

5.8

n/a

o.1

9

IMS-ALG

5.9

n/a

o.1

11

E-CSCF

5.11

n/a

o.1

c1: IF A.3/3 THEN o ELSE x – – I-CSCF.

c2: IF A.3/7 THEN o.2 ELSE n/a – – AS.

o.1: It is mandatory to support exactly one of these items.

o.2: It is mandatory to support at least one of these items.

NOTE: For the purposes of the present document it has been chosen to keep the specification simple by the tables specifying only one role at a time. This does not preclude implementations providing two roles, but an entirely separate assessment of the tables shall be made for each role.

Table A.3A: Roles specific to additional capabilities

Item

Roles

Reference

RFC status

Profile status

1

Presence server

3GPP TS 24.141 [8A]

n/a

c1

2

Presence user agent

3GPP TS 24.141 [8A]

n/a

c2

3

Resource list server

3GPP TS 24.141 [8A]

n/a

c3

4

Watcher

3GPP TS 24.141 [8A]

n/a

c4

11

Conference focus

3GPP TS 24.147 [8B]

n/a

c5

12

Conference participant

3GPP TS 24.147 [8B]

n/a

c6

c1: IF A.3/7A AND A.3/7B THEN o ELSE n/a – – AS acting as terminating UA, or redirect server and AS acting as originating UA.

c2: IF A.3/1 THEN o ELSE n/a – – UE.

c3: IF A.3/7A THEN o ELSE n/a – – AS acting as terminating UA, or redirect server.

c4: IF A.3/1 OR A.3/7B THEN o ELSE IF A.3/9 THEN m ELSE n/a – – UE or AS acting as originating UA.

c5: IF A.3/7D AND A.3/4 AND A.3/8 THEN o ELSE n/a – – AS performing 3rd party call control and S-CSCF and MRFC (note 2).

c6: IF A.3/1 OR A.3A/11 THEN o ELSE IF A.3/9 THEN m ELSE n/a – – UE or conference focus.

NOTE 1: For the purposes of the present document it has been chosen to keep the specification simple by the tables specifying only one role at a time. This does not preclude implementations providing two roles, but an entirely separate assessment of the tables shall be made for each role.

NOTE 2: The functional split between the MRFC and the conferencing AS is out of scope of this document and they are assumed to be collocated.

Table A.3B: Roles with respect to access technology

Item

Value used in P-Access-Network-Info header

Reference

RFC status

Profile status

1

3GPP-GERAN

[52] 4.4

o

c1

2

3GPP-UTRAN-FDD

[52] 4.4

o

c1

3

3GPP-UTRAN-TDD

[52] 4.4

o

c1

4

3GPP2-1X

[52] 4.4

o

c1

5

3GPP2-1X-HRPD

[52] 4.4

o

c1

11

IEEE-802.11

[52] 4.4

o

c1

12

IEEE-802.11°

[52] 4.4

o

c1

13

IEEE-802.11b

[52] 4.4

o

c1

14

IEEE-802.11g

[52] 4.4

o

c1

21

ADSL

[52] 4.4

o

c1

22

ADSL2

[52] 4.4

o

c1

23

ADSL2+

[52] 4.4

o

c1

24

RADSL

[52] 4.4

o

c1

25

SDSL

[52] 4.4

o

c1

26

HDSL

[52] 4.4

o

c1

27

HDSL2

[52] 4.4

o

c1

28

G.SHDSL

[52] 4.4

o

c1

29

VDSL

[52] 4.4

o

c1

30

IDSL

[52] 4.4

o

c1

c1: If A.3/1 OR A.3/2 THEN o.1 ELSE n/a.

o.1: It is mandatory to support at least one of these items.

A.2.1.2 Major capabilities

Table A.4: Major capabilities

Item

Does the implementation support

Reference

RFC status

Profile status

Capabilities within main protocol

1

client behaviour for registration?

[26] subclause 10.2

o

c3

2

registrar?

[26] subclause 10.3

o

c4

2A

registration of multiple contacts for a single address of record

[26] 10.2.1.2, 16.6

o

o

2B

initiating a session?

[26] subclause 13

o

o

3

client behaviour for INVITE requests?

[26] subclause 13.2

c18

c18

4

server behaviour for INVITE requests?

[26] subclause 13.3

c18

c18

5

session release?

[26] subclause 15.1

c18

c18

6

timestamping of requests?

[26] subclause 8.2.6.1

o

o

7

authentication between UA and UA?

[26] subclause 22.2

c34

c34

8

authentication between UA and registrar?

[26] subclause 22.2

o

n/a

8A

authentication between UA and proxy?

[26] 20.28, 22.3

o

o

9

server handling of merged requests due to forking?

[26] 8.2.2.2

m

m

10

client handling of multiple responses due to forking?

[26] 13.2.2.4

m

m

11

insertion of date in requests and responses?

[26] subclause 20.17

o

o

12

downloading of alerting information?

[26] subclause 20.4

o

o

Extensions

13

the SIP INFO method?

[25]

o

n/a

14

reliability of provisional responses in SIP?

[27]

c19

c18

15

the REFER method?

[36]

o

c33

16

integration of resource management and SIP?

[30] [64]

c19

c18

17

the SIP UPDATE method?

[29]

c5

c18

19

SIP extensions for media authorization?

[31]

o

c14

20

SIP specific event notification?

[28]

o

c13

21

the use of NOTIFY to establish a dialog?

[28] 4.2

o

n/a

22

acting as the notifier of event information?

[28]

c2

c15

23

acting as the subscriber to event information?

[28]

c2

c16

24

session initiation protocol extension header field for registering non-adjacent contacts?

[35]

o

c6

25

private extensions to the Session Initiation Protocol (SIP) for network asserted identity within trusted networks?

[34]

o

m

26

a privacy mechanism for the Session Initiation Protocol (SIP)?

[33]

o

m

26A

request of privacy by the inclusion of a Privacy header indicating any privacy option?

[33]

c9

c11

26B

application of privacy based on the received Privacy header?

[33]

c9

n/a

26C

passing on of the Privacy header transparently?

[33]

c9

c12

26D

application of the privacy option "header" such that those headers which cannot be completely expunged of identifying information without the assistance of intermediaries are obscured?

[33] 5.1

c10

c27

26E

application of the privacy option "session" such that anonymization for the session(s) initiated by this message occurs?

[33] 5.2

c10

c27

26F

application of the privacy option "user" such that user level privacy functions are provided by the network?

[33] 5.3

c10

c27

26G

application of the privacy option "id" such that privacy of the network asserted identity is provided by the network?

[34] 7

c10

n/a

26H

application of the privacy option "history" such that privacy of the History-Info header is provided by the network?

[66] 7.2

c37

c37

27

a messaging mechanism for the Session Initiation Protocol (SIP)?

[50]

o

c7

28

session initiation protocol extension header field for service route discovery during registration?

[38]

o

c17

29

compressing the session initiation protocol?

[55]

o

c8

30

private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP)?

[52]

o

m

31

the P-Associated-URI header extension?

[52] 4.1

c21

c22

32

the P-Called-Party-ID header extension?

[52] 4.2

c21

c23

33

the P-Visited-Network-ID header extension?

[52] 4.3

c21

c24

34

the P-Access-Network-Info header extension?

[52] 4.4

c21

c25

35

the P-Charging-Function-Addresses header extension?

[52] 4.5

c21

c26

36

the P-Charging-Vector header extension?

[52] 4.6

c21

c26

37

security mechanism agreement for the session initiation protocol?

[48]

o

c20

38

the Reason header field for the session initiation protocol?

[34A]

o

o (note 1)

39

an extension to the session initiation protocol for symmetric response routeing?

[56A]

o

xo

40

caller preferences for the session initiation protocol?

[56B]

C29

c29

40A

the proxy-directive within caller-preferences?

[56B] 9.1

o.5

o.5

40B

the cancel-directive within caller-preferences?

[56B] 9.1

o.5

o.5

40C

the fork-directive within caller-preferences?

[56B] 9.1

o.5

c28

40D

the recurse-directive within caller-preferences?

[56B] 9.1

o.5

o.5

40E

the parallel-directive within caller-preferences?

[56B] 9.1

o.5

c28

40F

the queue-directive within caller-preferences?

[56B] 9.1

o.5

o.5

41

an event state publication extension to the session initiation protocol?

[70]

o

c30

42

SIP session timer?

[58]

c19

c19

43

the SIP Referred-By mechanism?

[59]

o

c33

44

the Session Initiation Protocol (SIP) "Replaces" header?

[60]

c19

c38 (note 1)

45

the Session Initiation Protocol (SIP) "Join" header?

[61]

c19

c19 (note 1)

46

the callee capabilities?

[62]

o

c35

47

an extension to the session initiation protocol for request history information?

[66]

o

o

48

Rejecting anonymous requests in the Session Initiation Protocol (SIP)

[67]

o

o

49

session initiation protocol URIs for applications such as voicemail and interactive voice response

[68]

o

o

52

a uniform resource name for services

[69]

n/a

c39

c2: IF A.4/20 THEN o.1 ELSE n/a – – SIP specific event notification extension.

c3: IF A.3/1 OR A.3/4 THEN m ELSE n/a – – UE or S-CSCF functional entity.

c4: IF A.3/4 THEN m ELSE IF A.3/7 THEN o ELSE n/a – – S-CSCF or AS functional entity.

c5: IF A.4/16 THEN m ELSE o – – integration of resource management and SIP extension.

c6: IF A.3/4 OR A.3/1 THEN m ELSE n/a. – – S-CSCF or UE.

c7: IF A.3/1 OR A.3/4 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/9 THEN m ELSE n/a – – UA or S-CSCF or AS acting as terminating UA or AS acting as originating UA or AS performing 3rd party call control or IMS-ALG.

c8: IF A.3/1 THEN (IF (A.3B/1 OR A.3B/2 OR A.3B/3 OR A.3B/4 OR A.3B/5 OR A.3B/11 OR A.3B/12 OR A.3B/13 OR A.3B/14) THEN m ELSE o) ELSE n/a – – UE behaviour (based on P-Access-Network-Info usage).

c9: IF A.4/26 THEN o.2 ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c10: IF A.4/26B THEN o.3 ELSE n/a – – application of privacy based on the received Privacy header.

c11: IF A.3/1 OR A.3/6 THEN o ELSE IF A.3/9 THEN m ELSE n/a – – UE or MGCF, IMS-ALG

c12: IF A.3/7D THEN m ELSE n/a – – AS performing 3rd-party call control.

c13: IF A.3/1 OR A.3/2 OR A.3/4 OR A.3/9 THEN m ELSE o – – UE or S-CSCF or IMS-ALG.

c14: IF A.3/1 AND (A.3B/1 OR A.3B/2 OR A.3B/3 OR A.3B/4 OR A.3B/5) THEN m ELSE n/a – UE with appropriate access technology

c15: IF A.4/20 AND (A.3/4 OR A.3/9) THEN m ELSE o – SIP specific event notification extensions and S-CSCF, IMS-ALG .

c16: IF A.4/20 AND (A.3/1 OR A.3/2 OR A.3/9) THEN m ELSE o – – SIP specific event notification extension and UE or P-CSCF or IMS-ALG.

c17: IF A.3/1 or A.3/4 THEN m ELSE n/a – – UE or S-CSCF

c18: IF A.4/2B THEN m ELSE n/a – – initiating sessions.

c19: IF A.4/2B THEN o ELSE n/a – – initiating sessions.

c20: IF A.3/1 THEN m ELSE n/a – – UE behaviour.

c21: IF A.4/30 THEN o.4 ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP).

c22: IF A.4/30 AND (A.3/1 OR A.3/4) THEN m ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and S-CSCF or UA.

c23: IF A.4/30 AND A.3/1 THEN o ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and UE.

c24: IF A.4/30 AND A.3/4) THEN m ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and S-CSCF.

c25: IF A.4/30 AND (A.3/1 OR A.3/4 OR A.3/7A OR A.3/7D OR A.3/9) THEN m ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and UE,
S-CSCF or AS acting as terminating UA or AS acting as third-party call controller, IMS-ALG.

c26: IF A.4/30 AND (A.3/6 OR A.3/7A OR A.3/7B or A.3/7D) THEN m ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and MGCF, AS acting as a terminating UA, or AS acting as an originating UA, or AS acting as third-party call controller.

c27: IF A.3/7D THEN o ELSE x – – AS performing 3rd party call control.

c28: IF A.3/1 THEN m ELSE o.5 – – UE.

c29: IF A.4/40A OR A.4/40B OR A.4/40C OR A.4/40D OR A.4/40E OR A.4/40F THEN m ELSE n/a – – support of any directives within caller preferences for the session initiation protocol.

c30: IF A.3A/1 OR A.3A/2 THEN m ELSE IF A.3/1 THEN o ELSE n/a – – presence server, presence user agent, UE, AS.

c33: IF A.3/11 OR A.3/12 OR A.3/9 OR A.4/44 THEN m ELSE o – – conference focus or conference participant or IMS-ALG or the Session Initiation Protocol (SIP) "Replaces" header.

c34: IF A.4/44 OR A.4/45 OR A.3/9 THEN m ELSE n/a – – the Session Initiation Protocol (SIP) "Replaces" header or the Session Initiation Protocol (SIP) "Join" header or IMS-ALG.

c35: IF A.3/4 OR A.3/9 THEN m ELSE IF (A.3/1 OR A.3/6 OR A.3/7 OR A.3/8) THEN o ELSE n/a – – S-CSCF or IMS-ALG functional entities, UE or MGCF or AS or MRFC functional entity.

c37 IF A.4/47 THEN o.3 ELSE n/a – – an extension to the session initiation protocol for request history information.

c38: IF A.4/2B AND (A.3A/11 or A.3A/12) THEN m ELSE IF A.4/2B THEN o ELSE n/a – – initiating sessions, conference focus, conference participant

c39: IF A.3/1 THEN m ELSE n/a – – UE.

o.1: At least one of these capabilities is supported.

o.2: At least one of these capabilities is supported.

o.3: At least one of these capabilities is supported.

o.4: At least one of these capabilities is supported.

o.5: At least one of these capabilities is supported.

NOTE 1: At the MGCF, the interworking specifications do not support a handling of the header associated with this extension.

Prerequisite A.5/20 – – SIP specific event notification

Table A.4A: Supported event packages

Item

Does the implementation support

Subscriber

Notifier

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

reg event package?

[43]

c1

c3

[43]

c2

c4

2

refer package?

[36] 3

c13

c13

[36] 3

c13

c13

3

presence package?

[74] 6

c1

c5

[74] 6

c2

c6

4

eventlist with underlying presence package?

[75], [74] 6

c1

c7

[75], [74] 6

c2

c8

5

presence.winfo template-package?

[72] 4

c1

c9

[72] 4

c2

c10

6

sip-profile package?

[77] 3

c1

c11

[77] 3

c2

c12

7

conference package?

[78] 3

c1

c21

[78] 3

c1

c22

8

message-summary package?

[65]

c1

c23

[65] 3

c2

c24

c1: IF A.4/23 THEN o ELSE n/a – – acting as the subscriber to event information.

c2: IF A.4/22 THEN o ELSE n/a – – acting as the notifier of event information.

c3: IF A.3/1 OR A.3/2 THEN m ELSE IF A.3/7 THEN o ELSE n/a – – UE, P-CSCF, AS.

c4: IF A.3/4 THEN m ELSE n/a – – S-CSCF.

c5: IF A.3A/3 OR A.3A/4 THEN m ELSE IF A.4/23 THEN o ELSE n/a – – resource list server or watcher, acting as the subscriber to event information.

c6: IF A.3A/1 THEN m ELSE IF A.4/22 THEN o ELSE n/a – – presence server, acting as the notifier of event information.

c7: IF A.3A/4 THEN m ELSE IF A.4/23 THEN o ELSE n/a – – watcher, acting as the subscriber to event information.

c8: IF A.3A/3 THEN m ELSE IF A.4/22 THEN o ELSE n/a – – resource list server, acting as the notifier of event information.

c9: IF A.3A/2 THEN m ELSE IF A.4/23 THEN o ELSE n/a – – presence user agent, acting as the subscriber to event information.

c10: IF A.3A/1 THEN m ELSE IF A.4/22 THEN o ELSE n/a – – presence server, acting as the notifier of event information.

c11: IF A.3A/2 OR A.3A/4 THEN o ELSE IF A.4/23 THEN o ELSE n/a – – presence user agent or watcher, acting as the subscriber to event information.

c12: IF A.3A/1 OR A.3A/3 THEN m ELSE IF A.4/22 THEN o ELSE n/a – – presence server or resource list server, acting as the notifier of event information.

c13: IF A.4/15 THEN m ELSE n/a – – the REFER method.

c21: IF A.3A/12 THEN m ELSE IF A.4/23 THEN o ELSE n/a – – conference participant or acting as the subscriber to event information.

c22: IF A.3A/11 THEN m ELSE IF A.4/22 THEN o ELSE n/a – – conference focus or acting as the notifier of event information.

c23: IF (A.3/1 OR A.3/7A OR A.3/7B) AND A.4/23 THEN o ELSE n/a – – UE, AS acting as terminating UA, or redirect server, AS acting as originating UA all as subscriber of event information.

c24: IF (A.3/1 OR A.3/7A OR A.3/7B) AND A.4/22 THEN o ELSE n/a – – UE, AS acting as terminating UA, or redirect server, AS acting as originating UA all as notifier of event information.

A.2.1.4.1 Status-codes

Table A.6: Supported status-codes

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

100 (Trying)

[26] 21.1.1

n/a

n/a

[26] 21.1.1

c11

c11

101

1xx response

[26] 21.1

p21

p21

[26] 21.1

p21

p21

2

180 (Ringing)

[26] 21.1.2

c2

c2

[26] 21.1.2

c1

c1

3

181 (Call Is Being Forwarded)

[26] 21.1.3

c2

c2

[26] 21.1.3

c1

c1

4

182 (Queued)

[26] 21.1.4

c2

c2

[26] 21.1.4

c1

c1

5

183 (Session Progress)

[26] 21.1.5

c1

c1

[26] 21.1.5

c1

c1

102

2xx response

[26] 21.2

p22

p22

[26] 21.1

p22

p22

6

200 (OK)

[26] 21.2.1

m

m

[26] 21.2.1

m

m

7

202 (Accepted)

[28] 8.3.1

c3

c3

[28] 8.3.1

c3

c3

103

3xx response

[26] 21.3

p23

p23

[26] 21.1

p23

p23

8

300 (Multiple Choices)

[26] 21.3.1

[26] 21.3.1

9

301 (Moved Permanently)

[26] 21.3.2

[26] 21.3.2

10

302 (Moved Temporarily)

[26] 21.3.3

[26] 21.3.3

11

305 (Use Proxy)

[26] 21.3.4

[26] 21.3.4

12

380 (Alternative Service)

[26] 21.3.5

[26] 21.3.5

104

4xx response

[26] 21.4

p24

p24

[26] 21.4

p24

p24

13

400 (Bad Request)

[26] 21.4.1

m

m

[26] 21.4.1

m

m

14

401 (Unauthorized)

[26] 21.4.2

o

c12

[26] 21.4.2

m

m

15

402 (Payment Required)

[26] 21.4.3

n/a

n/a

[26] 21.4.3

n/a

n/a

16

403 (Forbidden)

[26] 21.4.4

m

m

[26] 21.4.4

m

m

17

404 (Not Found)

[26] 21.4.5

m

m

[26] 21.4.5

m

m

18

405 (Method Not Allowed)

[26] 21.4.6

m

m

[26] 21.4.6

m

m

19

406 (Not Acceptable)

[26] 21.4.7

m

m

[26] 21.4.7

m

m

20

407 (Proxy Authentication Required)

[26] 21.4.8

o

o

[26] 21.4.8

m

m

21

408 (Request Timeout)

[26] 21.4.9

m

m

[26] 21.4.9

m

m

22

410 (Gone)

[26] 21.4.10

m

m

[26] 21.4.10

m

m

22A

412 (Conditional Request Failed)

[70] 11.2.1

c20

c20

[70] 11.2.1

c20

c20

23

413 (Request Entity Too Large)

[26] 21.4.11

m

m

[26] 21.4.11

m

m

24

414 (Request-URI Too Large)

[26] 21.4.12

m

m

[26] 21.4.12

m

m

25

415 (Unsupported Media Type)

[26] 21.4.13

m

m

[26] 21.4.13

m

m

26

416 (Unsupported URI Scheme)

[26] 21.4.14

m

m

[26] 21.4.14

m

m

27

420 (Bad Extension)

[26] 21.4.15

m

c13

[26] 21.4.15

m

m

28

421 (Extension Required)

[26] 21.4.16

o

[26] 21.4.16

i

i

28A

422 (Session Interval Too Small)

[58] 6

c7

c7

[58] 6

c7

c7

29

423 (Interval Too Brief)

[26] 21.4.17

c4

c4

[26] 21.4.17

m

m

29A

429 (Provide Referrer Identity)

[59] 5

c8

c8

[59] 5

c9

c9

29B

433 (Anonymity Disallowed)

[67] 4

c14

c14

[67] 4

c14

c14

30

480 (Temporarily Unavailable)

[26] 21.4.18

m

m

[26] 21.4.18

m

m

31

481 (Call/Transaction Does Not Exist)

[26] 21.4.19

m

m

[26] 21.4.19

m

m

32

482 (Loop Detected)

[26] 21.4.20

m

m

[26] 21.4.20

m

m

33

483 (Too Many Hops)

[26] 21.4.21

m

m

[26] 21.4.21

m

m

34

484 (Address Incomplete)

[26] 21.4.22

o

o

[26] 21.4.22

m

m

35

485 (Ambiguous)

[26] 21.4.23

o

o

[26] 21.4.23

m

m

36

486 (Busy Here)

[26] 21.4.24

m

m

[26] 21.4.24

m

m

37

487 (Request Terminated)

[26] 21.4.25

m

m

[26] 21.4.25

m

m

38

488 (Not Acceptable Here)

[26] 21.4.26

m

m

[26] 21.4.26

m

m

39

489 (Bad Event)

[28] 7.3.2

c3

c3

[28] 7.3.2

c3

c3

40

491 (Request Pending)

[26] 21.4.27

m

m

[26] 21.4.27

m

m

41

493 (Undecipherable)

[26] 21.4.28

m

m

[26] 21.4.28

m

m

41A

494 (Security Agreement Required)

[48] 2

c5

c5

[48] 2

c6

c6

105

5xx response

[26] 21.5

p25

p25

[26] 21.5

p25

p25

42

500 (Internal Server Error)

[26] 21.5.1

m

m

[26] 21.5.1

m

m

43

501 (Not Implemented)

[26] 21.5.2

m

m

[26] 21.5.2

m

m

44

502 (Bad Gateway)

[26] 21.5.3

o

o

[26] 21.5.3

m

m

45

503 (Service Unavailable)

[26] 21.5.4

m

m

[26] 21.5.4

m

m

46

504 (Server Time-out)

[26] 21.5.5

m

m

[26] 21.5.5

m

m

47

505 (Version not supported)

[26] 21.5.6

m

m

[26] 21.5.6

m

m

48

513 (Message Too Large)

[26] 21.5.7

m

m

[26] 21.5.7

m

m

49

580 (Precondition Failure)

[30] 8

[30] 8

106

6xx response

[26] 21.6

p26

p26

[26] 21.6

p26

p26

50

600 (Busy Everywhere)

[26] 21.6.1

m

m

[26] 21.6.1

m

m

51

603 (Decline)

[26] 21.6.2

c10

c10

[26] 21.6.2

m

m

52

604 (Does Not Exist Anywhere)

[26] 21.6.3

m

m

[26] 21.6.3

m

m

53

606 (Not Acceptable)

[26] 21.6.4

m

m

[26] 21.6.4

m

m

c1: IF A.5/9 THEN m ELSE n/a – – INVITE response.

c2: IF A.5/9 THEN o ELSE n/a – – INVITE response.

c3: IF A.4/20 THEN m ELSE n/a – – SIP specific event notification extension.

c4: IF A.5/19 OR A.5/21 THEN m ELSE n/a – – REGISTER response or SUBSCRIBE response.

c5: IF A.4/37 AND A.4/2 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol and registrar.

c6: IF A.4/37 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

c7: IF A.4/42 AND (A.5/9 OR A.5/23) THEN m ELSE n/a – – the SIP session timer AND (INVITE response OR UPDATE response).

c8: IF A.4/43 AND A.5/17 THEN o ELSE n/a – – the SIP Referred-By mechanism and REFER response.

c9: IF A.4/43 AND A.5/17 THEN m ELSE n/a – – the SIP Referred-By mechanism and REFER response.

c10: IF A.4/44 THEN m ELSE o – – the Session Initiation Protocol (SIP) "Replaces" header.

c11: IF A.5/9 THE m ELSE n/a – – INVITE response (note 1).

c12: IF A.3/4 THEN m ELSE o – – S-CSCF.

c13: IF A.3/1 OR A.3/2 OR A.3/4 THEN m ELSE o – – UE, P-CSCF, S-CSCF.

c14: IF A.4/48 THEN m ELSE n/a – – rejecting anonymous requests in the session initiation protocol

c20: IF A.4/41 THEN m ELSE n/a – – an event state publication extension to the session initiation protocol.

p21: A.6/2 OR A.6/3 OR A.6/4 OR A.6/5 – – 1xx response.

p22: A.6/6 OR A.6/7 – – 2xx response.

p23: A.6/8 OR A.6/9 OR A.6/10 OR A.6/11 OR A.6/12 OR A.6/13 – – 3xx response.

p24: A.6/14 OR A.6/15 OR A.6/16 OR A.6/17 OR A.6/18 OR A.6/19 OR A.6/20 OR A.6/21 OR A.6/22 OR A.6/22A OR A.6/23 OR A.6/24 OR A.6/25 OR A.6/26 OR A.6/27 OR A.6/28 OR A.6/28A OR A.6/29 OR A.6/29A OR A.6/29B OR A.6/30 OR A.6/31 OR A.6/32 OR A.6/33 OR A.6/34 OR A.6/35 OR A.6/36 OR A.6/436 OR A.6/38 OR A.6/39 OR A.6/40 OR A.6/41 OR A.6/41A. – 4xx response.

p25: A.6/42 OR A.6/43 OR A.6/44 OR A.6/45 OR A.6/46 OR A.6/47 OR A.6/48 OR A.6/49 – – 5xx response

p26: A.6/50 OR A.6/51 OR A.6/52 OR A.6/53 – – 6xx response.

NOTE 1: RFC 3261 [26] gives the status of this header for methods other than INVITE as SHOULD NOT.

A.2.2.2 Major capabilities

Table A.162: Major capabilities

Item

Does the implementation support

Reference

RFC status

Profile status

Capabilities within main protocol

3

initiate session release?

[26] 16

x

c27

4

stateless proxy behaviour?

[26] 16.11

o.1

c28

5

stateful proxy behaviour?

[26] 16.2

o.1

c29

6

forking of initial requests?

[26] 16.1

c1

c31

7

support of indication of TLS connections in the Record-Route header on the upstream side?

[26] 16.7

o

n/a

8

support of indication TLS connections in the Record-Route header on the downstream side?

[26] 16.7

o

n/a

8A

authentication between UA and proxy?

[26] 20.28, 22.3

o

x

9

insertion of date in requests and responses?

[26] 20.17

o

o

10

suppression or modification of alerting information data?

[26] 20.4

o

o

11

reading the contents of the Require header before proxying the request or response?

[26] 20.32

o

o

12

adding or modifying the contents of the Require header before proxying the REGISTER request or response

[26] 20.32

o

m

13

adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER?

[26] 20.32

o

o

14

being able to insert itself in the subsequent transactions in a dialog (record-routing)?

[26] 16.6

o

c2

15

the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing?

[26] 16.7

c3

c3

16

reading the contents of the Supported header before proxying the response?

[26] 20.37

o

o

17

reading the contents of the Unsupported header before proxying the 420 response to a REGISTER?

[26] 20.40

o

m

18

reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER?

[26] 20.40

o

o

19

the inclusion of the Error-Info header in 3xx – 6xx responses?

[26] 20.18

o

o

19A

reading the contents of the Organization header before proxying the request or response?

[26] 20.25

o

o

19B

adding or concatenating the Organization header before proxying the request or response?

[26] 20.25

o

o

19C

reading the contents of the Call-Info header before proxying the request or response?

[26] 20.25

o

o

19D

adding or concatenating the Call-Info header before proxying the request or response?

[26] 20.25

o

o

19E

delete Contact headers from 3xx responses prior to relaying the response?

[26] 20

o

o

Extensions

20

the SIP INFO method?

[25]

o

o

21

reliability of provisional responses in SIP?

[27]

o

i

22

the REFER method?

[36]

o

o

23

integration of resource management and SIP?

[30] [64]

o

i

24

the SIP UPDATE method?

[29]

c4

i

26

SIP extensions for media authorization?

[31]

o

c7

27

SIP specific event notification

[28]

o

i

28

the use of NOTIFY to establish a dialog

[28] 4.2

o

n/a

29

Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts

[35]

o

c6

30

extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks

[34]

o

m

30A

act as first entity within the trust domain for asserted identity

[34]

c5

c8

30B

act as subsequent entity within trust network that can route outside the trust network

[34]

c5

c9

31

a privacy mechanism for the Session Initiation Protocol (SIP)

[33]

o

m

31A

request of privacy by the inclusion of a Privacy header

[33]

n/a

n/a

31B

application of privacy based on the received Privacy header

[33]

c10

c12

31C

passing on of the Privacy header transparently

[33]

c10

c13

31D

application of the privacy option "header" such that those headers which cannot be completely expunged of identifying information without the assistance of intermediaries are obscured?

[33] 5.1

x

x

31E

application of the privacy option "session" such that anonymization for the session(s) initiated by this message occurs?

[33] 5.2

n/a

n/a

31F

application of the privacy option "user" such that user level privacy functions are provided by the network?

[33] 5.3

n/a

n/a

31G

application of the privacy option "id" such that privacy of the network asserted identity is provided by the network?

[34] 7

c11

c12

31H

application of the privacy option "history" such that privacy of the History-Info header is provided by the network?

[66] 7.2

c34

c34

32

Session Initiation Protocol Extension Header Field for Service Route Discovery During Registration

[38]

o

c30

33

a messaging mechanism for the Session Initiation Protocol (SIP)

[50]

o

m

34

Compressing the Session Initiation Protocol

[55]

o

c7

35

private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP)?

[52]

o

m

36

the P-Associated-URI header extension?

[52] 4.1

c14

c15

37

the P-Called-Party-ID header extension?

[52] 4.2

c14

c16

38

the P-Visited-Network-ID header extension?

[52] 4.3

c14

c17

39

reading, or deleting the P-Visited-Network-ID header before proxying the request or response?

[52] 4.3

c18

n/a

41

the P-Access-Network-Info header extension?

[52] 4.4

c14

c19

42

act as first entity within the trust domain for access network information?

[52] 4.4

c20

c21

43

act as subsequent entity within trust network for access network information that can route outside the trust network?

[52] 4.4

c20

c22

44

the P-Charging-Function-Addresses header extension?

[52] 4.5

c14

m

44A

adding, deleting or reading the P‑Charging-Function-Addresses header before proxying the request or response?

[52] 4.6

c25

c26

45

the P-Charging-Vector header extension?

[52] 4.6

c14

m

46

adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response?

[52] 4.6

c23

c24

47

security mechanism agreement for the session initiation protocol?

[48]

o

c7

48

the Reason header field for the session initiation protocol

[34A]

o

o

49

an extension to the session initiation protocol for symmetric response routeing

[56A]

o

x

50

caller preferences for the session initiation protocol?

[56B]

c33

c33

50A

the proxy-directive within caller-preferences?

[56B] 9.1

o.4

o.4

50B

the cancel-directive within caller-preferences?

[56B] 9.1

o.4

o.4

50C

the fork-directive within caller-preferences?

[56B] 9.1

o.4

c32

50D

the recurse-directive within caller-preferences?

[56B] 9.1

o.4

o.4

50E

the parallel-directive within caller-preferences?

[56B] 9.1

o.4

c32

50F

the queue-directive within caller-preferences?

[56B] 9.1

o.4

o.4

51

an event state publication extension to the session initiation protocol?

[70]

o

m

52

SIP session timer?

[58]

o

o

53

the SIP Referred-By mechanism?

[59]

o

o

54

the Session Initiation Protocol (SIP) "Replaces" header?

[60]

o

o

55

the Session Initiation Protocol (SIP) "Join" header?

[61]

o

o

56

the callee capabilities?

[62]

o

o

57

an extension to the session initiation protocol for request history information?

[66]

o

o

58

Rejecting anonymous requests in the Session Initiation Protocol (SIP)

[200]

o

o

59

session initiation protocol URIs for applications such as voicemail and interactive voice response

[68]

o

o

60

an SIP Reason header extension for indicating redirection/ communication diversion reasons?

[80]

o

c34

62

a uniform resource name for services

[69]

n/a

c35

c1: IF A.162/5 THEN o ELSE n/a – – stateful proxy behaviour.

c2: IF A.3/2 OR A.3/3A OR A.3/4 THEN m ELSE o – – P-CSCF, I-CSCF(THIG) or S-CSCF.

c3: IF (A.162/7 AND NOT A.162/8) OR (NOT A.162/7 AND A.162/8) THEN m ELSE IF A.162/14 THEN o ELSE n/a – – TLS interworking with non-TLS else proxy insertion.

c4: IF A.162/23 THEN m ELSE o – – integration of resource management and SIP.

c5: IF A.162/30 THEN o ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c6: IF A.3/2 OR A.3/3A THEN m ELSE n/a – – P-CSCF or I-CSCF (THIG).

c7: IF A.3/2 THEN m ELSE n/a – – P-CSCF.

c8: IF A.3/2 AND A.162/30 THEN m ELSE n/a – – P-CSCF and extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks.

c9: IF A.3/2 AND A.162/30 THEN m ELSE IF A.3/7C AND A.162/30 THEN o ELSE n/a – – S-CSCF or AS acting as proxy and extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks (note).

c10: IF A.162/31 THEN o.2 ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP).

c11: IF A.162/31B THEN o ELSE x – – application of privacy based on the received Privacy header.

c12: IF A.162/31 AND A.3/4 THEN m ELSE n/a – – S-CSCF.

c13: IF A.162/31 AND (A.3/2 OR A.3/3 OR A.3/7C) THEN m ELSE n/a – – P-CSCF OR
I-CSCF OR AS acting as a SIP proxy.

c14: IF A.162/35 THEN o.3 ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP).

c15: IF A.162/35 AND (A.3/2 OR A.3/3) THEN m THEN o ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and P-CSCF or I-CSCF.

c16: IF A.162/35 AND (A.3/2 OR A.3/3 OR A.3/4) THEN m ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and P-CSCF or I-CSCF or S-CSCF.

c17: IF A.162/35 AND (A.3/2 OR A.3/3) THEN m ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and P‑CSCF or I-CSCF.

c18: IF A.162/38 THEN o ELSE n/a – – the P-Visited-Network-ID header extension.

c19: IF A.162/35 AND (A.3/2 OR A.3.3 OR A.3/4 OR A.3/7 THEN m ELSE n/a – – private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and P-CSCF, I-CSCF, S-CSCF, AS acting as a proxy.

c20: IF A.162/41 THEN o ELSE n/a – – the P-Access-Network-Info header extension.

c21: IF A.162/41 AND A.3/2 THEN m ELSE n/a – – the P-Access-Network-Info header extension and P-CSCF.

c22: IF A.162/41 AND A.3/4 THEN m ELSE n/a – – the P-Access-Network-Info header extension and S-CSCF.

c23: IF A.162/45 THEN o ELSE n/a – – the P-Charging-Vector header extension.

c24: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension.

c25: IF A.162/44 THEN o ELSE n/a – – the P-Charging-Function-Addresses header extension.

c26: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function Addresses header extension.

c27: IF A.3/2 OR A.3/4 THEN m ELSE x – – P-CSCF or S-CSCF.

c28: IF A.3/2 OR A.3/4 OR A.3/6 then m ELSE o – – P-CSCF or S-CSCF of MGCF.

c29: IF A.3/2 OR A.3/4 OR A.3/6 then o ELSE m – – P-CSCF or S-CSCF of MGCF.

c30: IF A.3/2 o ELSE i – – P-CSCF.

c31: IF A.3/4 THEN m ELSE x – – S-CSCF.

c32: IF A.3/4 THEN m ELSE o.4 – – S-CSCF.

c33: IF A.162/50A OR A.162/50B OR A.162/50C OR A.162/50D OR A.162/50E OR A.162/50F THEN m ELSE n/a – – support of any directives within caller preferences for the session initiation protocol.

c34 IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information.

c35: IF A.3/2 OR A.3/11 THEN m ELSE n/a – – P-CSCF, E-CSCF.

o.1: It is mandatory to support at least one of these items.

o.2: It is mandatory to support at least one of these items.

o.3: It is mandatory to support at least one of these items.

o.4 At least one of these capabilities is supported.

NOTE: An AS acting as a proxy may be outside the trust domain, and therefore not able to support the capability for that reason; in this case it is perfectly reasonable for the header to be passed on transparently, as specified in the PDU parts of the profile.

A.2.2.4.1 Status-codes

Table A.164: Supported-status codes

Item

Header

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

100 (Trying)

[26] 21.1.1

c1

c1

[26] 21.1.1

c2

c2

101

1xx response

[26] 21.1

p21

p21

[26] 21.1

p21

p21

2

180 (Ringing)

[26] 21.1.2

c3

c3

[26] 21.1.2

c3

c3

3

181 (Call Is Being Forwarded)

[26] 21.1.3

c3

c3

[26] 21.1.3

c3

c3

4

182 (Queued)

[26] 21.1.4

c3

c3

[26] 21.1.4

c3

c3

5

183 (Session Progress)

[26] 21.1.5

c3

c3

[26] 21.1.5

c3

c3

102

2xx response

[26] 21.2

p22

p22

[26] 21.1

p22

p22

6

200 (OK)

[26] 21.2.1

m

m

[26] 21.2.1

i

m

7

202 (Accepted)

[28] 8.3.1

c4

c4

[28] 8.3.1

c4

c4

103

3xx response

[26] 21.3

p23

p23

[26] 21.1

p23

p23

8

300 (Multiple Choices)

[26] 21.3.1

m

m

[26] 21.3.1

i

i

9

301 (Moved Permanently)

[26] 21.3.2

m

m

[26] 21.3.2

i

i

10

302 (Moved Temporarily)

[26] 21.3.3

m

m

[26] 21.3.3

i

i

11

305 (Use Proxy)

[26] 21.3.4

m

m

[26] 21.3.4

i

i

12

380 (Alternative Service)

[26] 21.3.5

m

m

[26] 21.3.5

i

i

104

4xx response

[26] 21.4

p24

p24

[26] 21.4

p24

p24

13

400 (Bad Request)

[26] 21.4.1

m

m

[26] 21.4.1

i

i

14

401 (Unauthorized)

[26] 21.4.2

m

m

[26] 21.4.2

i

c10

15

402 (Payment Required)

[26] 21.4.3

n/a

n/a

[26] 21.4.3

n/a

n/a

16

403 (Forbidden)

[26] 21.4.4

m

m

[26] 21.4.4

i

i

17

404 (Not Found)

[26] 21.4.5

m

m

[26] 21.4.5

i

i

18

405 (Method Not Allowed)

[26] 21.4.6

m

m

[26] 21.4.6

i

i

19

406 (Not Acceptable)

[26] 21.4.7

m

m

[26] 21.4.7

i

i

20

407 (Proxy Authentication Required)

[26] 21.4.8

m

m

[26] 21.4.8

i

i

21

408 (Request Timeout)

[26] 21.4.9

m

m

[26] 21.4.9

i

i

22

410 (Gone)

[26] 21.4.10

m

m

[26] 21.4.10

i

i

22A

412 (Conditional Request Failed)

[70] 11.2.1

c20

c20

[70] 11.2.1

c19

c19

23

413 (Request Entity Too Large)

[26] 21.4.11

m

m

[26] 21.4.11

i

i

24

414 (Request-URI Too Large)

[26] 21.4.12

m

m

[26] 21.4.12

i

i

25

415 (Unsupported Media Type)

[26] 21.4.13

m

m

[26] 21.4.13

i

i

26

416 (Unsupported URI Scheme)

[26] 21.4.14

m

m

[26] 21.4.14

i

i

27

420 (Bad Extension)

[26] 21.4.15

m

m

[26] 21.4.15

i

i

28

421 (Extension Required)

[26] 21.4.16

m

m

[26] 21.4.16

i

i

28A

422 (Session Interval Too Small)

[58] 6

c8

c8

[58] 6

c8

c8

29

423 (Interval Too Brief)

[26] 21.4.17

c5

c5

[26] 21.4.17

c6

c6

29A

429 (Provide Referrer Identity)

[59] 5

c9

c9

[59] 5

c9

c9

29B

433 (Anonymity Disallowed)

[67] 4

c14

c14

[67] 4

c14

c14

30

480 (Temporarily not available)

[26] 21.4.18

m

m

[26] 21.4.18

i

i

31

481 (Call /Transaction Does Not Exist)

[26] 21.4.19

m

m

[26] 21.4.19

i

i

32

482 (Loop Detected)

[26] 21.4.20

m

m

[26] 21.4.20

i

i

33

483 (Too Many Hops)

[26] 21.4.21

m

m

[26] 21.4.21

i

i

34

484 (Address Incomplete)

[26] 21.4.22

m

m

[26] 21.4.22

i

i

35

485 (Ambiguous)

[26] 21.4.23

m

m

[26] 21.4.23

i

i

36

486 (Busy Here)

[26] 21.4.24

m

m

[26] 21.4.24

i

i

37

487 (Request Terminated)

[26] 21.4.25

m

m

[26] 21.4.25

i

i

38

488 (Not Acceptable Here)

[26] 21.4.26

m

m

[26] 21.4.26

i

i

39

489 (Bad Event)

[28] 7.3.2

c4

c4

[28] 7.3.2

c4

c4

40

491 (Request Pending)

[26] 21.4.27

m

m

[26] 21.4.27

i

i

41

493 (Undecipherable)

[26] 21.4.28

m

m

[26] 21.4.28

i

i

41A

494 (Security Agreement Required)

[48] 2

c7

c7

[48] 2

n/a

n/a

105

5xx response

[26] 21.5

p25

p25

[26] 21.5

p25

p25

42

500 (Internal Server Error)

[26] 21.5.1

m

m

[26] 21.5.1

i

i

43

501 (Not Implemented)

[26] 21.5.2

m

m

[26] 21.5.2

i

i

44

502 (Bad Gateway)

[26] 21.5.3

m

m

[26] 21.5.3

i

i

45

503 (Service Unavailable)

[26] 21.5.4

m

m

[26] 21.5.4

i

i

46

504 (Server Time-out)

[26] 21.5.5

m

m

[26] 21.5.5

i

i

47

505 (Version not supported)

[26] 21.5.6

m

m

[26] 21.5.6

i

i

48

513 (Message Too Large)

[26] 21.5.7

m

m

[26] 21.5.7

i

i

49

580 (Precondition Failure)

[30] 8

m

m

[30] 8

i

i

106

6xx response

[26] 21.6

p26

p26

[26] 21.6

p26

p26

50

600 (Busy Everywhere)

[26] 21.6.1

m

m

[26] 21.6.1

i

i

51

603 (Decline)

[26] 21.6.2

m

m

[26] 21.6.2

i

i

52

604 (Does Not Exist Anywhere)

[26] 21.6.3

m

m

[26] 21.6.3

i

i

53

606 (Not Acceptable)

[26] 21.6.4

m

m

[26] 21.6.4

i

i

c1: IF A.163/9 AND A.162/5 THEN m ELSE n/a – – INVITE response, stateful proxy.

c2: IF A.163/9 THEN (IF A.162/5 THEN m ELSE i) ELSE n/a – – INVITE response, stateful proxy.

c3: IF A.163/9 THEN m ELSE n/a – – INVITE response.

c4: IF A.162/27 THEN m ELSE n/a – – SIP specific event notification.

c5: IF A.163/19 OR A.163/21 THEN m ELSE n/a – – REGISTER response or SUBSCRIBE response.

c6: IF A.163/19 OR A.163/21 THEN i ELSE n/a – – REGISTER response or SUBSCRIBE response.

c7: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

c8: IF A.162/52 THEN m ELSE n/a – – the SIP session timer.

c9: IF A.162/53 AND A.163/17 THEN m ELSE n/a – – the SIP Referred-By mechanism and REFER response.

c10: IF A.3/2 THEN m ELSE i – – P-CSCF.

c14: IF A.162/58 THEN m ELSE n/a – rejecting anonymous requests in the session initiation protocol.

c19: IF A.162/51 THEN i ELSE n/a – – an event state publication extension to the session initiation protocol.

c20: IF A.162/51 THEN m ELSE n/a – – an event state publication extension to the session initiation protocol.

p21: A.164/2 OR A.164/3 OR A.164/4 OR A.164/5 – – 1xx response.

p22: A.164/6 OR A.164/7 – – 2xx response.

p23: A.164/8 OR A.164/9 OR A.164/10 OR A.164/11 OR A.164/12 OR A.164/13 – – 3xx response.

p24: A.164/14 OR A.164/15 OR A.164/16 OR A.164/17 OR A.164/18 OR A.164/19 OR A.164/20 OR A.164/21 OR A.164/22 OR A.164/22A OR A.164/23 OR A.164/24 OR A.164/25 OR A.164/26 OR A.164/27 OR A.164/28 OR A.164/28A OR A.164/29 OR A.164/29A OR A.164/29B OR A.164/30 OR A.164/31 OR A.164/32 OR A.164/33 OR A.164/34 OR A.164/35 OR A.164/36 OR A.164/436 OR A.164/38 OR A.164/39 OR A.164/40 OR A.164/41 OR A.164/41A. – – 4xx response.

p25: A.164/42 OR A.164/43 OR A.164/44 OR A.164/45 OR A.164/46 OR A.164/47 OR A.164/48 OR A.164/49 – – 5xx response.

p26: A.164/50 OR A.164/51 OR A.164/52 OR A.164/53 – – 6xx response.

A.3.2.1 Major capabilities

Table A.317: Major capabilities

Item

Does the implementation support

Reference

RFC status

Profile status

Capabilities within main protocol

Extensions

22

Integration of resource management and SIP?

[30] [64]

O

m

23

Grouping of media lines

[53]

O

c1

24

Mapping of Media Streams to Resource Reservation Flows

[54]

O

c1

25

SDP Bandwidth Modifiers for RTCP Bandwidth

[56]

O

o (NOTE 1)

C1: IF A.3/1 THEN o.1 ELSE n/a – – UE role.

o.1: The procedure is mandatory in case if there are access specific procedures which the UE is using.

NOTE 1: For "video" and "audio" media types that utilise RTP/RTCP, it shall be specified. For other media types, it may be specified.

A.3.2.2 SDP types

Table A.318: SDP types

Item

Type

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

Session level description

1

v= (protocol version)

[39] 6

m

m

[39] 6

m

m

2

o= (owner/creator and session identifier)

[39] 6

m

m

[39] 6

m

m

3

s= (session name)

[39] 6

m

m

[39] 6

m

m

4

i= (session information)

[39] 6

o

o

[39] 6

m

m

5

u= (URI of description)

[39] 6

o

n/a

[39] 6

o

n/a

6

e= (email address)

[39] 6

o

n/a

[39] 6

o

n/a

7

p= (phone number)

[39] 6

o

n/a

[39] 6

o

n/a

8

c= (connection information)

[39] 6

o

o

[39] 6

m

m

9

b= (bandwidth information)

[39] 6

o

o (NOTE 1)

[39] 6

m

m

Time description (one or more per description)

10

t= (time the session is active)

[39] 6

m

m

[39] 6

m

m

11

r= (zero or more repeat times)

[39] 6

o

n/a

[39] 6

o

n/a

Session level description (continued)

12

z= (time zone adjustments)

[39] 6

o

n/a

[39] 6

o

n/a

13

k= (encryption key)

[39] 6

o

o

[39] 6

o

o

14

a= (zero or more session attribute lines)

[39] 6

o

o

[39] 6

m

m

Media description (zero or more per description)

15

m= (media name and transport address)

[39] 6

o

o

[39] 6

m

m

16

i= (media title)

[39] 6

o

o

[39] 6

o

o

17

c= (connection information)

[39] 6

c1

c1

[39] 6

c1

c1

18

b= (bandwidth information)

[39] 6

o

o (NOTE 1)

[39] 6

19

k= (encryption key)

[39] 6

o

o

[39] 6

o

o

20

a= (zero or more media attribute lines)

[39] 6

o

o

[39] 6

m

m

c1: IF (A.318/15 AND NOT A.318/8) THEN m ELSE (IF (A.318/15 AND A.318/8) THEN o ELSE n/a) — “c=” contained in session level description and SDP contains media descriptions.IF A.318/15 THEN m ELSE n/a.

NOTE 1: For "video" and "audio" media types that utilise RTP/RTCP, it shall be specified. For other media types, it may be specified.

Prerequisite A.318/14 OR A.318/20 – – a= (zero or more session/media attribute lines)

Table A.319: zero or more session / media attribute lines (a=)

Item

Field

Sending

Receiving

Ref.

RFC status

Profile status

Ref.

RFC status

Profile status

1

category (a=cat)

[39] 6

[39] 6

2

keywords (a=keywds)

[39] 6

[39] 6

3

name and version of tool (a=tool)

[39] 6

[39] 6

4

packet time (a=ptime)

[39] 6

[39] 6

5

maximum packet time (a=maxptime)

[39] 6

[39] 6

6

receive-only mode (a=recvonly)

[39] 6

[39] 6

7

send and receive mode (a=sendrecv)

[39] 6

[39] 6

8

send-only mode (a=sendonly)

[39] 6

[39] 6

9

whiteboard orientation (a=orient)

[39] 6

[39] 6

10

conference type (a=type)

[39] 6

[39] 6

11

character set (a=charset)

[39] 6

[39] 6

12

language tag (a=sdplang)

[39] 6

[39] 6

13

language tag (a=lang)

[39] 6

[39] 6

14

frame rate (a=framerate)

[39] 6

[39] 6

15

quality (a=quality)

[39] 6

[39] 6

16

format specific parameters (a=fmtp)

[39] 6

[39] 6

17

rtpmap attribute (a=rtpmap)

[39] 6

[39] 6

18

current-status attribute (a=curr)

[30] 5

c1

c1

[30] 5

c2

c2

19

desired-status attribute (a=des)

[30] 5

c1

c1

[30] 5

c2

c2

20

confirm-status attribute (a=conf)

[30] 5

c1

c1

[30] 5

c2

c2

21

media stream identification attribute (a=mid)

[53] 3

c3

c3

[53] 3

c4

c4

22

group attribute (a=group)

[53] 4

c5

c5

[53] 3

c6

c6

c1: IF A.317/22 THEN o ELSE n/a.

c2: IF A.317/22 THEN m ELSE n/a.

c3: IF A.317/23 THEN o ELSE n/a.

c4: IF A.317/23 THEN m ELSE n/a.

c5: IF A.317/24 THEN o ELSE n/a.

c6: IF A.317/24 THEN m ELSE n/a.

B.2.2.6 Emergency service

When activating a PDP context for emergency to perform emergency registration, based on the conditions in subclause 5.1.6.1 of this specification, the UE shall select an APN for emergency, as described in 3GPP TS 23.060 [4]. The procedures for PDP context activation and P-CSCF discovery, as described in subclause B.2.2.1 of this specification apply accordingly.

In order to find out whether the UE is attached to the home PLMN or to the visited PLMN, the UE shall compare the MCC values derived from its IMSI with the MCC of the PLMN the UE is attached to. If the MCC of the PLMN the UE is attached to does not match with the MCC derived from the IMSI, then for the purpose of emergency calls in the IM CN subsystem the UE shall consider to be attached to a VPLMN.

NOTE: In this respect an equivalent HPLMN, as defined in 3GPP TS 23.122 [4C] will be considered as a visited network.

B.3.1.1 P-Access-Network-Info header

The UE shall always include the P-Access-Network-Info header where indicated in subclause 5.1.

Annex C UICC and USIM Aspects for access to the IM CN subsystem

C.4 Provisioning of IMS parameters for UEs without ISIM or USIM

In case the UE contains neither a USIM application nor a ISIM application, the following IMS parameters are assumed to be available to the UE:

– a private user identity;

– a public user identity; and

– a home network domain name to address the SIP REGISTER request to.

These parameters may not necessarily reside in a UICC.

Annex D IP-Connectivity Access Network specific concepts when using I-WLAN to access IM CN subsystem

D.2.2.6 Emergency service

The details of network selection to select HPLMN or VPLMN are specified in 3GPP TS 24.234 [8C].

D.3 Application usage of SIP

D.3.1 Procedures at the UE

D.3.1.1 P-Access-Network-Info header

The UE shall always include the P-Access-Network-Info header where indicated in subclause 5.1.

Annex E IP-Connectivity Access Network specific concepts when using xDSL to access IM CN subsystem

E.2.2.6 Emergency service

If attached to network via xDSL access technology, the UE shall always consider being attached to its home operator’s network for the purpose of emergency calls.

NOTE: In xDSL the UE is unable to receive any indication from the network, that would allow the UE to determine, whether it is currently attached to its home operator’s network or to a different network, so the UE assumes itself always attached to the home operator’s network when connected via xDSL access technology.

E.3 Application usage of SIP

E.3.1 Procedures at the UE

E.3.1.1 P-Access-Network-Info header

The UE may, but need not, include the P-Access-Network-Info header where indicated in subclause 5.1.

Annex ZA (normative):
Cpc parameter definition