Content for TS 24.229 Word version: 18.4.0

1… 3… 4… 4.5… 5… 5.1.1.4… 5.1.2… 5.1.4… 5.2… 5.2.3… 5.2.6… 5.2.7… 5.3… 5.4… 5.4.1.2.2… 5.4.1.3… 5.4.2 5.4.3… 5.4.3.3… 5.4.4… 5.5… 5.7… 5.7.2… 5.8… 5.11… 6… 6.6… 7… 7.2A… 7.2A.6… 7.3… 7.9A… 8… A… A.2… A.2.1.4… A.2.1.4.7… A.2.1.4.8… A.2.1.4.10A… A.2.1.4.12… A.2.2… A.2.2.4… A.2.2.4.7… A.2.2.4.8… A.2.2.4.10A… A.2.2.4.12… A.3… A.3.3… B… C… E… F… H… I… K… L… L.2A… M… N… O… Q… R… S… U… U.2A… V… W…

A.2.2 Proxy role A.2.2.1 Introduction A.2.2.2 Major capabilities A.2.2.3 PDUs
...

A.2.2 Proxy role p. 652

A.2.2.1 Introduction p. 652

This subclause contains the ICS proforma Tables related to the proxy role. They need to be completed only for proxy implementations.

Prerequisite: A.2/2 - - proxy role

A.2.2.2 Major capabilities p. 653

Table A.162: Major capabilities

Item	Does the implementation support Capabilities within main protocol	Reference	RFC status	Profile status
3	initiate session release?	[26] 16	x	c27
4	stateless proxy behaviour?	[26] 16.11	o.1	c29
5	stateful proxy behaviour?	[26] 16.2	o.1	c28
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, [287]	o	c85
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.9	o	o
19D	adding or concatenating the Call-Info header before proxying the request or response?	[26] 20.9	o	o
19E	delete Contact headers from 3xx responses prior to relaying the response?	[26] 20	o	o
19F	proxy reading the contents of a body or including a body in a request or response?	[26]	o	c88
19G	proxy modifying the content of a body	TS 24.237	n/a	c103
	Extensions
20	SIP INFO method and package framework?	[25]	o	o
20A	legacy INFO usage?	[25] 2, 3	o	o
21	reliability of provisional responses in SIP?	[27]	o	i
22	the REFER method?	[36]	o	o
22A	clarifications for the use of REFER with RFC6665?	[231]	c113	c113
22B	explicit subscriptions for the REFER method?	[232]	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	a clarification on the use of GRUUs in the SIP event notification framework?	[232]	n/a	n/a
29	Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts	[35]	o	c6
30	private 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	c9
30B	act as entity within trust network that can route outside the trust network?	[34]	c5	c9
30C	act as entity passing on identity transparently independent of trust domain?	[34]	c5	c96
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, [52A] 4	c14	c15
37	the P-Called-Party-ID header extension?	[52] 4.2, [52A] 4`	c14	c16
38	the P-Visited-Network-ID header extension?	[52] 4.3, [52A] 4, [52B] 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, [52A] 4, [234] 2	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, [52A] 4	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, [52A] 4	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
47A	mediasec header field parameter for marking security mechanisms related to media?	Subclause 7.2A.7	n/a	c99
48	the Reason header field for the session initiation protocol	[34A]	o	c78
48A	carrying Q.850 codes in reason header fields in SIP (Session Initiation Protocol) responses?	[130]	o	o
48B	the location parameter for the SIP Reason header field?	[255]	o	o
48C	Handling of Identity Header Errors for Secure Telephone Identity Revisited (STIR) (carrying STIR codes in Reason header fields in SIP responses)?	[294]	o	c130
48D	Multiple SIP Reason Header Field Values?	[296]	o	c131
49	an extension to the session initiation protocol for symmetric response routeing	[56A]	o	m
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 Inititation Protocol (SIP) "Replaces" header?	[60]	o	o
55	the Session Inititation 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
57A	application of the "mp" optional header field parameter?	[66]	o	o
57B	application of the "rc" optional header field parameter?	[66]	o	o
57C	application of the "np" optional header field parameter?	[66]	o	o
58	Rejecting anonymous requests in the session initiation protocol?	[67]	o	o
59	session initiation protocol URIs for applications such as voicemail and interactive voice response	[68]	o	o
59A	Session Initiation Protocol (SIP) cause URI parameter for service number translation?	[230]	c111	c111
60	the P-User-Database private header extension?	[82]	o	c95
61	Session initiation protocol's non-INVITE transactions?	[84]	m	m
62	a uniform resource name for services	[69]	n/a	c35
63	obtaining and using GRUUs in the Session Initiation Protocol (SIP)	[93]	o	c36
65	the Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)?	[96]	o	o (note2)
66	the SIP P-Profile-Key private header extension?	[97]	o	c41
66A	making the first query to the database in order to populate the P-Profile-Key header?	[97]	c38	c39
66B	using the information in the P-Profile-Key header?	[97]	c38	c40
67	managing client initiated connections in SIP?	[92] 11	o	c42
68	indicating support for interactive connectivity establishment in SIP?	[102]	o	o
69	multiple-recipient MESSAGE requests in the session initiation protocol	[104]	n/a	n/a
70	SIP location conveyance?	[89]	o	c94
70A	addition or modification of location in a SIP method?	[89]	c44	c45
70B	passes on locations in SIP method without modification?	[89]	c44	c46
71	referring to multiple resources in the session initiation protocol?	[105]	n/a	n/a
72	conference establishment using request-contained lists in the session initiation protocol?	[106]	n/a	n/a
73	subscriptions to request-contained resource lists in the session initiation protocol?	[107]	n/a	n/a
74	dialstring parameter for the session initiation protocol uniform resource identifier?	[103]	o	n/a
75	the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular?	[111]	o	c60
76	the SIP P-Early-Media private header extension for authorization of early media?	[109] 8	o	c51
77	number portability parameters for the 'tel' URI?	[112]	o	c47
77A	assert or process carrier indication?	[112]	o	c48
77B	local number portability?	[112]	o	c50
79	extending the session initiation protocol Reason header for preemption events	[115]	c79	c79
80	communications resource priority for the session initiation protocol?	[116]	o	c80
80A	inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol?	[116] 4.2	c82	c82
80B	inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol?	[116] 4.2	c82	c82
81	addressing an amplification vulnerability in session initiation protocol forking proxies?	[117]	c52	c52
82	the remote application identification of applying signalling compression to SIP	[79] 9.1	o	c7
83	a session initiation protocol media feature tag for MIME application subtypes?	[120]	o	c53
84	SIP extension for the identification of services?	[121]	o	c54
84A	act as authentication entity within the trust domain for asserted service?	[121]	c55	c56
85	a framework for consent-based communications in SIP?	[125]	o	m
86	a mechanism for transporting user-to-user call control information in SIP?	[126]	o	c84
87	the SIP P-Private-Network-Indication private-header (P-Header)?	[134]	o	o
88	the SIP P-Served-User private header in the 3GG IM CN subsystem?	[133] 6	o	o
89	the SIP P-Served-User header extension for Originating CDIV session case?	[239] 4	c126	c126
90	marking SIP messages to be logged?	[140]	o	m
91	the 199 (Early Dialog Terminated) response code	[142]	o	c90
92	message body handling in SIP?	[150]	o	c89
93	indication of support for keep-alive?	[143]	o	c51
94	SIP Interface to VoiceXML Media Services?	[145]	o	c91
95	common presence and instant messaging (CPIM): message format?	[151]	o	o
96	instant message disposition notification?	[157]	o	o
97	requesting answering modes for SIP?	[158]	o	o
97A	adding, deleting or reading the Answer-Mode header or Priv-Answer-Mode before proxying the request or response?	[158]	o	c92
99	the early session disposition type for SIP?	[74B]	i	i
101	The Session-ID header?	[162]	o	o
102	correct transaction handling for 2xx responses to Session Initiation Protocol INVITE requests?	[163]	m	m
103	addressing Record-Route issues in the Session Initiation Protocol (SIP)?	[164]	o	o
104	essential correction for IPv6 ABNF and URI comparison in RFC3261?	[165]	m	m
105	suppression of session initiation protocol REFER method implicit subscription?	[173]	o	c100
106	Alert-Info URNs for the Session Initiation Protocol?	[175]	o	o
107	multiple registrations?	Subclause 3.1	n/a	c101
108	the SIP P-Refused-URI-List private-header?	[183]	o	c102
109	request authorization through dialog Identification in the session initiation protocol?	[184]	o	o
110	indication of features supported by proxy?	[190]	o	c104
111	registration of bulk number contacts?	[191]	o	c105
112	media control channel framework?	[146]	n/a	n/a
113	S-CSCF restoration procedures?	Subclause 4.14	n/a	n/a
114	SIP overload control?	[198]	o	o
114A	feedback control?	[199]	c106	c106
114B	distribution of load filters?	[201]	n/a	n/a
115	handling of a 380 (Alternative service) response?	Subclause 5.2.10	n/a	n/a
116	indication of adjacent network in the Via "received-realm" header field parameter?	[208]	o	c107
117	PSAP callback indicator?	[209]	o	c108
118	SIP URI parameter to indicate traffic leg?	[225]	o	c109
119	PCF or PCRF based P-CSCF restoration?	Subclause 4.14.2	n/a	c110
120	UDM/HSS or HSS based P-CSCF restoration?	Subclause 4.14.2	n/a	c112
121	the Relayed-Charge header field extension?	Subclause 7.2.12	n/a	c114
122	resource sharing?	Subclause 4.15	n/a	c115
123	the Cellular-Network-Info header extension?	Subclause 7.2.15	n/a	c116
124	the Priority-Share header field extension?	Subclause 7.2.16	n/a	c127
125	the Response-Source header field extension?	Subclause 7.2.17	n/a	o
126	authenticated identity management in the Session Initiation Protocol?	[252]	o	c128
127	a SIP response code for unwanted calls extension?	[254]	o	o
128	the Attestation-Info header field extension?	Subclause 7.2.18	n/a	o
129	the Origination-Id header field extension?	Subclause 7.2.19	n/a	o
130	Dynamic services interactions?	Subclause 4.18	n/a	c128
131	the Additional-Identity header field extension?	Subclause 7.2.20	n/a	o
132	RLOS?	Subclause 4.19	n/a	c129
133	the Priority-Verstat header field extension?	Subclause 7.2.21	n/a	c82
c1: IF A.162/5 THEN o ELSE n/a - - stateful proxy behaviour. c2: IF A.3/2 OR A.3/9A OR A.3/4 OR A.3/13A OR A.3A/88 THEN m ELSE o - - P-CSCF, IBCF (THIG), S-CSCF, ISC gateway function (THIG), ATCF (proxy). 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/9A OR A.3A/88 THEN m ELSE n/a - - P-CSCF, IBCF (THIG), ATFC (proxy). c7: IF A.3/2 AND (A.3D/1 OR A.3D/4) THEN m ELSE n/a - - P-CSCF and (IMS AKA plus IPsec ESP or SIP digest with TLS). c9: IF (A.3/2 OR A.3/4 OR A.3/9A OR A.3/13A) AND A.162/30 THEN m ELSE IF A.3/7C AND A.162/30 THEN o ELSE n/a - - P-CSCF or S-CSCF or IBCF (THIG) or ISC gateway function (THIG) or AS acting as proxy and extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks (NOTE 1). 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 IF A.3/11 THEN o ELSE n/a - - S-CSCF, E-CSCF. c13: IF A.162/31 AND (A.3/2 OR A.3/3 OR A.3/7C OR A.3/9A OR A.3/13A OR A.3A/88) THEN m ELSE n/a - - P-CSCF, I-CSCF, AS acting as a SIP proxy or IBCF (THIG), ISC gateway function (THIG), ATCF (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 OR A.3/9A OR A.3/13A) 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 IBCF (THIG) or ISC gateway function (THIG). c16: IF A.162/35 AND (A.3/2 OR A.3/3 OR A.3/4 OR A.3/9A OR A.3/13A) 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 or IBCF (THIG) or ISC gateway function (THIG). c17: IF A.162/35 AND (A.3/2 OR A.3/3 OR A.3/9A OR A.3/13A) 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 IBCF (THIG) or ISC gateway function (THIG). 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/3 OR A.3/4 THEN m ELSE o.8 - - P-CSCF or I-CSCF or S-CSCF. c29: IF A.3/2 OR A.3/4 THEN n/a ELSE IF A.3/3 THEN o ELSE o.8 - - P-CSCF or S-CSCF or I-CSCF. 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 IF A.3/7C OR A.3/9 OR A.3/13A THEN o ELSE n/a - - P-CSCF, E-CSCF, AS acting as proxy, IBCF, ISC gateway function (THIG). c36: IF A.3/4 THEN m ELSE n/a - - S-CSCF. c38: IF A.162/66 THEN o ELSE n/a - - the SIP P-Profile-Key private header. c39: IF A.162/66 AND (A.3/3 OR A.3/9A) THEN m ELSE n/a - - the SIP P-Profile-Key private header, I-CSCF or IBCF (THIG). c40: IF A.162/66 AND A.3/4 THEN m ELSE n/a - - the SIP P-Profile-Key private header, S-CSCF. c41: IF A.3/3 OR A.3/4 OR A.3/9A THEN o ELSE n/a - - I-CSCF or S-CSCF or IBCF (THIG). c42: IF A.162/107 THEN m ELSE n/a - - multiple registrations. c44: IF A.162/70 THEN o.5 ELSE n/a - - SIP location conveyance. c45: IF A.3/11 THEN m ELSE IF A.162/70 AND A.3/7C THEN o.6 ELSE n/a - - E-CSCF, SIP location conveyance, AS acting as a SIP proxy. c46: IF A.162/70 AND A.3/2 OR A.3/3 OR A.3/5 OR A.3/10 OR A.3A/88 THEN m ELSE IF A.162/70 AND A.3/7C THEN o.6 ELSE n/a - - SIP location conveyance, P-CSCF, I-CSCF, S-CSCF, BGCF, additional routeing functionality, ATCF (proxy). c47: IF A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C THEN o ELSE n/a - - I-CSCF, S-CSCF, BGCF, AS acting as a SIP proxy. c48: IF A.162/77 THEN m ELSE n/a - - number portability parameters for the 'tel' URI. c50: IF A.162/77 THEN m ELSE n/a - - number portability parameters for the 'tel' URI. c51: IF A.3/2 THEN m ELSE o - - P-CSCF. c52: IF A.162/6 THEN m ELSE o - - forking of initial requests. c53: IF A.3/4 THEN m ELSE n/a - - S-CSCF. c54: IF A.3/3 OR A.3/4 OR A.3/7 OR A.3/2 OR A.3/9A OR A.3/13A THEN m ELSE n/a - - I-CSCF, S-CSCF, BGCF, P-CSCF. IBCF (THIG), ISC gateway function (THIG). c55: IF A.162/84 THEN o ELSE n/a - - SIP extension for the identification of services. c56: IF A.3/4 AND A.162/84 THEN m ELSE n/a - - S-CSCF and SIP extension for the identification of services. c60: IF A.3/2 OR A.3/3 OR A.3/4 THEN o ELSE n/a - - P-CSCF, I-CSCF, S-CSCF. c78: IF A.3/2 OR A.3/4 OR A.3/9 OR A.162/79 OR A.162/3 THEN m ELSE o - - P-CSCF, S-CSCF, IBCF, extending the session initiation protocol Reason header for preemption events, initiate session release. c79: IF A.162/80 THEN o ELSE n/a - - communications resource priority for the session initiation protocol. c80: IF A.3/2 OR A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/13A THEN o ELSE n/a - - P-CSCF, I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, ISC gateway function (THIG). c82: IF A.162/80 THEN o ELSE n/a - - communications resource priority for the session initiation protocol. c84: A.3/2 OR A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/11 OR A.3/13A THEN o ELSE n/a - - P-CSCF, I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). c85: IF A.3/2 OR A.3/3 OR A.3/4 THEN o ELSE x - - P-CSCF, I-CSCF, S-CSCF. c88: IF A.3/2 OR A.3/4 OR A.3/7 OR A.3/7C OR A.3/9C OR A.3/11 OR A.3/13C OR A.3A/88 THEN m ELSE o - - P-CSCF, S-CSCF, AS, AS acting as a SIP proxy, IBCF (Screening of SIP signalling), E-CSCF, ISC gateway function (Screening of SIP signalling), ATCF (proxy). c89: IF A.162/19F THEN m ELSE n/a - - proxy reading the contents of a body or including a body in a request or response. c90: IF A.3/4 THEN m ELSE i - - S-CSCF. c91: IF A.3/4 THEN o ELSE n/a - - S-CSCF. c92: IF A.162/92 THEN o ELSE n/a - - requesting answering modes for SIP. c94: IF A.3/11 THEN m ELSE o - - E-CSCF. c95: IF A.3/3 OR A.3/4 OR A.3/7C THEN o ELSE n/a - - I-CSCF, S-CSCF, AS acting as a SIP proxy. c96: IF A.3/2 OR A.3/11 OR A.3A/88 THEN m ELSE n/a - - P-CSCF, E-CSCF, ATCF (proxy). c99: IF A.3/2A AND (A.3D/30 OR A.3D/20A OR A.3D/20B OR A.3D/20C OR A.3D/31) THEN m ELSE n/a - - P-CSCF (IMS-ALG) and end-to-access-edge media security using SDES, end-to-access-edge media security for MSRP using TLS and certificate fingerprints, end-to-access-edge media security for BFCP using TLS and certificate fingerprints, end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints, end-to-access-edge media security for RTP media using DTLS-SRTP and certificate fingerprints. c100: IF A.4/22 THEN o ELSE n/a - - the REFER method. c101: IF A.3/2 OR A.3/4 THEN m ELSE n/a - - P-CSCF, S-CSCF. c102: IF A.3/9B THEN m ELSE IF A.3/7A OR A.3/7B OR A.3/7D THEN o ELSE n/a - - IBCF (IMS-ALG), AS acting as terminating UA, AS acting as originating UA, AS performing 3rd party call control. c103: IF A.3A/88 THEN m ELSE n/a - - ATCF (proxy). c104: IF A.3/2 OR A.3A/50A OR A.3A/83 OR A.3A/88 THEN m ELSE o - - P-CSCF, Multimedia telephony application server, SCC application server, ATCF (proxy). c105: IF A.3/2 OR A.3/3 OR A.3/9 THEN o ELSE n/a - - P-CSCF, I-CSCF, IBCF. c106: IF A.162/114 THEN o.9 ELSE n/a - - SIP overload control. c107: IF A.162/115 THEN o.9 ELSE n/a - - indication of adjacent network in the Via "received-realm" header field parameter. c108: IF A.3/2 OR A.3/3 OR A.3/4 OR A.3/7 OR A.3/9 THEN o ELSE n/a - - P-CSCF, I-CSCF, S-CSCF, AS, IBCF. c109: IF A.3/2 OR A.3/4 OR A.3/5 OR A.3/9 OR A.3/10 OR A.3A/83 OR A.3A/88 OR A.3/3 THEN o ELSE n/a - - P-CSCF, S-CSCF, BGCF, IBCF, Additional routeing functionality, SCC application server, ATCF (proxy), I-CSCF. c110: IF A.3/2 OR A.3/4 OR A.3/9 THEN o ELSE n/a - - P-CSCF, S-CSCF, IBCF. c111: IF A.162/59 THEN o ELSE n/a - - session initiation protocol URIs for applications such as voicemail and interactive voice response (NOTE 3). c112: IF A.3/2 OR A.3/4 OR A.3/9 THEN o ELSE n/a - - P-CSCF, S-CSCF, IBCF. c113: IF A.162/22 THEN m ELSE n/a - - the REFER method. c114: IF A.3/4 OR A.3/7 OR A.3A/102 THEN o ELSE n/a.-.-.S-CSCF, AS, transit function. c115: IF A.3/2 OR A.3/7C OR A.3/9 THEN o ELSE n/a - - P-CSCF, AS acting as a SIP proxy, IBCF. c116: IF A.3/2 OR A.3.3 OR A.3/4 OR A.3/7C OR A.3/9 OR A.3/11B OR A.3A/88 OR A.3/5 THEN m ELSE n/a - - P-CSCF, I-CSCF, S-CSCF, AS acting as a proxy, IBCF, E-CSCF acting as a SIP Proxy, ATCF (proxy), BGCF. c126: IF A.162/88 THEN o ELSE n/a - - the SIP P-Served-User private header for the 3GPP IM CN subsystem. c127: IF A.3/2 OR A.3/7C OR A.3/9 THEN o ELSE n/a - - P-CSCF, AS acting as a SIP proxy, IBCF. c128: IF A.3/7 OR A.3/9 THEN o ELSE n/a - - AS, IBCF. c129: IF A.3/2 OR A.3/4 THEN o ELSE n/a - - P-CSCF, S-CSCF. c130: IF A.3/4 OR A.3/7C OR A.3/9 THEN o ELSE n/a - - S-CSCF, AS acting as a SIP proxy, IBCF. c131: IF A.162/48C AND (A.3/4 OR A.3/7C OR A.3/9) THEN o ELSE n/a - - Multiple SIP Reason Header Field Values (carrying STIR codes in Reason header fields in SIP responses), S-CSCF, AS acting as a SIP proxy, IBCF. 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. o.5: It is mandatory to support exactly one of these items. o.6: It is mandatory to support exactly one of these items. o.7: It is mandatory to support at least one of these items. o.8 It is mandatory to support at least one of these items. o.9: At least one of these capabilities is supported.
NOTE 1: 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. NOTE 2: Not applicable over Gm reference point (UE - P-CSCF). NOTE 3: AS performing a service number translation (e.g. Freephone)

A.2.2.3 PDUs p. 663

Table A.163: Supported methods

Item	PDU	Sending			Receiving
Item	PDU	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	ACK request	[26] 13	m	m	[26] 13	m	m
2	BYE request	[26] 16	m	m	[26] 16	m	m
3	BYE response	[26] 16	m	m	[26] 16	m	m
4	CANCEL request	[26] 16.10	m	m	[26] 16.10	m	m
5	CANCEL response	[26] 16.10	m	m	[26] 16.10	m	m
6	INFO request	[25] 4.2	c2	c2	[25] 4.2	c2	c2
7	INFO response	[25] 4.2	c2	c2	[25] 4.2	c2	c2
8	INVITE request	[26] 16	m	m	[26] 16	m	m
9	INVITE response	[26] 16	m	m	[26] 16	m	m
9A	MESSAGE request	[50] 4	c5	c5	[50] 7	c5	c5
9B	MESSAGE response	[50] 4	c5	c5	[50] 7	c5	c5
10	NOTIFY request	[28] 8.1.2	c3	c3	[28] 8.1.2	c3	c3
11	NOTIFY response	[28] 8.1.2	c3	c3	[28] 8.1.2	c3	c3
12	OPTIONS request	[26] 16	m	m	[26] 16	m	m
13	OPTIONS response	[26] 16	m	m	[26] 16	m	m
14	PRACK request	[27] 6	c6	c6	[27] 6	c6	c6
15	PRACK response	[27] 6	c6	c6	[27] 6	c6	c6
15A	PUBLISH request	[70] 11.1.1	c20	c20	[70] 11.1.1	c20	c20
15B	PUBLISH response	[70] 11.1.1	c20	c20	[70] 11.1.1	c20	c20
16	REFER request	[36] 3	c1	c1	[36] 3	c1	c1
17	REFER response	[36] 3	c1	c1	[36] 3	c1	c1
18	REGISTER request	[26] 16	m	m	[26] 16	m	m
19	REGISTER response	[26] 16	m	m	[26] 16	m	m
20	SUBSCRIBE request	[28] 8.1.1	c3	c3	[28] 8.1.1	c3	c3
21	SUBSCRIBE response	[28] 8.1.1	c3	c3	[28] 8.1.1	c3	c3
22	UPDATE request	[29] 7	c4	c4	[29] 7	c4	c4
23	UPDATE response	[29] 7	c4	c4	[29] 7	c4	c4
c1: IF A.162/22 THEN m ELSE n/a - - the REFER method. c2: IF A.162/20 OR A.162/20A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c3: IF A.162/27 THEN m ELSE n/a - - SIP specific event notification. c4: IF A.162/24 THEN m ELSE n/a - - the SIP UPDATE method. c5: IF A.162/33 THEN m ELSE n/a - - the SIP MESSAGE method. c6: IF A.162/21 THEN m ELSE n/a - - reliability of provisional responses. c20: IF A.4/51 THEN m ELSE n/a