A.2.2.4 PDU parameters

24.2293GPPIP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Release 18Stage 3TS

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

A.2.2.4.1 Status-codes

Table A.164: Supported-status codes

Item	Header		Sending				Receiving
Item	Header		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
101A	18x 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
5A	199 (Early Dialog Terminated)		[142] 11.1		c32	c32	[142] 11.1	c32		c32
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		c34	c34	[28] 8.3.1	c34		c34
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		c3	c3	[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
26A	417 (Unknown Resource Priority)		[116] 4.6.2		c25	c25	[116] 4.6.2	c25		c25
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	424 (Bad Location Information)		[89] 4.2		c23	c23	[89] 4.2	c24		c24
29AA	428 Use Identity Header		[252] 6.2.2		m	m	[252] 6.2.2	c35		c35
29B	429 (Provide Referrer Identity)		[59] 5		c9	c9	[59] 5	c9		c9
29C	430 (Flow Failed)		[92] 11		o	c21	[92] 11	m		c22
29D	433 (Anonymity Disallowed)		[67] 4		c14	c14	[67] 4	c14		c14
29DA	436 Bad Identity Info		[252] 6.2.2		m	m	[252] 6.2.2	c35		c35
29DB	437 Unsupported Credential		[252] 6.2.2		m	m	[252] 6.2.2	c35		c35
29DC	438 Invalid Identity Header		[252] 6.2.2		m	m	[252] 6.2.2	c35		c35
29E	439 (First Hop Lacks Outbound Support)		[92] 11		c28	c28	[92] 11	c29		c29
29F	440 (Max Breadth Exceeded)		[117] 5		c30	c30	[117] 5	c31		c31
29G	469 (Bad INFO Package)		[25] 4.2		c33	c33	[25] 4.2	c33		c33
29H	470 (Consent Needed)		[125] 5.9.2		c26	c26	[125] 5.9.2	c27		c27
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] 8.3.2		c4	c4	[28] 8.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
54	607 (Unwanted)		[254]		m	m	[254]	i		i
c1: IF A.163/3 OR A.163/9 OR A.163/9B OR A.163/11 OR A.163/13 OR A.163/15 OR A.163/15B OR A.163/17 OR A.163/19 OR A.163/21 OR A.163/23 AND A.162/5 THEN m ELSE n/a – – BYE response or INVITE response or MESSAGE response or NOTIFY response or OPTIONS response or PRACK response or PUBLISH response or REFER response or REGISTER response or SUBSCRIBE response or UPDATE response, stateful proxy. c2: IF A.163/3 OR A.163/9 OR A.163/9B OR A.163/11 OR A.163/13 OR A.163/15 OR A.163/15B OR A.163/17 OR A.163/19 OR A.163/21 OR A.163/23 THEN (IF A.162/5 THEN m ELSE i) ELSE n/a – – BYE response or INVITE response or MESSAGE response or NOTIFY response or OPTIONS response or PRACK response or PUBLISH response or REFER response or REGISTER response or SUBSCRIBE response or UPDATE 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. c21: IF A.4/57 AND A.3/2 THEN o ELSE n/a – – managing client initiated connections in SIP, P-CSCF. c22: IF A.4/57 AND A.3/4 THEN m ELSE i – – managing client initiated connections in SIP, S-CSCF. c23: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c24: IF A.162/70 THEN i ELSE n/a – – SIP location conveyance. c25: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c26: IF A.162/85 THEN m ELSE n/a – – a framework for consent-based communications in SIP. c27: IF A.162/85 THEN i ELSE n/a – – a framework for consent-based communications in SIP. c28: IF A.162/57 AND THEN m ELSE n/a – – managing client initiated connections in SIP. c29: IF A.162/57 AND THEN i ELSE n/a – – managing client initiated connections in SIP. c30: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c31: IF A.162/81 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c32: IF A.162/91 AND A.163/9 THEN m ELSE n/a – – INVITE response and 199 (Early Dialog Terminated) response. c33 IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c34: IF A.162/27 OR A.163/9B OR A.163/17 THEN m ELSE n/a – – SIP specific event notification or MESSAGE response or REFER response. c35 IF A.162/126 THEN m ELSE i – authenticated identity management in the Session Initiation Protocol p21: A.164/2 OR A.164/3 OR A.164/4 OR A.164/5 OR A.164/5A – – 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 – – 3xx response p24: A.164/13 OR 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/26A 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/29C OR A.164/29D OR A.164/29E OR A.164/29F OR A.164/29G OR A.164/29H 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.2.2.4.2 ACK method

Prerequisite A.163/1 – – ACK request

Table A.165: Supported header fields within the ACK request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Contact	[56B] 9.2	c10	c10	[56B] 9.2	c11	c11
2	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
3	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
4	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
5	Cellular-Network-Info	7.2.15	n/a	c27	7.2.15	n/a	c28
6	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
7	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
8	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
9	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
10	Content-Type	[26] 20.15	m	m	[26] 20.15	i	c3
11	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
12	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
13	From	[26] 20.20	m	m	[26] 20.20	m	m
13A	Max-Breadth	[117] 5.8	c15	c15	[117] 5.8	c16	c16
14	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
15	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	c3
15A	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c20	c20	[52] 4.4, [52A] 4, [234] 2	c21	c21
15BA	Priority-Share	Subclause 7.2.16	n/a	c29	Subclause 7.2.16	n/a	c29
15C	Privacy	[33] 4.2	c6	c6	[33] 4.2	c7	c7
15D	P-Charging-Vector	[52] 4.6, [52A] 4	c22	c22	[52] 4.6, [52A] 4	c23	c23
16	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c4	c4
17	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
17A	Reason	[34A] 2	c8	c8	[34A] 2	c9	c9
17B	Record-Route	[26] 20.30	m	m	[26] 20.30	c26	c26
17C	Recv-Info	[25] 5.2.3	c17	c17	[25] 5.2.3	c18	c18
17D	Reject-Contact	[56B] 9.2	c10	c10	[56B] 9.2	c11	c11
17E	Relayed-Charge	7.2.12	n/a	c24	7.2.12	n/a	c24
17F	Request-Disposition	[56B] 9.1	c10	c10	[56B] 9.1	c11	c11
18	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
18A	Resource-Priority	[116] 3.1	c12	c12	[116] 3.1	c12	c47
18B	Resource-Share	Subclause 4.15	n/a	c25	Subclause 4.15	n/a	c25
19	Route	[26] 20.34	m	m	[26] 20.34	m	m
19A	Session-ID	[162]	c19	c19	[162]	c19	c19
20	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
21	To	[26] 20.39	m	m	[26] 20.39	m	m
22	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
23	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.3/2 OR A.3/4 THEN m ELSE i – – P-CSCF or S-CSCF. c4: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c8: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c9: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c10: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c11: IF A.162/50 THEN i ELSE n/a – – caller preferences for the session initiation protocol. c12: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c15: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c16: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c17: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c18: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c19: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c20: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c21: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c22: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c23: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c24: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c25: IF A.162/122 THEN o ELSE n/a – – resource sharing. c26: IF A.162/14 THEN o ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c27: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c28: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c29: IF A.162/124 THEN o ELSE n/a – – priority sharing.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/1 – – ACK request

Table A.166: Supported message bodies within the ACK request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.3 BYE method

Prerequisite A.163/2 – – BYE request

Table A.167: Supported header fields within the BYE request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
1A	Accept-Contact	[56B] 9.2	c22	c22	[56B] 9.2	c23	c23
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
3A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
4	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
5	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
6	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
6A	Cellular-Network-Info	7.2.15	n/a	c37	7.2.15	n/a	c38
7	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	c3
8	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	c3
9	Content-Language	[26] 20.13	m	m	[26] 20.13	i	c3
10	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
11	Content-Type	[26] 20.15	m	m	[26] 20.15	i	c3
12	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
13	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
14	From	[26] 20.20	m	m	[26] 20.20	m	m
14A	Geolocation	[89] 4.1	c26	c26	[89] 4.1	c27	c27
14B	Geolocation-Routing	[89] 4.1	c26	c26	[89] 4.1	c27	c27
14C	Max-Breadth	[117] 5.8	c33	c33	[117] 5.8	c34	c34
15	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
16	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	c3
16A	P-Access-Network-Info	[52] 4.4, [234] 2	c13	c13	[52] 4.4, [234] 2	c14	c14
16B	P-Asserted-Identity	[34] 9.1	c9	c9	[34] 9.1	c10	c10
16C	P-Charging-Function-Addresses	[52] 4.5	c17	c17	[52] 4.5	c18	c18
16D	P-Charging-Vector	[52] 4.6	c15	c15	[52] 4.6	c16	c16
16F	P-Preferred-Identity	[34] 9.2	x	x	[34] 9.2	c8	n/a
16G	Privacy	[33] 4.2	c11	c11	[33] 4.2	c12	c12
17	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c4	c4
18	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
18A	Reason	[34A] 2	c20	c20	[34A] 2	c21	c21
19	Record-Route	[26] 20.30	m	m	[26] 20.30	c7	c7
19A	Referred-By	[59] 3	c24	c24	[59] 3	c25	c25
19B	Reject-Contact	[56B] 9.2	c22	c22	[56B] 9.2	c23	c23
19C	Relayed-Charge	7.2.12	n/a	c36	7.2.12	n/a	c36
19D	Request-Disposition	[56B] 9.1	c22	c22	[56B] 9.1	c23	c23
20	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
20A	Resource-Priority	[116] 3.1	c28	c28	[116] 3.1	c28	c28
21	Route	[26] 20.34	m	m	[26] 20.34	m	m
21A	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c19	c19
21B	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c19	c19
21C	Session-ID	[162]	c35	c35	[162]	c35	c35
22	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
23	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
24	To	[26] 20.39	m	m	[26] 20.39	m	m
25	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
25A	User-to-User	[126] 7	c29	c29	[126] 7	c30	c30
26	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.3/2 OR A.3/4 THEN m ELSE i – – P-CSCF or S-CSCF. c4: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c9: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c10: IF A.162/30A OR A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c11: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c12: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c13: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c16: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c17: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c18: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c19: IF A.162/47 OR A.162/47A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c20: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c21: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c22: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c23: IF A.162/50 THEN i ELSE n/a – – caller preferences for the session initiation protocol. c24: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c25: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c26: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c27: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c28: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c29: IF A.162/86 THEN m – – transporting user to user information for call centers using SIP. c30: IF A.162/86 THEN i – – transporting user to user information for call centers using SIP. c33: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c34: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c35: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c36: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c37: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c38: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/2 – – BYE request

Table A.168: Supported message bodies within the BYE request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	XML Schema for PSTN	[11B]	n/a	c1	[11B]	n/a	i
2	VoiceXML expr / namelist data	[145] 4.2	m	c2	[145] 4.2	m	c2
3	application/vnd.3gpp.ussd	[8W]	n/a	m	[8W]	n/a	i
c1: 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 m ELSE n/a – – I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). c2: IF A.162/94 THEN m ELSE n/a – – SIP Interface to VoiceXML Media Services.

Table A.169: Void

Prerequisite A.163/3 – – BYE response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.169A: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/3 – – BYE response

Table A.170: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
1A	Cellular-Network-Info	7.2.15	n/a	c23	7.2.15	n/a	c24
2	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	c2
3	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	c2
4	Content-Language	[26] 20.13	m	m	[26] 20.13	i	c2
5	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
6	Content-Type	[26] 20.15	m	m	[26] 20.15	i	c2
7	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
8	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
9	From	[26] 20.20	m	m	[26] 20.20	m	m
9A	Geolocation-Error	[89] 4.3	c15	c15	[89] 4.3	c16	c16
10	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	c2
10A	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c12	c12	[52] 4.4, [52A] 4, [234] 2	c13	c13
10B	P-Asserted-Identity	[34] 9.1	c4	c4	[34] 9.1	c5	c5
10C	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c10	c10	[52] 4.5, [52A] 4	c11	c11
10D	P-Charging-Vector	[52] 4.6, [52A] 4	c8	c8	[52] 4.6, [52A] 4	c9	c9
10F	P-Preferred-Identity	[34] 9.2	x	x	[34] 9.2	c3	n/a
10G	Privacy	[33] 4.2	c6	c6	[33] 4.2	c7	c7
10H	Relayed-Charge	7.2.12	n/a	c22	7.2.12	n/a	c22
10I	Require	[26] 20.32	m	m	[26] 20.32	c14	c14
10J	Server	[26] 20.35	m	m	[26] 20.35	i	i
10K	Session-ID	[162]	c21	c21	[162]	c21	c21
11	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
12	To	[26] 20.39	m	m	[26] 20.39	m	m
12A	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
12B	User-to-User	[126] 7	c17	c17	[126] 7	c18	c18
13	Via	[26] 20.42	m	m	[26] 20.42	m	m
14	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.3/2 OR A.3/4 THEN m ELSE i – – P-CSCF or S-CSCF. c3: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c4: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c5: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c6: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c8: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c9: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c10: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c11: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c12: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c13: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c15: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c16: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c17: IF A.162/86 THEN m – – transporting user to user information for call centers using SIP. c18: IF A.162/86 THEN i – – transporting user to user information for call centers using SIP. c21: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c22: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c23: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.

Prerequisite A.163/3 – – BYE response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.171: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Accept-Resource-Priority	[116] 3.2	c4	c4	[116] 3.2	c4	c4
0B	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	i	c1
1	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
2	Record-Route	[26] 20.30	m	m	[26] 20.30	c3	c3

5	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c3: IF A.162/15 THEN o ELSE i – – the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.163/3 – – BYE response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.171A: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.163/3 – BYE response

Prerequisite: A.164/103 OR A.164/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.172: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Contact	[26] 20.10	m	m	[26] 20.10	c1	c1
c1: IF A.162/19E THEN m ELSE i – – deleting Contact headers.

Prerequisite A.163/3 – – BYE response

Prerequisite: A.164/14 – – Additional for 401 (Unauthorized) response

Table A.173: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
8	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/3 – – BYE response

Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.174: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.175: Void

Prerequisite A.163/3 – – BYE response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.176: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
6	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/3 – – BYE response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type) response

Table A.177: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/3 – – BYE response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.177A: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.163/3 – – BYE response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.178: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
5	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/3 – – BYE response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.178A: Supported header fields within the BYE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.179: Void

Prerequisite A163/3 – – BYE response

Prerequisite: A.164/6 – – Additional for 200 (OK) response

Table A.180: Supported message bodies within the BYE response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	VoiceXML expr / namelist data	[145] 4.2	o	c1	[145] 4.2	o	c1
c1: IF A.162/94 THEN o ELSE n/a – – SIP Interface to VoiceXML Media Services.

A.2.2.4.4 CANCEL method

Prerequisite A.163/4 – – CANCEL request

Table A.181: Supported header fields within the CANCEL request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Contact	[56B] 9.2	c10	c10	[56B] 9.2	c11	c11
5	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
6	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
8	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
8A	Content-Type	[26] 20.15	c21	c21	[26] 20.15	o	o
9	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
10	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
11	From	[26] 20.20	m	m	[26] 20.20	m	m
11A	Max-Breadth	[117] 5.8	c15	c15	[117] 5.8	c16	c16
12	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
14	Privacy	[33] 4.2	c3	c3	[33] 4.2	c4	c4
15	Reason	[34A] 2	c8	c8	[34A] 2	c9	c9
16	Record-Route	[26] 20.30	m	m	[26] 20.30	c7	c7
17	Reject-Contact	[56B] 9.2	c10	c10	[56B] 9.2	c11	c11
17A	Relayed-Charge	7.2.12	n/a	c20	7.2.12	n/a	c20
17B	Request-Disposition	[56B] 9.1	c10	c10	[56B] 9.1	c11	c11
17C	Resource-Priority	[116] 3.1	c12	c12	[116] 3.1	c12	c12
18	Route	[26] 20.34	m	m	[26] 20.34	m	m
18A	Session-ID	[162]	c17	c17	[162]	c17	c17
19	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
20	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
21	To	[26] 20.39	m	m	[26] 20.39	m	m
22	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
23	Via	[26] 20.42	m	m	[26] 20.42	m	m
c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c4: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c9: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c10: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c11: IF A.162/50 THEN i ELSE n/a – – caller preferences for the session initiation protocol. c12: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c15: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c16: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c17: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c20: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c21: IF A.162/23 OR A.182/1 THEN m ELSE o – – integration of resource management and SIP or XML schema for PSTN.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/4 – – CANCEL request

Table A.182: Supported message bodies within the CANCEL request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	XML Schema for PSTN	[11B]		c1	[11B]		i
c1: 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 m ELSE n/a – – I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG).

Prerequisite A.163/5 – – CANCEL response for all status-codes

Table A.183: Supported header fields within the CANCEL response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
5	From	[26] 20.20	m	m	[26] 20.20	m	m
5C	Privacy	[33] 4.2	c2	c2	[33] 4.2	c3	c3
5D	Relayed-Charge	7.2.12	n/a	c9	7.2.12	n/a	c9
5C	Session-ID	[162]	c6	c6	[162]	c6	c6
6	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
7	To	[26] 20.39	m	m	[26] 20.39	m	m
7A	User-Agent	[26] 20.41	o		[26] 20.41	o
8	Via	[26] 20.42	m	m	[26] 20.42	m	m
9	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c3: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c6: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c9: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension.

Prerequisite A.163/5 – – CANCEL response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.184: Supported header fields within the CANCEL response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c4	c4	[116] 3.2	c4	c4
2	Record-Route	[26] 20.30	m	m	[26] 20.30	c3	c3
4	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c3: IF A.162/15 THEN o ELSE i – – the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.163/5 – – CANCEL response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.184A: Supported header fields within the CANCEL response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Table A.185: Void

Prerequisite A.163/5 – – CANCEL response

Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 – – Additional 404 (Not Found), 413 (Request for Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.186: Supported header fields within the CANCEL response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Prerequisite A.163/5 – – CANCEL response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.186A: Supported header fields within the CANCEL response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Table A.187: Void

Table A.188: Void

Prerequisite A.163/5 – – CANCEL response

Table A.189: Supported message bodies within the CANCEL response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.5 Void

A.2.2.4.6 INFO method

Prerequisite A.163/6 – – INFO request

Table A.190: Supported header fields within the INFO request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
4	Allow	[26] 20.5	m	m	[50] 10	i	i
5	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
6	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
7	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
7A	Call-Info	[26] 20.9	m	m	[26] 20.9	c3	c3
8	Cellular-Network-Info	7.2.15	n/a	c54	7.2.15	n/a	c55
9	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
10	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
11	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
12	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
13	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
14	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
15	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
16	From	[26] 20.20	m	m	[26] 20.20	m	m
17	Geolocation	[89] 4.1	c36	c36	[89] 4.1	c37	c37
17A	Geolocation-Routing	[89] 4.1	c36	c36	[89] 4.1	c37	c37
18	Info-Package	[25] 7.2	c50	c50	[25] 7.2	c51	c51
19	Max-Breadth	[117] 5.8	c48	c48	[117] 5.8	c49	c49
20	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
21	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
22	P-Access-Network-Info	[52] 4.4, [234] 2	c23	c23	[52] 4.4, [234] 2	c24	c24
23	P-Charging-Function-Addresses	[52] 4.5	c21	c21	[52] 4.5	c22	c22
24	P-Charging-Vector	[52] 4.6	c19	c19	[52] 4.6	c20	c20
26	Privacy	[33] 4.2	c12	c12	[33] 4.2	c13	c13
27	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c8	c8
28	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
29	Reason	[34A] 2	c26	c26	[34A] 2	c27	c27
30	Record-Route	[26] 20.30	m	m	[26] 20.30	c7	c7
31	Referred-By	[59] 3	c30	c30	[59] 3	c31	c31
32	Relayed-Charge	7.2.12	n/a	c53	7.2.12	n/a	c53
33	Request-Disposition	[56B] 9.1	c28	c28	[56B] 9.1	c28	c28
34	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
35	Resource-Priority	[116] 3.1	c38	c38	[116] 3.1	c38	c38
36	Route	[26] 20.34	m	m	[26] 20.34	m	m
37	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c25	c25
38	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c25	c25
38A	Session-ID	[162]	c52	c52	[162]	c52	c52
39	Subject	[26] 20.36	m	m	[26] 20.36	i	i
40	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
41	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
42	To	[26] 20.39	m	m	[26] 20.39	m	m
43	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
44	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c12: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c13: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c19: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c20: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c21: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c22: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c23: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c25: IF A.162/47 OR A.162/47A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c26: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c27: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c28: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c30: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c31: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c36: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c37: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c38: IF A.162/80A THEN m ELSE n/a – – inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c48: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c49: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c50: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c51: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c52: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c53: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c54: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c55: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/6 – – INFO request

Table A.191: Supported message bodies within the INFO request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Info-Package	[25]	m	m	[25]	i	i

Prerequisite A.163/7 – – INFO response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.192: Supported header fields within the INFO response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/7 – – INFO response for all remaining status-codes

Table A.193: Supported header fields within the INFO response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Call-Info	[26] 20.9	m	m	[26] 20.9	c3	c3
2A	Cellular-Network-Info	7.2.15	n/a	c23	7.2.15	n/a	c24
3	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
4	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
5	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
6	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
7	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
8	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
9	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
10	From	[26] 20.20	m	m	[26] 20.20	m	m
11	Geolocation-Error	[89] 4.3	c17	c17	[89] 4.3	c18	c18
12	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
13	Organization	[26] 20.25	m	m	[26] 20.25	c2	c2
14	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c13	c13	[52] 4.4, [52A] 4, [234] 2	c14	c14
15	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c11	c11	[52] 4.5, [52A] 4	c12	c12
16	P-Charging-Vector	[52] 4.6, [52A] 4	c9	c9	[52] 4.6, [52A] 4	c10	c10
18	Privacy	[33] 4.2	c7	c7	[33] 4.2	c8	c8
18A	Relayed-Charge	7.2.12	n/a	c22	7.2.12	n/a	c22
19	Require	[26] 20.32	m	m	[26] 20.32	c15	c15
20	Server	[26] 20.35	m	m	[26] 20.35	i	i
20A	Session-ID	[162]	c21	c21	[162]	c21	c21
21	Timestamp	[26] 20.38	i	i	[26] 20.38	i	i
22	To	[26] 20.39	m	m	[26] 20.39	m	m
23	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
24	Via	[26] 20.42	m	m	[26] 20.42	m	m
25	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c3: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c7: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c9: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c10: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c11: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c12: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c13: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c17: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c18: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c21: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c22: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c23: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.

Prerequisite A.163/7 – – INFO response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.194: Supported header fields within the INFO response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
4	Accept-Resource-Priority	[116] 3.2	c4	c4	[116] 3.2	c4	c4
5	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
6	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
8	Record-Route	[26] 20.30	m	m	[26] 20.30	c5	c5
9	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c4: IF A.162/80A THEN m ELSE n/a – – inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c5: IF A.162/15 THEN o ELSE i – – the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing.

Prerequisite A.163/7 – – INFO response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.195: Supported header fields within the INFO response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.163/7 – – INFO response

Prerequisite: A.164/103 OR A.164/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.195A: Void

Prerequisite A.163/7 – – INFO response

Prerequisite: A.164/14 – – Additional for 401 (Unauthorized) response

Table A.196: Supported header fields within the INFO response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
6	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/7 – – INFO response

Table A.197: Supported header fields within the INFO response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.198: Void

Prerequisite A.163/7 – – INFO response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type)

Table A.199: Supported header fields within the INFO response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/7 – – INFO response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.199A: Supported header fields within the INFO response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80A THEN m ELSE n/a – – inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

Prerequisite A.163/7 – – INFO response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.200: Supported header fields within the INFO response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
5	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/7 – – INFO response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.200A: Supported header fields within the INFO response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.201: Void

Table A.202: Void

Prerequisite A.163/7 – – INFO response

Table A.203: Supported message bodies within the INFO response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.7 INVITE method

Prerequisite A.163/8 – – INVITE request

Table A.204: Supported header fields within the INVITE request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
1A	Accept-Contact	[56B] 9.2	c34	c34	[56B] 9.2	c34	c35
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
3A	Additional-Identity	7.2.20	n/a	c85	7.2.20	n/a	c85
4	Alert-Info	[26] 20.4	c2	c2	[26] 20.4	c3	c3
5	Allow	[26] 20.5	m	m	[26] 20.5	i	i
6	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
7	Answer-Mode	[158]	c67	c67	[158]	c68	c68
7A	Attestation-Info	7.2.18	n/a	c82	7.2.18	n/a	c82
8	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
9	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
10	Call-Info	[26] 20.9	m	m	[26] 20.9	c12	c12
10A	Cellular-Network-Info	7.2.15	n/a	c78	7.2.15	n/a	c79
11	Contact	[26] 20.10	m	m	[26] 20.10	i	i
12	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	c6
13	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	c6
14	Content-Language	[26] 20.13	m	m	[26] 20.13	i	c6
15	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
16	Content-Type	[26] 20.15	m	m	[26] 20.15	i	c6
17	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
18	Date	[26] 20.17	m	m	[26] 20.17	c4	c4
19	Expires	[26] 20.19	m	m	[26] 20.19	i	i
19A	Feature-Caps	[190]	c73	c73	[190]	c73	c73
20	From	[26] 20.20	m	m	[26] 20.20	m	m
20A	Geolocation	[89] 4.1	c47	c47	[89] 4.1	c48	c48
20B	Geolocation-Routing	[89] 4.1	c47	c47	[89] 4.1	c48	c48
20C	History-Info	[66] 4.1	c43	c43	[66] 4.1	c43	c43
20D	Identity	[252] 4	c81	c81	[252] 4	c81	c81
21	In-Reply-To	[26] 20.21	m	m	[26] 20.21	i	i
21A	Join	[61] 7.1	c41	c41	[61] 7.1	c42	c42
21B	Max-Breadth	[117] 5.8	c63	c63	[117] 5.8	c64	c64
22	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
23	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	c6
23A	Min-SE	[58] 5	o	o	[58] 5	o	o
24	Organization	[26] 20.25	m	m	[26] 20.25	c5	c5
24AA	Origination-Id	7.2.19	n/a	c83	7.2.19	n/a	c83
24A	P-Access-Network-Info	[52] 4.4, [234] 2	c28	c28	[52] 4.4, [234] 2	c29	c30
24B	P-Asserted-Identity	[34] 9.1	c15	c15	[34] 9.1	c16	c16
24C	P-Asserted-Service	[121] 4.1	c53	c53	[121] 4.1	c54	c54
24D	P-Called-Party-ID	[52] 4.2	c19	c19	[52] 4.2	c20	c21
24E	P-Charging-Function-Addresses	[52] 4.5	c26	c27	[52] 4.5	c26	c27
24F	P-Charging-Vector	[52] 4.6	c24	c24	[52] 4.6	c25	c25
24H	P-Early-Media	[109] 8	o	c50	[109] 8	o	c50
25	P-Media-Authorization	[31] 5.1	c9	x	[31] 5.1	n/a	n/a
25A	P-Preferred-Identity	[34] 9.2	x	c69	[34] 9.2	c14	c14
25B	P-Preferred-Service	[121] 4.2	x	x	[121] 4.2	c52	c52
25C	P-Private-Network-Indication	[134]	c59	c59	[134]	c59	c59
25D	P-Profile-Key	[97] 5	c45	c45	[97] 5	c46	c46
25E	P-Served-User	[133] 6	c60	c60	[133] 6	c60	c60
25F	P-User-Database	[82] 4	c44	c44	[82] 4	c44	c44
25G	P-Visited-Network-ID	[52] 4.3	c22	o	[52] 4.3	c23	o
26	Priority	[26] 20.26	m	m	[26] 20.26	i	c74
26AA	Priority-Share	Subclause 7.2.16	n/a	c80	Subclause 7.2.16	n/a	c80
26A	Privacy	[33] 4.2	c17	c17	[33] 4.2	c18	c18
26AB	Priority-Verstat	Subclause 7.2.21	n/a	c86	Subclause 7.2.21	n/a	c86
26B	Priv-Answer-Mode	[158]	c67	c67	[158]	c68	c68
27	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c13	c13
28	Proxy-Require	[26] 20.29, [34] 4	m	m	[26] 20.29, [34] 4	m	m
28A	Reason	[34A] 2	c32	c32	[34A] 2	c33	c33
29	Record-Route	[26] 20.30	m	m	[26] 20.30	c11	c11
29A	Recv-Info	[25] 5.2.3	c65	c65	[25] 5.2.3	c66	c66
30	Referred-By	[59] 3	c37	c37	[59] 3	c38	c38
31	Reject-Contact	[56B] 9.2	c34	c34	[56B] 9.2	c34	c35
31A	Relayed-Charge	7.2.12	n/a	c76	7.2.12	n/a	c76
31B	Replaces	[60] 6.1	c39	c39	[60] 6.1	c40	c40
31C	Reply-To	[26] 20.31	m	m	[26] 20.31	i	i
31D	Request-Disposition	[56B] 9.1	c34	c34	[56B] 9.1	c34	c34
32	Require	[26] 20.32	m	m	[26] 20.32	c7	c7
32A	Resource-Priority	[116] 3.1	c49	c49	[116] 3.1	c49	c49
32B	Restoration-Info	Subclause 7.2.11	n/a	c75	Subclause 7.2.11	n/a	c75
32C	Resource-Share	Subclause 4.15	n/a	c77	Subclause 4.15	n/a	c77
33	Route	[26] 20.34	m	m	[26] 20.34	m	m
33A	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c31	c31
33B	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c31	c31

33DA	Service-Interact-Info	Subclause 7.2.14	n/a	c84	Subclause 7.2.14	n/a	c84
33D	Session-Expires	[58] 4	c36	c36	[58] 4	c36	c36
33E	Session-ID	[162]	c70	c70	[162]	c70	c70
34	Subject	[26] 20.36	m	m	[26] 20.36	i	i
35	Supported	[26] 20.37	m	m	[26] 20.37	c8	c8
35A	Target-Dialog	[184] 7	c71	c71	[184] 7	c72	c72
36	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
37	To	[26] 20.39	m	m	[26] 20.39	m	m
37A	Trigger-Consent	[125] 5.11.2	c55	c55	[125] 5.11.2	c56	c56
38	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
38A	User-to-User	[126] 7	c57	c57	[126] 7	c58	c58
39	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/10 THEN n/a ELSE m – – suppression or modification of alerting information data. c3: IF A.162/10 THEN m ELSE i – – suppression or modification of alerting information data. c4: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c5: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c6: IF A.3/2 OR A.3/4 THEN m ELSE i – – P-CSCF or S-CSCF. c7: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c8: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c9: IF A.162/26 THEN m ELSE n/a – – SIP extensions for media authorization. c11: IF A.162/14 THEN m ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c12: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c13: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c14: IF A.162/30A OR A.162/30C THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c15: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c16: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c17: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c18: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c19: IF A.162/37 THEN m ELSE n/a – – the P-Called-Party-ID header extension. c20: IF A.162/37 THEN i ELSE n/a – – the P-Called-Party-ID header extension. c21: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a – – the P-Called-Party-ID header extension and P-CSCF or (I-CSCF or IBCF (THIG)). c22: IF A.162/38 THEN m ELSE n/a – – the P-Visited-Network-ID header extension. c23: IF A.162/39 THEN m ELSE i – – reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c24: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c25: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c26: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c27: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c28: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c29: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c30: IF A.162/43 OR (A.162/41 AND A.3/2) THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension (with or without P-CSCF). c31: IF A.162/47 OR A.162/47A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c32: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c33: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c34: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c35: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a – – caller preferences for the session initiation protocol, and S-CSCF. c36: IF A.162/52 THEN m ELSE n/a – – the SIP session timer. c37: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c38: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c39: IF A.162/54 THEN m ELSE n/a – – the Session Inititation Protocol (SIP) "Replaces" header. c40: IF A.162/54 THEN i ELSE n/a – – the Session Inititation Protocol (SIP) "Replaces" header.
c41: IF A.162/55 THEN m ELSE n/a – – the Session Inititation Protocol (SIP) "Join" header. c42: IF A.162/55 THEN i ELSE n/a – – the Session Inititation Protocol (SIP) "Join" header. c43: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c44: IF A.162/60 THEN m ELSE n/a – – the P-User-Database private header extension. c45: IF A.162/66A THEN m ELSE n/a – – making the first query to the database in order to populate the P-Profile-Key header. c46: IF A.162/66B THEN m ELSE n/a – – using the information in the P-Profile-Key header. c47: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c48: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c49: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c50: IF A.162/76 THEN m ELSE n/a – – the SIP P-Early-Media private header extension for authorization of early media. c52: IF A.162/84A THEN m ELSE n/a – – act as authentication entity within the trust domain for asserted service. c53: IF A.162/84 THEN m ELSE n/a – – SIP extension for the identification of services. c54: IF A.162/84 OR A.162/30B THEN m ELSE i – – SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network. c55: IF A.162/85 THEN m ELSE n/a – – a framework for consent-based communications in SIP. c56: IF A.162/85 THEN i ELSE n/a – – a framework for consent-based communications in SIP. c57: IF A.162/86 THEN m – – transporting user to user information for call centers using SIP. c58: IF A.162/86 THEN i – – transporting user to user information for call centers using SIP. c59: IF A.162/87 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header). c60: IF A.162/88 THEN m – – the SIP P-Served-User private header. c63: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c64: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c65: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c66: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c67: IF A.162/97 THEN m ELSE n/a – – requesting answering modes for SIP. c68: IF NOT A.162/97 THEN n/a ELSE IF A.162/97A THEN m ELSE i – – requesting answering modes for SIP, adding, deleting or reading the Answer-Mode header or Priv-Answer-Mode header before proxying the request or response. c69: IF A.162/30C THEN m ELSE x – – act as entity passing on identity transparently independent of trust domain. c70: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c71: IF A.162/109 THEN m ELSE n/a – – request authorization through dialog Identification in the session initiation protocol. c72: IF A.162/109 THEN i ELSE n/a – – request authorization through dialog Identification in the session initiation protocol. c73: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c74: IF A.162/115 THEN m ELSE i – – PSAP callback indicator. c75: IF A.162/119 THEN o ELSE n/a – – PCRF based P-CSCF restoration. c76: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c77: IF A.162/122 THEN o ELSE n/a – – resource sharing. c78: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c79: IF A.162/43 OR (A.162/41A AND A.3/2) THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension (with or without P-CSCF). c80: IF A.162/124 THEN o ELSE n/a – – priority sharing. c81: IF A.162/126 THEN o ELSE n/a – – authenticated identity management in the Session Initiation Protocol. c82: IF A.162/128 THEN o ELSE n/a – – the Attestation-Info header field extension. c83: IF A.162/129 THEN o ELSE n/a – – the Origination-Id header field extension. c84: IF A.162/130 THEN m ELSE n/a – – Dynamic services interactions. c85: IF A.162/131 THEN o ELSE n/a – – the Additional-Identity header field extension. c86: IF A.162/80 AND A.162/133 THEN o ELSE n/a – – communications resource priority for the session initiation protocol, the Priority-Verstat header field extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/8 – – INVITE request

Table A.205: Supported message bodies within the INVITE request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	XML Schema for PSTN	[11B]	n/a	c1	[11B]	n/a	i
2	application/vnd.3gpp.ussd	[8W]	n/a	m	[8W]	n/a	i
3	application/vnd.3gpp.mcptt-info+xml	[8ZE]	n/a	c1	[8ZE]	n/a	i
c1: 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 m ELSE n/a – – I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG).

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.206: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/9 – – INVITE response for all remaining status-codes

Table A.207: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
1A	Call-Info	[26] 20.9	m	m	[26] 20.9	c4	c4
1B	Cellular-Network-Info	7.2.15	n/a	c27	7.2.15	n/a	c28
2	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	c3
3	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	c3
4	Content-Language	[26] 20.13	m	m	[26] 20.13	i	c3
5	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
6	Content-Type	[26] 20.15	m	m	[26] 20.15	i	c3
7	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
8	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
8A	Expires	[26] 20.19	m	m	[26] 20.19	i	i
9	From	[26] 20.20	m	m	[26] 20.20	m	m
9A	Geolocation-Error	[89] 4.3	c24	c24	[89] 4.3	c24	c24
9B	History-Info	[66] 4.1	c17	c17	[66] 4.1	c17	c17
10	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	c3
11	Organization	[26] 20.25	m	m	[26] 20.25	c2	c2
11A	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c14	c14	[52] 4.4, [52A] 4, [234] 2	c15	c15
11B	P-Asserted-Identity	[34] 9.1	c6	c6	[34] 9.1	c7	c7
11C	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c12	c12	[52] 4.5, [52A] 4	c13	c13
11D	P-Charging-Vector	[52] 4.6, [52A] 4	c10	c10	[52] 4.6, [52A] 4	c11	c11
11F	P-Preferred-Identity	[34] 9.2	x	x	[34] 9.2	c5	n/a
11G	Privacy	[33] 4.2	c8	c8	[33] 4.2	c9	c9
11H	Relayed-Charge	7.2.12	n/a	c26	7.2.12	n/a	c26
11I	Reply-To	[26] 20.31	m	m	[26] 20.31	i	i
11J	Require	[26] 20.32	m	m	[26] 20.32	c16	c16
11K	Server	[26] 20.35	m	m	[26] 20.35	i	i
11LA	Service-Interact-Info	Subclause 7.2.14	n/a	c29	Subclause 7.2.14	n/a	c29
11L	Session-ID	[162]	c25	c25	[162]	c25	c25
12	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
13	To	[26] 20.39	m	m	[26] 20.39	m	m
13A	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
13B	User-to-User	[126] 7	c20	c20	[126] 7	c21	c21
14	Via	[26] 20.42	m	m	[26] 20.42	m	m
15	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c3: IF A.3/2 OR A.3/4 THEN m ELSE i – – P-CSCF or S-CSCF. c4: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c5: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c6: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c7: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c8: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c9: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c10: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c11: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c12: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c13: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c14: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c16: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c17: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c18: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c19: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c20: IF A.162/86 THEN m – – transporting user to user information for call centers using SIP. c21: IF A.162/86 THEN i – – transporting user to user information for call centers using SIP. c24: IF A.4/60 THEN m ELSE n/a – – SIP location conveyance. c25: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c26: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c27: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c28: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c29: IF A.162/130 THEN m ELSE n/a – – Dynamic services interactions.

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/101A – – Additional for 18x response

Table A.208: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Contact	[26] 20.10	m	m	[26] 20.10	i	i
4A	Feature-Caps	[190]	c19	c19	[190]	c19	c19
5	P-Answer-State	[111]	c13	c13	[111]	c14	c14
5A	P-Early-Media	[109] 8	o	c11	[109] 8	o	c11
6	P-Media-Authorization	[31] 5.1	c9	x	[31] 5.1	n/a	n/a
6AA	Priority-Share	Subclause 7.2.16	n/a	c21	Subclause 7.2.16	n/a	c21
6A	Reason	[130], [294]	o	c18	[130], [294]	o	c18
7	Record-Route	[26] 20.30	m	m	[26] 20.30	c15	c15
8	Recv-Info	[25] 5.2.3	c16	c16	[25] 5.2.3	c17	c17
8A	Resource-Share	Subclause 4.15	n/a	c20	Subclause 4.15	n/a	c20
9	RSeq	[27] 7.1	m	m	[27] 7.1	i	i
c9: IF A.162/26 THEN m ELSE n/a – – SIP extensions for media authorization. c11: IF A.162/76 THEN m ELSE n/a – – the SIP P-Early-Media private header extension for authorization of early media. c13: IF A.162/75 THEN m ELSE n/a – – the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular. c14: IF A.162/75 THEN i ELSE n/a – – the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular. c15: IF A.162/14 THEN m ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c16: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c17: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c18: IF A.162/48A OR A.162/48C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes). c19: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c20: IF A.162/122 THEN o ELSE n/a – – resource sharing. c21: IF A.162/124 THEN o ELSE n/a – – priority sharing.

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/2 – – Additional for 180 (Ringing) response

Table A.208A: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Alert-Info	[26] 20.4	m	m	[26] 20.4	i	i

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/5A – – Additional for 199 (Early Dialog Terminated) response

Table A.208B: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Contact	[26] 20.10	m	m	[26] 20.10	i	i
5	Reason	[130], [294]	o	c18	[130], [294]	o	c18
7	Record-Route	[26] 20.30	m	m	[26] 20.30	c15	c15
8	Recv-Info	[25] 5.2.3	c16	c16	[25] 5.2.3	c17	c17
9	RSeq	[27] 7.1	m	m	[27] 7.1	i	i
c15: IF A.162/14 THEN m ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c16: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c17: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c18: IF A.162/48A OR A.162/48C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes).

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.209: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
1A	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
1B	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
1C	Accept-Resource-Priority	[116] 3.2	c12	c12	[116] 3.2	c12	c12
2	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
3	Answer-Mode	[158]	c19	c19	[158]	c20	c20
4	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
6	Contact	[26] 20.10	m	m	[26] 20.10	i	i
6A	Feature-Caps	[190]	c22	c22	[190]	c22	c22
7	P-Answer-State	[111]	c13	c13	[111]	c14	c14
7A	P-Visited-Network-ID	[52B] 3	o	o	[52B] 3	o	o
8	P-Media-Authorization	[31] 5.1	c9	x	[31] 5.1	n/a	n/a
8AA	Priority-Share	Subclause 7.2.16	n/a	c24	Subclause 7.2.16	n/a	c24
8A	Priv-Answer-Mode	[158]	c19	c19	[158]	c20	c20
8B	Reason	[294]	o	c25	[294]	o	c25
9	Record-Route	[26] 20.30	m	m	[26] 20.30	c3	c3
9A	Recv-Info	[25] 5.2.3	c17	c17	[25] 5.2.3	c18	c18
9B	Resource-Share	Subclause 4.15	n/a	c23	Subclause 4.15	n/a	c23
10	Session-Expires	[58] 4	c11	c11	[58] 4	c11	c11
13	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c3: IF A.162/14 THEN m ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c9: IF A.162/26 THEN m ELSE n/a – – SIP extensions for media authorization. c11: IF A.162/52 THEN m ELSE n/a – – the SIP session timer. c12: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c13: IF A.162/75 THEN m ELSE n/a – – the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular. c14: IF A.162/75 THEN i ELSE n/a – – the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular. c17: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c18: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c19: IF A.162/97 THEN m ELSE n/a – – requesting answering modes for SIP. c20: IF NOT A.162/97 THEN n/a ELSE IF A.162/97A THEN m ELSE i – – requesting answering modes for SIP, adding, deleting or reading the Answer-Mode header or Priv-Answer-Mode header before proxying the request or response. c22: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c23: IF A.162/122 THEN o ELSE n/a – – resource sharing. c24: IF A.162/124 THEN o ELSE n/a – – priority sharing. c25: IF A.162/48C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes).

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.209A: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Reason	[130], [294]	o	c1	[130], [294]	o	c1
3	Response-Source	7.2.17	n/a	c2	7.2.17	n/a	c2
c1: IF A.162/48A OR A.162/48C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes). c2: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/103 OR A.164/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.210: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Contact	[26] 20.10	m	m	[26] 20.10	c1	c1
c1: IF A.162/19E THEN m ELSE i – – deleting Contact headers.

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/14 – – Additional for 401 (Unauthorized) response

Table A.211: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
6	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
15	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.6/16 – – Additional for 403 (Forbidden) response

Table A.211A: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	P-Refused-URI-List	[183]	c1	c1	[183]	c1	c1
c1: IF A.162/108 THEN m ELSE n/a — The SIP P-Refused-URI-List private-header.

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/50 OR A.164/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 600 (Busy Everywhere), 603 (Decline) response

Table A.212: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
8	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.213: Void

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.214: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
6	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
11	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/21 – – Additional for 408 (Request timeout) response

Table A.214A: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Restoration-Info	subclause 7.2.11	n/a	c1	subclause 7.2.11	n/a	c2
c1: IF A.162/120 THEN o ELSE n/a – – HSS based P-CSCF restoration. c2: IF A.162/120 THEN m ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type) response

Table A.215: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.215A: Supported header field s within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.216: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
10	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.216A: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.16/9 – – INVITE response

Prerequisite: A.164/28A – – Additional for 422 (Session Interval Too Small) response

Table A.216B: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Min-SE	[58] 5	c1	c1	[58] 5	c1	c1
c1: IF A.162/52 THEN m ELSE n/a – – the SIP session timer.

Table A.217: Void

Table A.217A: Void

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/29H – – Additional for 470 (Consent Needed) response

Table A.217AA: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Permission-Missing	[125] 5.9.3	m	m	[125] 5.9.3	m	m

Prerequisite A.163/9 – – INVITE response

Prerequisite: A.164/45 – – 503 (Service Unavailable)

Table A.217B: Supported header fields within the INVITE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
8	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.217C: void

Prerequisite A.163/9 – – INVITE response

Table A.218: Supported message bodies within the INVITE response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	XML Schema for PSTN	[11B]		c1	[11B]		i
2	Recipient List	[183]	c2	c2	[183]	c3	c3
3	3GPP IM CN subsystem XML body	subclause 7.6	n/a	c4	subclause 7.6	n/a	c5
4	application/vnd.3gpp.mcptt-info+xml	[8ZE]	n/a	c1	[8ZE]	n/a	i
c1: 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 m ELSE n/a – – I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). c2 IF A.3/9B THEN m ELSE IF A.3/7A OR A.3/7B OR A.3/7D THEN m ELSE n/a – – IBCF (IMS-ALG), AS acting as terminating UA, AS acting as originating UA, AS performing 3^rd party call control. c3 IF A.3/9B THEN m ELSE IF A.3/7A OR A.3/7B OR A.3/7D THEN i ELSE n/a – – IBCF (IMS-ALG), AS acting as terminating UA, AS acting as originating UA, AS performing 3^rd party call control. c4: IF A.3/2 OR (A.3/9 AND NOT A.3/9B) OR A.3A/88 THEN m ELSE n/a – – P-CSCF, IBCF, IBCF (IMS-ALG), ATCF (proxy). c5: IF A.3/2 OR (A.3/9 AND NOT A.3/9B) OR A.3A/88 THEN i ELSE n/a – – P-CSCF, IBCF, IBCF (IMS-ALG), ATCF (proxy).

A.2.2.4.7A MESSAGE method

Prerequisite A.163/9A – – MESSAGE request

Table A.218A: Supported header fields within the MESSAGE request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Contact	[56B] 9.2	c28	c28	[56B] 9.2	c28	c29
1AA	Additional-Identity	7.2.20	n/a	c79	7.2.20	n/a	c79
1A	Allow	[26] 20.5	m	m	[50] 10	i	i
2	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
2A	Attestation-Info	7.2.18	n/a	c76	7.2.18	n/a	c76
3	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
4	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
5	Call-Info	[26] 20.9	m	m	[26] 20.9	c4	c4
5A	Cellular-Network-Info	7.2.15	n/a	c73	7.2.15	n/a	c74
6	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
7	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
8	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
9	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
10	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
11	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
12	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
13	Expires	[26] 20.19	m	m	[26] 20.19	I	i
13A	Feature-Caps	[190]	c71	c71	[190]	c71	c71
14	From	[26] 20.20	m	m	[26] 20.20	m	m
14A	Geolocation	[89] 4.1	c36	c36	[89] 4.1	c37	c37
14B	History-Info	[66] 4.1	c32	c32	[66] 4.1	c32	c32
14C	Geolocation-Routing	[89] 4.1	c36	c36	[89] 4.1	c37	c37
14D	Identity	[252] 4	c75	c75	[252] 4	c75	c75
15	In-Reply-To	[26] 20.21	m	m	[50] 10	i	i
15A	Max-Breadth	[117] 5.8	c48	c48	[117] 5.8	c49	c49
16	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
17	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
18	Organization	[26] 20.25	m	m	[26] 20.25	c3	c3
18AA	Origination-Id	7.2.19	n/a	c77	7.2.19	n/a	c77
18A	P-Access-Network-Info	[52] 4.4, [234] 2	c23	c23	[52] 4.4, [234] 2	c24	c24
18B	P-Asserted-Identity	[34] 9.1	c10	c10	[34] 9.1	c11	c11
18C	P-Asserted-Service	[121] 4.1	c40	c40	[121] 4.1	c41	c41
18D	P-Called-Party-ID	[52] 4.2	c14	c14	[52] 4.2	c15	c16
18E	P-Charging-Function-Addresses	[52] 4.5	c21	c21	[52] 4.5	c22	c22
18F	P-Charging-Vector	[52] 4.6	c19	c19	[52] 4.6	c20	c20
18H	P-Preferred-Identity	[34] 9.2	x	c69	[34] 9.2	c9	c9
18I	P-Preferred-Service	[121] 4.2	x	x	[121] 4.2	c39	c39
18J	P-Private-Network-Indication	[134]	c44	c44	[134]	c44	c44
18K	P-Profile-Key	[97] 5	c34	c34	[97] 5	c35	c35
18L	P-Served-User	[133] 6	c45	c45	[133] 6	c45	c45
18M	P-User-Database	[82] 4	c33	c33	[82] 4	c33	c33
18N	P-Visited-Network-ID	[52] 4.3	c17	o	[52] 4.3	c18	o
19	Priority	[26] 20.26	m	m	[26] 20.26	i	c50
19A	Privacy	[33] 4.2	c12	c12	[33] 4.2	c13	c13
20	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c8	c8
21	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
21A	Reason	[34A] 2	c26	c26	[34A] 2	c27	c27

22A	Referred-By	[59] 3	c30	c30	[59] 3	c31	c31
23	Reject-Contact	[56B] 9.2	c28	c28	[56B] 9.2	c28	c29
23A	Relayed-Charge	7.2.12	n/a	c72	7.2.12	n/a	c72
23B	Reply-To	[26] 20.31	m	m	[26] 20.31	i	i
23C	Request-Disposition	[56B] 9.1	c28	c28	[56B] 9.1	c28	c28
24	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
24A	Resource-Priority	[116] 3.1	c38	c38	[116] 3.1	c38	c38
25	Route	[26] 20.34	m	m	[26] 20.34	m	m
25A	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c25	c25
25B	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c25	c25
25D	Service-Interact-Info	Subclause 7.2.14	n/a	c78	Subclause 7.2.14	n/a	c78
26	Subject	[26] 20.36	m	m	[26] 20.36	i	i
25C	Session-ID	[162]	c70	c70	[162]	c70	c70
27	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
28	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
29	To	[26] 20.39	m	m	[26] 20.39	m	m
29A	Trigger-Consent	[125] 5.11.2	c42	c42	[125] 5.11.2	c43	c43
30	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
31	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c4: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c8: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c9: IF A.162/30A OR A.162/30C THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c10: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c11: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c12: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c13: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c14: IF A.162/37 THEN m ELSE n/a – – the P-Called-Party-ID header extension. c15: IF A.162/37 THEN i ELSE n/a – – the P-Called-Party-ID header extension. c16: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a – – the P-Called-Party-ID header extension and P-CSCF or (I-CSCF or IBCF (THIG)). c17: IF A.162/38 THEN m ELSE n/a – – the P-Visited-Network-ID header extension. c18: IF A.162/39 THEN m ELSE i – – reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c19: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c20: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c21: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c22: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c23: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c25: IF A.162/47 OR A.162/47A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c26: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c27: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c28: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c29: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a – – caller preferences for the session initiation protocol, and S-CSCF. c30: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c31: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c32: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c33: IF A.162/60 THEN m ELSE n/a – – the P-User-Database private header extension. c34: IF A.162/66A THEN m ELSE n/a – – making the first query to the database in order to populate the P-Profile-Key header. c35: IF A.162/66B THEN m ELSE n/a – – using the information in the P-Profile-Key header. c36: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c37: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c38: IF A.162/80A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c39: IF A.162/84A THEN m ELSE n/a – – act as authentication entity within the trust domain for asserted service.
c40: IF A.162/84 THEN m ELSE n/a – – SIP extension for the identification of services. c41: IF A.162/84 OR A.162/30B THEN m ELSE i – – SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network. c42: IF A.162/85 THEN m ELSE n/a – – a framework for consent-based communications in SIP. c43: IF A.162/85 THEN i ELSE n/a – – a framework for consent-based communications in SIP. c44: IF A.162/87 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header). c45: IF A.162/88 THEN m ELSE n/a – – the SIP P-Served-User private header. c48: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c49: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c50: IF A.162/115 THEN m ELSE i – – PSAP callback indicator. c69: IF A.162/30C THEN m ELSE x – – act as entity passing on identity transparently independent of trust domain. c70: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c71: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c72: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c73: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c74: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c75: IF A.162/126 THEN o ELSE n/a – – authenticated identity management in the Session Initiation Protocol. c76: IF A.162/128 THEN o ELSE n/a – – the Attestation-Info header field extension. c77: IF A.162/129 THEN o ELSE n/a – – the Origination-Id header field extension. c78: IF A.162/130 THEN m ELSE n/a – – Dynamic services interactions. c79: IF A.162/131 THEN o ELSE n/a – – the Additional-Identity header field extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/9A – – MESSAGE request

Table A.218B: Supported message bodies within the MESSAGE request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	permission document	[125] 5.4	c1	c1	[125] 5.4	c2	c2
2	application/vnd.3gpp.sms	[4D]	m	m	[4D]	i	i
2	message/cpim	[151]	c3	c3	[151]	c4	c4
3	message/imdn+xml	[157]	c5	c5	[157]	c6	c6
4	application/vnd.3gpp.mcptt-info+xml	[8ZE]	n/a	c7	[8ZE]	n/a	i
5	application/vnd.3gpp.mcptt-mbms-usage-info+xml	[8ZE]	n/a	c7	[8ZE]	n/a	i
6	application/vnd.3gpp.mcptt-location-info+xml	[8ZE]	n/a	c7	[8ZE]	n/a	i
7	application/vnd.3gpp.mcptt-floor-request+xml	[8ZE]	n/a	c7	[8ZE]	n/a	i
8	application/vnd.3gpp.mcptt-affiliation-command+xml	[8ZE]	n/a	c7	[8ZE]	n/a	i
c1: IF A.162/85 THEN m ELSE n/a – – a framework for consent-based communications in SIP. c2: IF A.162/85 THEN i ELSE n/a – – a framework for consent-based communications in SIP. c3: IF A.162/95 THEN m ELSE n/a – – common presence and instant messaging (CPIM): message format. c4: IF A.162/95 THEN i ELSE n/a – – common presence and instant messaging (CPIM): message format. c5: IF A.162/96 THEN m ELSE n/a – – instant message disposition notification. c6: IF A.162/96 THEN i ELSE n/a – – instant message disposition notification. c7: 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 m ELSE n/a – – I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG).

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.218BA: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/9B – – MESSAGE response for all remaining status-codes

Table A.218C: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Call-Info	[26] 20.9	m	m	[26] 20.9	c3	c3
2A	Cellular-Network-Info	7.2.15	n/a	c23	7.2.15	n/a	c24
3	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
4	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
5	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
6	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
7	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
8	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
9	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
9A	Expires	[26] 20.19	m	m	[26] 20.19	i	i
10	From	[26] 20.20	m	m	[26] 20.20	m	m
10A	Geolocation-Error	[89] 4.3	c17	c17	[89] 4.3	c18	c18
10B	History-Info	[66] 4.1	c16	c16	[66] 4.1	c16	c16
11	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
12	Organization	[26] 20.25	m	m	[26] 20.25	c2	c2
12A	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c13	c13	[52] 4.4, [52A] 4, [234] 2	c14	c14
12B	P-Asserted-Identity	[34] 9.1	c5	c5	[34] 9.1	c6	c6
12C	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c11	c11	[52] 4.5, [52A] 4	c12	c12
12D	P-Charging-Vector	[52] 4.6, [52A] 4	c9	c9	[52] 4.6, [52A] 4	c10	c10
12F	P-Preferred-Identity	[34] 9.2	x	x	[34] 9.2	c4	n/a
12G	Privacy	[33] 4.2	c7	c7	[33] 4.2	c8	c8
12H	Relayed-Charge	7.2.12	n/a	c22	7.2.12	n/a	c22
12I	Reply-To	[26] 20.31	m	m	[26] 20.31	i	i
12J	Require	[26] 20.32	m	m	[26] 20.32	c15	c15
13	Server	[26] 20.35	m	m	[26] 20.35	i	i
13AA	Service-Interact-Info	Subclause 7.2.14	n/a	c25	Subclause 7.2.14	n/a	c25
13A	Session-ID	[162]	c21	c21	[162]	c21	c21
14	Timestamp	[26] 20.38	i	i	[26] 20.38	i	i
15	To	[26] 20.39	m	m	[26] 20.39	m	m
16	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
17	Via	[26] 20.42	m	m	[26] 20.42	m	m
18	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c3: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c4: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c5: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c6: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c7: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c9: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c10: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c11: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c12: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c13: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c16: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c17: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c18: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c21: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c22: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c23: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c25: IF A.162/130 THEN m ELSE n/a – – Dynamic services interactions.

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.218D: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Accept-Resource-Priority	[116] 3.2	c4	c4	[116] 3.2	c4	c4
1	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
2	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
3	Feature-Caps	[190]	c6	c6	[190]	c6	c6
3A	Reason	[294]	o	c7	[294]	o	c7
4	P-Visited-Network-ID	[52B] 3	o	o	[52B] 3	o	o
6	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c4: IF A.162/80A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c6: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c7: IF A.162/48C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes).

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.218DA: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
1A	Reason	[294]	o	c2	[294]	o	c2
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses. c2: IF A.4/38C THEN o ELSE n/a – – use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes).

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/103 OR A.164/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.218E: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Contact	[26] 20.10	m	m	[26] 20.10	c1	c1
c1: IF A.162/19E THEN m ELSE i – – deleting Contact headers.

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/14 – – Additional for 401 (Unauthorized) response

Table A.218F: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
6	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/9B – – MESSAGE response

Table A.218G: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.218H: Void

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.218I: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
6	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Table 218IA: Void

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type)

Table A.218J: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.218JA: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.218K: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
5	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.218L: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.218M: Void

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/29H – – Additional for 470 (Consent Needed) response

Table A.218MA: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Permission-Missing	[125] 5.9.3	m	m	[125] 5.9.3	m	m

Prerequisite A.163/9B – – MESSAGE response

Prerequisite: A.164/46 – – Additional for 504 (Server Time-out) response

Table A.218MB: Supported header fields within the MESSAGE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Restoration-Info	subclause 7.2.11	n/a	c1	subclause 7.2.11	n/a	n/a
c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.163/9B – – MESSAGE response

Table A.218N: Supported message bodies within the MESSAGE response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.8 NOTIFY method

Prerequisite A.163/10 – – NOTIFY request

Table A.219: Supported header fields within the NOTIFY request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
1A	Accept-Contact	[56B] 9.2	c21	c21	[56B] 9.2	c22	c22
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
3A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
4	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
5	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
6	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
6A	Call-Info	[26] 20.9	m	m	[26] 20.9	c28	c28
6B	Cellular-Network-Info	7.2.15	n/a	c43	7.2.15	n/a	c44
6C	Contact	[26] 20.10	m	m	[26] 20.10	i	i
7	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
8	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
9	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
10	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
11	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
12	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
13	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
14	Event	[28] 8.2.1	m	m	[28] 8.2.1	m	m
14A	Feature-Caps	[190]	c41	c41	[190]	c41	c41
15	From	[26] 20.20	m	m	[26] 20.20	m	m
15A	Geolocation	[89] 4.1	c26	c26	[89] 4.1	c27	c27
15B	Geolocation-Routing	[89] 4.1	c26	c26	[89] 4.1	c27	c27
15C	History-Info	[66] 4.1	c25	c25	[66] 4.1	c25	c25
15D	Max-Breadth	[117] 5.8	c29	c29	[117] 5.8	c30	c30
16	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
17	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
17A	P-Access-Network-Info	[52] 4.4, [234] 2	c16	c16	[52] 4.4. [234] 2	c17	c17
17B	P-Asserted-Identity	[34] 9.1	c8	c8	[34] 9.1	c9	c9
17C	P-Charging-Function-Addresses	[52] 4.5	c14	c14	[52] 4.5	c15	c15
17D	P-Charging-Vector	[52] 4.6	c12	c12	[52] 4.6	c13	c13
17F	P-Preferred-Identity	[34] 9.2	x	x	[34] 9.2	c3	n/a

17G	Privacy	[33] 4.2	c10	c10	[33] 4.2	c11	c11
18	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c4	c4
19	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
19A	Reason	[34A] 2	c19	c19	[34A] 2	c20	c20
20	Record-Route	[26] 20.30	m	m	[26] 20.30	c7	c7
20A	Referred-By	[59] 3	c23	c23	[59] 3	c24	c24
20B	Reject-Contact	[56B] 9.2	c21	c21	[56B] 9.2	c22	c22
20C	Relayed-Charge	7.2.12	n/a	c42	7.2.12	n/a	c42
20D	Request-Disposition	[56B] 9.1	c21	c21	[56B] 9.1	c22	c22
21	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
22	Route	[26] 20.34	m	m	[26] 20.34	m	m
22A	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c18	c18
22B	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c18	c18
22C	Session-ID	[162]	c40	c40	[162]	c40	c40
23	Subscription-State	[28] 8.2.3	m	m	[28] 8.2.3	i	i
24	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
24A	Resource-Priority	[116] 3.1	c36	c36	[116] 3.1	c36	c36
25	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
26	To	[26] 20.39	m	m	[26] 20.39	m	m
27	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
28	Via	[26] 20.42	m	m	[26] 20.42	m	m
29	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c4: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN (IF A.162/22 OR A.162/27 THEN m ELSE o) ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog or (the REFER method or SIP specific event notification). c8: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c9: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c10: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c11: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c12: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c13: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c14: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c15: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c16: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c17: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c18: IF A.162/47 OR A.162/47A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c19: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c20: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c21: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c22: IF A.162/50 THEN i ELSE n/a – – caller preferences for the session initiation protocol. c23: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c24: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c25: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c26: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c27: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c28: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c29: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c30: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c36: IF A.162/80A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c40: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c41: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c42: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c43: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c44: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/10 – – NOTIFY request

Table A.220: Supported message bodies within the NOTIFY request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	sipfrag	[37] 2	m	m	[37] 2	i	i
2	event package	[28]	m	m	[28]	i	i

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.220A: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/11 – – NOTIFY response for all remaining status-codes

Table A.221: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
1A	Cellular-Network-Info	7.2.15	n/a	c20	7.2.15	n/a	c21
2	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
3	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
4	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
5	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
6	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
7	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
8	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
9	From	[26] 20.20	m	m	[26] 20.20	m	m
9A	Geolocation-Error	[89] 4.3	c14	c14	[89] 4.3	c15	c15
10	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
10A	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c11	c11	[52] 4.4, [52A] 4, [234] 2	c12	c12
10B	P-Asserted-Identity	[34] 9.1	c3	c3	[34] 9.1	c4	c4
10C	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c9	c9	[52] 4.5, [52A] 4	c10	c10
10D	P-Charging-Vector	[52] 4.6, [52A] 4	c7	c7	[52] 4.6, [52A] 4	c8	c8
10F	P-Preferred-Identity	[34] 9.2	x	x	[34] 9.2	c2	n/a
10G	Privacy	[33] 4.2	c5	c5	[33] 4.2	c6	c6
10H	Relayed-Charge	7.2.12	n/a	c19	7.2.12	n/a	c19
10I	Require	[26] 20.32	m	m	[26] 20.32	c13	c13
10J	Server	[26] 20.35	m	m	[26] 20.35	i	i
10K	Session-ID	[162]	c18	c18	[162]	c18	c18
11	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
12	To	[26] 20.39	m	m	[26] 20.39	m	m
12A	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
13	Via	[26] 20.42	m	m	[26] 20.42	m	m
14	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c3: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c4: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c5: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c6: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c7: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c8: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c9: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c10: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c11: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c12: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c13: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c14: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c15: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c18: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c19: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c20: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c21: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.222: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Accept-Resource-Priority	[116] 3.2	c4	c4	[116] 3.2	c4	c4
0B	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
1	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
1A	Contact	[26] 20.10	m	m	[26] 20.10	i	i
1B	Feature-Caps	[190]	c6	c6	[190]	c6	c6
2	Record-Route	[26] 20.30	m	m	[26] 20.30	c3	c3

5	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c3: IF A.162/15 THEN m ELSE i – – the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/80A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c6: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy.

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.222A: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/103 – – Additional for 3xx response

Table A.223: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Contact	[26] 20.10	m	m	[26] 20.10	c1	c1
c1: IF A.162/19E THEN m ELSE i – – deleting Contact headers.

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/14 – – Additional for 401 (Unauthorized) response

Table A.224: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
8	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/11 – – NOTIFY response

Table A.225: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.226: Void

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.227: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
6	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Table A.227A: Void

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type) response

Table A.228: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.228A: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.229: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
5	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.229A: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.230: Void

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/35 – – Additional for 485 (Ambigious) response

Table A.230A: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Contact	[26] 20.10	m	m	[26] 20.10	i	i

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/39 – – Additional for 489 (Bad Event) response

Table A.231: Supported header fields within the NOTIFY response

Item	Header field	Sending			Receiving
		Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/11 – – NOTIFY response

Prerequisite: A.164/46 – – Additional for 504 (Server Time-out) response

Table A.231A: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Restoration-Info	subclause 7.2.11	n/a	c1	subclause 7.2.11	n/a	n/a
c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.163/11 – – NOTIFY response

Table A.232: Supported message bodies within the NOTIFY response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.9 OPTIONS method

Prerequisite A.163/12 – – OPTIONS request

Table A.233: Supported header fields within the OPTIONS request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
1A	Accept-Contact	[56B] 9.2	c28	c28	[56B] 9.2	c28	c29
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
3A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
4	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
5	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
6	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
7	Call-Info	[26] 20.9	m	m	[26] 20.9	c4	c4
7A	Cellular-Network-Info	7.2.15	n/a	c59	7.2.15	n/a	c60
8	Contact	[26] 20.10	m	m	[26] 20.10	i	i
9	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
10	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
11	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
12	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
13	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
14	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
15	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
15A	Feature-Caps	[190]	c57	c57	[190]	c57	c57
16	From	[26] 20.20	m	m	[26] 20.20	m	m
16A	Geolocation	[89] 4.1	c36	c36	[89] 4.1	c37	c37
16B	Geolocation-Routing	[89] 4.1	c36	c36	[89] 4.1	c37	c37
16C	History-Info	[66] 4.1	c32	c32	[66] 4.1	c32	c32
16D	Max-Breadth	[117] 5.8	c41	c41	[117] 5.8	c42	c42
17	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
18	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
19	Organization	[26] 20.25	m	m	[26] 20.25	c3	c3
19A	P-Access-Network-Info	[52] 4.4, [234] 2	c23	c23	[52] 4.4, [234] 2	c24	c24
19B	P-Asserted-Identity	[34] 9.1	c10	c10	[34] 9.1	c11	c11
19C	P-Asserted-Service	[121] 4.1	c39	c39	[121] 4.1	c40	c40
19D	P-Called-Party-ID	[52] 4.2	c14	c14	[52] 4.2	c15	c16
19E	P-Charging-Function-Addresses	[52] 4.5	c21	c21	[52] 4.5	c22	c22
19F	P-Charging-Vector	[52] 4.6	c19	c19	[52] 4.6	c20	c20
19H	P-Preferred-Identity	[34] 9.2	x	c54	[34] 9.2	c9	c55
19I	P-Preferred-Service	[121] 4.2	x	x	[121] 4.2	c38	c38
19J	P-Private-Network-Indication	[134]	c48	c48	[134]	c48	c48
19K	P-Profile-Key	[97] 5	c34	c34	[97] 5	c35	c35
19L	P-Served-User	[133] 6	c49	c49	[133] 6	c49	c49
19M	P-User-Database	[82] 4	c33	c33	[82] 4	c33	c33
19N	P-Visited-Network-ID	[52] 4.3	c17	o	[52] 4.3	c18	o
19O	Privacy	[33] 4.2	c12	c12	[33] 4.2	c13	c13
20	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c8	c8
21	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
21A	Reason	[34A] 2	c26	c26	[34A] 2	c27	c27
22	Record-Route	[26] 20.30	m	m	[26] 20.30	c7	c7
22A	Recv-Info	[25] 5.2.3	c52	c52	[25] 5.2.3	c53	c53
22B	Referred-By	[59] 3	c30	c30	[59] 3	c31	c31
22C	Reject-Contact	[56B] 9.2	c28	c28	[56B] 9.2	c28	c29
22D	Relayed-Charge	7.2.12	n/a	c58	7.2.12	n/a	c58
22E	Request-Disposition	[56B] 9.1	c28	c28	[56B] 9.1	c28	c28
23	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
23A	Resource-Priority	[116] 3.1	c47	c47	[116] 3.1	c47	c47
24	Route	[26] 20.34	m	m	[26] 20.34	m	m
24A	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c25	c25
24B	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c25	c25
24C	Session-ID	[162]	c56	c56	[162]	c56	c56
25	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
26	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
27	To	[26] 20.39	m	m	[26] 20.39	m	m
28	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
29	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c4: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c9: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c10: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c11: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c12: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c13: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c14: IF A.162/37 THEN m ELSE n/a – – the P-Called-Party-ID header extension. c15: IF A.162/37 THEN i ELSE n/a – – the P-Called-Party-ID header extension. c16: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a – – the P-Called-Party-ID header extension and P-CSCF or (I-CSCF or IBCF (THIG)). c17: IF A.162/38 THEN m ELSE n/a – – the P-Visited-Network-ID header extension. c18: IF A.162/39 THEN m ELSE i – – reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c19: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c20: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c21: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c22: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c23: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c25: IF A.162/47 OR A.162/47A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c26: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c27: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c28: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c29: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a – – caller preferences for the session initiation protocol, and S-CSCF. c30: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c31: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c32: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c33: IF A.162/60 THEN m ELSE n/a – – the P-User-Database private header extension. c34: IF A.162/66A THEN m ELSE n/a – – making the first query to the database in order to populate the P-Profile-Key header. c35: IF A.162/66B THEN m ELSE n/a – – using the information in the P-Profile-Key header. c36: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c37: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c38: IF A.162/84A THEN m ELSE n/a – – act as authentication entity within the trust domain for asserted service. c39: IF A.162/84 THEN m ELSE n/a – – SIP extension for the identification of services. c40: IF A.162/84 OR A.162/30B THEN m ELSE i – – SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network. c41: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies.
c42: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c47: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c48: IF A.162/87 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header). c49: IF A.162/88 THEN m ELSE n/a – – the SIP P-Served-User private header. c52: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c53: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c54: IF A.162/30C THEN m ELSE x – – act as entity passing on identity transparently independent of trust domain. c55: IF A.162/30A OR A.162/30C THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c56: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c57: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c58: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c59: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c60: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/12 – – OPTIONS request

Table A.234: Supported message bodies within the OPTIONS request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

Table A.235: Void

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.235A: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/13 – – OPTIONS response for all remaining status-codes

Table A.236: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
1A	Call-Info	[26] 20.9	m	m	[26] 20.9	c3	c3
1B	Cellular-Network-Info	7.2.15	n/a	c25	7.2.15	n/a	c26
2	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
3	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
4	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
5	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
6	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
7	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
8	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
9	From	[26] 20.20	m	m	[26] 20.20	m	m
9A	Geolocation-Error	[89] 4.3	c17	c17	[89] 4.3	c18	c18
9B	History-Info	[66] 4.1	c16	c16	[66] 4.1	c16	c16
10	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
11	Organization	[26] 20.25	m	m	[26] 20.25	c2	c2
11A	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c13	c13	[52] 4.4, [52A] 4, [234] 2	c14	c14
11B	P-Asserted-Identity	[34] 9.1	c5	c5	[34] 9.1	c6	c6
11C	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c11	c11	[52] 4.5, [52A] 4	c12	c12
11D	P-Charging-Vector	[52] 4.6, [52A] 4	c9	c9	[52] 4.6, [52A] 4	c10	c10
11F	P-Preferred-Identity	[34] 9.2	x	x	[34] 9.2	c4	n/a
11G	Privacy	[33] 4.2	c7	c7	[33] 4.2	c8	c8
11H	Recv-Info	[25] 5.2.3	c21	c21	[25] 5.2.3	c22	c22
11I	Relayed-Charge	7.2.12	n/a	c24	7.2.12	n/a	c24
11J	Require	[26] 20.32	m	m	[26] 20.32	c15	c15
11K	Server	[26] 20.35	m	m	[26] 20.35	i	i
11K	Session-ID	[162]	c23	c23	[162]	c23	c23
12	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
13	To	[26] 20.39	m	m	[26] 20.39	m	m
13A	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
14	Via	[26] 20.42	m	m	[26] 20.42	m	m
15	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c3: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c4: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c5: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c6: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c7: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c9: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c10: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c11: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c12: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c13: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c16: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c17: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c18: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c21: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c22: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c23: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c24: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c25: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c26: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.237: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
1A	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
1B	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
1C	Accept-Resource-Priority	[116] 3.2	c12	c12	[116] 3.2	c12	c12
2	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
3	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
5	Contact	[26] 20.10	m	m	[26] 20.10	i	i
6	Feature-Caps	[190]	c14	c14	[190]	c14	c14
7	Recv-Info	[25] 5.2.3	c7	c7	[25] 5.2.3	c8	c8
9	Record-Route	[26] 20.30	m	m	[26] 20.30	c3	c3

12	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c3: IF A.162/15 THEN o ELSE i – – the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c7: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c8: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c12: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c14: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy.

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.237A: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/103 OR A.164/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.238: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Contact	[26] 20.10	m	m	[26] 20.10	c1	c1
c1: IF A.162/19E THEN m ELSE i – – deleting Contact headers.

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/14 – – Additional for 401 (Unauthorized) response

Table A.239: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
10	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/13 – – OPTIONS response

Table A.240: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
5	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.241: Void

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.242: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
8	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Table A.242A: Void

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type) response

Table A.243: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.243A: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.244: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
7	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.244A: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.245: Void

Prerequisite A.163/13 – – OPTIONS response

Prerequisite: A.164/46 – – Additional for 504 (Server Time-out) response

Table A.245A: Supported header fields within the OPTIONS response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Restoration-Info	subclause 7.2.11	n/a	c1	subclause 7.2.11	n/a	n/a
c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.163/13 – – OPTIONS response

Table A.246: Supported message bodies within the OPTIONS response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.10 PRACK method

Prerequisite A.163/14 – – PRACK request

Table A.247: Supported header fields within the PRACK request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
1A	Accept-Contact	[56B] 9.2	c18	c18	[56B] 9.2	c19	c19
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
3A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
4	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
5	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
6	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
6A	Cellular-Network-Info	7.2.15	n/a	c51	7.2.15	n/a	c52
7	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	c3
8	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	c3
9	Content-Language	[26] 20.13	m	m	[26] 20.13	i	c3
10	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
11	Content-Type	[26] 20.15	m	m	[26] 20.15	i	c3
12	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
13	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
14	From	[26] 20.20	m	m	[26] 20.20	m	m
14A	Max-Breadth	[117] 5.8	c26	c26	[117] 5.8	c27	c27
15	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
16	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	c3
16A	P-Access-Network-Info	[52] 4.4, [234] 2	c14	c14	[52] 4.4, [234] 2	c15	c15
16B	P-Charging-Function-Addresses	[52] 4.5	c12	c12	[52] 4.5	c13	c13
16C	P-Charging-Vector	[52] 4.6	c10	c10	[52] 4.6	c11	c11
16E	P-Early-Media	[109] 8	o	c22	[109] 8	o	c22
16EA	Priority-Share	Subclause 7.2.16	n/a	c53	Subclause 7.2.16	n/a	c53
16F	Privacy	[33] 4.2	c8	c8	[33] 4.2	c9	c9
17	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c4	c4
18	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
19	RAck	[27] 7.2	m	m	[27] 7.2	i	i
19A	Reason	[34A] 2	c16	c16	[34A] 2	c17	c17
20	Record-Route	[26] 20.30	m	m	[26] 20.30	c7	c7
20A	Recv-Info	[25] 5.2.3	c28	c28	[25] 5.2.3	c29	c29
20B	Referred-By	[59] 3	c20	c20	[59] 3	c21	c21
20C	Reject-Contact	[56B] 9.2	c18	c18	[56B] 9.2	c19	c19
20D	Relayed-Charge	7.2.12	n/a	c49	7.2.12	n/a	c49
20E	Request-Disposition	[56B] 9.1	c18	c18	[56B] 9.1	c19	c19
21	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
21A	Resource-Priority	[16] 3.1	c47	c47	[116] 3.1	c47	c47
21B	Resource-Share	Subclause 4.15	n/a	c50	Subclause 4.15	n/a	c50
22	Route	[26] 20.34	m	m	[26] 20.34	m	m
22A	Session-ID	[162]	c48	c48	[162]	c48	c48
23	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
24	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
25	To	[26] 20.39	m	m	[26] 20.39	m	m
26	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
27	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.3/2 OR A.3/4 THEN m ELSE i – – P-CSCF or S-CSCF. c4: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c9: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c10: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c11: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c12: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c13: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c14: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c16: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c17: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c18: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c19: IF A.162/50 THEN i ELSE n/a – – caller preferences for the session initiation protocol. c20: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c21: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c22: IF A.162/76 THEN m ELSE n/a – – the SIP P-Early-Media private header extension for authorization of early media. c26: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c27: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c28: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c29: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c47: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c48: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c49: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c50: IF A.4/112 THEN o ELSE n/a – – resource sharing. c51: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c52: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c53: IF A.162/124 THEN o ELSE n/a – – priority sharing.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/14 – – PRACK request

Table A.248: Supported message bodies within the PRACK request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

Table A.249: Void

Prerequisite A.163/15 – – PRACK response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.249A: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/15 – – PRACK response for all remaining status-codes

Table A.250: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
1A	Cellular-Network-Info	7.2.15	n/a	c18	7.2.15	n/a	c19
2	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	c2
3	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	c2
4	Content-Language	[26] 20.13	m	m	[26] 20.13	i	c2
5	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
6	Content-Type	[26] 20.15	m	m	[26] 20.15	i	c2
7	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
8	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
9	From	[26] 20.20	m	m	[26] 20.20	m	m
10	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	c2
10A	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c9	c9	[52] 4.4, [52A] 4, [234] 2	c10	c10
10B	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c7	c7	[52] 4.5, [52A] 4	c8	c8
10C	P-Charging-Vector	[52] 4.6, [52A] 4	c5	c5	[52] 4.6, [52A] 4	c6	c6
10F	Privacy	[33] 4.2	c3	c3	[33] 4.2	c4	c4
10G	Recv-Info	[25] 5.2.3	c14	c14	[25] 5.2.3	c15	c15
10H	Relayed-Charge	7.2.12	n/a	c17	7.2.12	n/a	c17
10I	Require	[26] 20.32	m	m	[26] 20.32	c11	c11
10J	Server	[26] 20.35	m	m	[26] 20.35	i	i
10K	Session-ID	[162]	c16	c16	[162]	c16	c16
11	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
12	To	[26] 20.39	m	m	[26] 20.39	m	m
12A	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
13	Via	[26] 20.42	m	m	[26] 20.42	m	m
14	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.3/2 OR A.3/4 THEN m ELSE i – – P-CSCF or S-CSCF. c3: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c4: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c5: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c6: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c7: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c8: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c9: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c10: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c11: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c14: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c15: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c16: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c17: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c18: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c19: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.

Prerequisite A.163/15 – – PRACK response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.251: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
0B	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
0C	Accept-Resource-Priority	[116] 3.2	c12	c12	[116] 3.2	c12	c12
0D	P-Early-Media	[109] 8	o	c4	[109] 8	o	c4
0E	Priority-Share	Subclause 7.2.16	n/a	c14	Subclause 7.2.16	n/a	c14
1	Record-Route	[26] 20.30	m	m	[26] 20.30	c3	c3
2	Recv-Info	[25] 5.2.3	c6	c6	[25] 5.2.3	c7	c7
2A	Resource-Share	Subclause 4.15	n/a	c13	Subclause 4.15	n/a	c13
3	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c3: IF A.162/15 THEN o ELSE i – – the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/76 THEN m ELSE n/a – – the SIP P-Early-Media private header extension for authorization of early media. c6: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c7: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c12: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c13: IF A.4/112 THEN o ELSE n/a – – resource sharing. c14: IF A.162/124 THEN o ELSE n/a – – priority sharing.

Prerequisite A.163/3 – – PRACK response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.251A: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.163/15 – – PRACK response

Prerequisite: A.164/103 OR A.164/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.252: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Contact	[26] 20.10	m	m	[26] 20.10	c1	c1
c1: IF A.162/19E THEN m ELSE i – – deleting Contact headers.

Prerequisite A.163/15 – – PRACK response

Prerequisite: A.164/14 – – Additional for 401 (Unauthorized) response

Table A.253: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
8	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/15 – – PRACK response

Table A.254: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.255: Void

Prerequisite A.163/15 – – PRACK response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.256: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
6	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/15 – – PRACK response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type) response

Table A.257: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/15 – – PRACK response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.257A: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

Prerequisite A.163/15 – – PRACK response

Prerequisite: A.164/27 – – Addition for 420 (Bad Extension) response

Table A.258: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
5	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/15 – – PRACK response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.258A: Supported header fields within the PRACK response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.259: Void

Prerequisite A.163/15 – – PRACK response

Table A.260: Supported message bodies within the PRACK response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.10A PUBLISH method

Prerequisite A.163/15A – – PUBLISH request

Table A.260A: Supported header fields within the PUBLISH request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Contact	[56B] 9.2	c28	c28	[56B] 9.2	c28	c29
2	Allow	[26] 20.5	m	m	[26] 20.5	i	i
3	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c29	c29
4	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
5	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
6	Call-Info	[26] 24.9	m	m	[26] 24.9	c4	c4
6A	Cellular-Network-Info	7.2.15	n/a	c72	7.2.15	n/a	c73
6B	Contact	[70] 4	o	o	[70] 6	n/a	n/a
7	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
8	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
9	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
10	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
11	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
12	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
13	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
14	Event	[70] 4, 6	m	m	[70] 4, 6	m	m
15	Expires	[26] 20.19, [70] 4, 5, 6	m	m	[26] 20.19, [70] 4, 5, 6	i	i
15A	Feature-Caps	[190]	c70	c70	[190]	c70	c70
16	From	[26] 20.20	m	m	[26] 20.20	m	m
16A	Geolocation	[89] 4.1	c46	c46	[89] 4.1	c47	c47
16B	Geolocation-Routing	[89] 4.1	c46	c46	[89] 4.1	c47	c47
16C	History-Info	[66] 4.1	c32	c32	[66] 4.1	c32	c32
17	In-Reply-To	[26] 20.21	m	m	[26] 20.21	i	i
17A	Max-Breadth	[117] 5.8	c44	c44	[117] 5.8	c45	c45
18	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
19	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
20	Organization	[26] 20.25	m	m	[26] 20.25	c3	c3
21	P-Access-Network-Info	[52] 4.4, [234] 2	c23	c23	[52] 4.4, [234] 2	c24	c24
22	P-Asserted-Identity	[34] 9.1	c10	c10	[34] 9.1	c11	c11
22A	P-Asserted-Service	[121] 4.1	c38	c38	[121] 4.1	c39	c39
23	P-Called-Party-ID	[52] 4.2	c14	c14	[52] 4.2	c15	c16
24	P-Charging-Function-Addresses	[52] 4.5	c21	c21	[52] 4.5	c22	c22
25	P-Charging-Vector	[52] 4.6	c19	c19	[52] 4.6	c20	c20
26	P-Preferred-Identity	[34] 9.2	x	c69	[34] 9.2	c9	c9
26A	P-Preferred-Service	[121] 4.2	x	x	[121] 4.2	c37	c37
26B	P-Private-Network-Indication	[134]	c40	c40	[134]	c40	c40
26C	P-Profile-Key	[97] 5	c34	c34	[97] 5	c35	c35
26D	P-Served-User	[133] 6	c41	c41	[133] 6	c41	c41
26E	P-User-Database	[82] 4	c33	c33	[82] 4	c33	c33
27	P-Visited-Network-ID	[52] 4.3	c17	o	[52] 4.3	c18	o
28	Priority	[26] 20.26	m	m	[26] 20.26	i	c50
29	Privacy	[33] 4.2	c12	c12	[33] 4.2	c13	c13
30	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c7	c7
31	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
32	Reason	[34A] 2	c8	c8	[34A] 2	c1	c1
33	Referred-By	[59] 3	c30	c30	[59] 3	c31	c31
34	Reject-Contact	[56B] 9.2	c27	c27	[56B] 9.2	c27	c28
34A	Relayed-Charge	7.2.12	n/a	c71	7.2.12	n/a	c71
34B	Reply-To	[26] 20.31	m	m	[26] 20.31	i	i
35	Request-Disposition	[56B] 9.1	c27	c27	[56B] 9.1	c27	c27
36	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
36A	Resource-Priority	[116] 3.1	c36	c36	[116] 3.1	c36	c36
37	Route	[26] 20.34	m	m	[26] 20.34	m	m
38	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c25	c25
39	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c25	c25
39A	Session-ID	[162]	c48	c48	[162]	c48	c48
40	SIP-If-Match	[70] 11.3.2	m	m	[70] 11.3.2	i	i
41	Subject	[26] 20.36	m	m	[26] 20.36	i	i
42	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
43	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
44	To	[26] 20.39	m	m	[26] 20.39	m	m
45	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
46	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c4: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c7: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c8: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c9: IF A.162/30A OR A.162/30C THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c10: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c11: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c12: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c13: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c14: IF A.162/37 THEN m ELSE n/a – – the P-Called-Party-ID header extension. c15: IF A.162/37 THEN i ELSE n/a – – the P-Called-Party-ID header extension. c16: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a – – the P-Called-Party-ID header extension and P-CSCF or (I-CSCF or IBCF (THIG). c17: IF A.162/38 THEN m ELSE n/a – – the P-Visited-Network-ID header extension. c18: IF A.162/39 THEN m ELSE i – – reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c19: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c20: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c21: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c22: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c23: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c25: IF A.162/47 OR A.162/47A THEN o ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 1). c27: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c28: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a – – caller preferences for the session initiation protocol, and S-CSCF. c29: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension (note 2). c30: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c31: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c32: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c33: IF A.162/60 THEN m ELSE n/a – – the P-User-Database private header extension. c34: IF A.162/66A THEN m ELSE n/a – – making the first query to the database in order to populate the P-Profile-Key header. c35: IF A.162/66B THEN m ELSE n/a – – using the information in the P-Profile-Key header. c36: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c37: IF A.162/84A THEN m ELSE n/a – – act as authentication entity within the trust domain for asserted service. c38: IF A.162/84 THEN m ELSE n/a – – SIP extension for the identification of services. c39: IF A.162/84 OR A.162/30B THEN m ELSE i – – SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network. c40: IF A.162/87 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header). c41: IF A.162/88 THEN m ELSE n/a – – the SIP P-Served-User private header.
c44: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c45: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c46: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c47: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c48: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c69: IF A.162/30C THEN m ELSE x – – act as entity passing on identity transparently independent of trust domain. c50: IF A.162/115 THEN m ELSE i – – PSAP callback indicator. c70: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c71: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c72: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c73: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.
NOTE 1: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. NOTE 2: c29 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/15A – – PUBLISH request

Table A.260B: Supported message bodies within the PUBLISH request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	application/vnd.3gpp.mcptt-info+xml	[8ZE]	n/a	c1	[8ZE]	n/a	c1
2	application/poc-settings+xml	[110]	o	c1	[110]	o	c1
3	application/pidf+xml	[242]	o	c1	[242]	o	c1
c1: 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 m ELSE n/a – – I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG).

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.260BA: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/15B – – PUBLISH response for all remaining status-codes

Table A.260C: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Call-Info	[26] 24.9	m	m	[26] 24.9	c3	c3
2A	Cellular-Network-Info	7.2.15	n/a	c23	7.2.15	n/a	c24
3	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
4	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
5	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
6	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
7	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
8	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
9	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
9A	Expires	[26] 20.19 [70] 4, 5, 6	m	m	[26] 20.19 [70] 4, 5, 6	i	i
10	From	[26] 20.20	m	m	[26] 20.20	m	m
10A	Geolocation-Error	[89] 4.3	c19	c19	[89] 4.3	c20	c20
10B	History-Info	[66] 4.1	c16	c16	[66] 4.1	c16	c16
11	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
12	Organization	[26] 20.25	m	m	[26] 20.25	c2	c2
13	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c13	c13	[52] 4.4, [52A] 4, [234] 2	c14	c14
14	P-Asserted-Identity	[34] 9.1	c5	c5	[34] 9.1	c6	c6
15	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c11	c11	[52] 4.5, [52A] 4	c12	c12
16	P-Charging-Vector	[52] 4.6, [52A] 4	c9	c9	[52] 4.6, [52A] 4	c10	c10
17	P-Preferred-Identity	[34] 9.2	x	x	[34] 9.2	c4	n/a
18	Privacy	[33] 4.2	c7	c7	[33] 4.2	c8	c8
18A	Relayed-Charge	7.2.12	n/a	c22	7.2.12	n/a	c22
19	Require	[26] 20.32	m	m	[26] 20.32	c15	c15
20	Server	[26] 20.35	m	m	[26] 20.35	i	i
20A	Session-ID	[162]	c21	c21	[162]	c21	c21
21	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
22	To	[26] 20.39	m	m	[26] 20.39	m	m
23	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
24	Via	[26] 20.42	m	m	[26] 20.42	m	m
25	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c3: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c4: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c5: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c6: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c7: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c9: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c10: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c11: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c12: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c13: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c16: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c19: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c20: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c21: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c22: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c23: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.260D: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status


2	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
3	Expires	[26] 20.19, [70] 4, 5, 6	m	m	[26] 20.19, [70] 4, 5, 6	i	i
3A	Feature-Caps	[190]	c6	c6	[190]	c6	c6

4	SIP-Etag	[70] 11.3.1	m	m	[70] 11.3.1	i	i
5	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c6: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy.

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/6 – – Additional for 200 (OK) response

Table A.260DAA: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.260DA: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/103 OR A.164/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.260E: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Contact	[26] 20.10	m	m	[26] 20.10	c1	c1
c1: IF A.162/19E THEN m ELSE i – – deleting Contact headers.

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/8 OR A.164/9 OR A.164/10 OR A.164/11 OR A.164/12 – – Additional for 401 (Unauthorized) response

Table A.260F: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
5	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/15B – – PUBLISH response

Table A.260G: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.260H: Void

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.260I: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
5	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Table A.260IA: Void

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type) response

Table A.260J: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.260JA: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.260K: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.260L: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/29 – – Additional for 423 (Interval Too Brief) response

Table A.260M: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Min-Expires	[26] 20.23, [70] 5, 6	m	m	[26] 20.23, [70] 5, 6	i	i

Table A.260N: Void

Prerequisite A.163/15B – – PUBLISH response

Prerequisite: A.164/39 – – Additional for 489 (Bad Event) response

Table A.260O: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	i	i

Prerequisite A.163/17 – – PUBLISH response

Prerequisite: A.164/46 – – Additional for 504 (Server Time-out) response

Table A.260OA: Supported header fields within the PUBLISH response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Restoration-Info	subclause 7.2.11	n/a	c1	subclause 7.2.11	n/a	n/a
c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.163/17 – – PUBLISH response

Table A.260P: Supported message bodies within the PUBLISH response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.11 REFER method

Prerequisite A.163/16 – – REFER request

Table A.261: Supported header fields within the REFER request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Accept	[26] 20.1	m	m	[26] 20.1	i	i
0B	Accept-Contact	[56B] 9.2	c27	c27	[56B] 9.2	c27	c28
0C	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
1	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
1AA	Additional-Identity	7.2.20	n/a	c77	7.2.20	n/a	c77
1A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
2	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
3	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
4	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
4A	Cellular-Network-Info	7.2.15	n/a	c75	7.2.15	n/a	c76
5	Contact	[26] 20.10	m	m	[26] 20.10	i	i
5A	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
5B	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
5C	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
6	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
7	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
8	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
9	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
10	Expires	[26] 20.19	m	m	[26] 20.19	i	i
10A	Feature-Caps	[190]	cj	cj	[190]	cj	cj
11	From	[26] 20.20	m	m	[26] 20.20	m	m
11A	Geolocation	[89] 4.1	c35	c35	[89] 4.1	c36	c36
11B	Geolocation-Routing	[89] 4.1	c35	c35	[89] 4.1	c36	c36
11C	History-Info	[66] 4.1	c31	c31	[66] 4.1	c31	c31
11D	Max-Breadth	[117] 5.8	c40	c40	[117] 5.8	c41	c41
12	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
13	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
14	Organization	[26] 20.25	m	m	[26] 20.25	c3	c3
14A	P-Access-Network-Info	[52] 4.4, [234] 2	c22	c22	[52] 4.4, [234] 2	c23	c23
14B	P-Asserted-Identity	[34] 9.1	c9	c9	[34] 9.1	c10	c10
14C	P-Asserted-Service	[121] 4.1	c38	c38	[121] 4.1	c39	c39
14D	P-Called-Party-ID	[52] 4.2, [52A] 4	c13	c13	[52] 4.2, [52A] 4	c14	c15
14E	P-Charging-Function-Addresses	[52] 4.5	c20	c20	[52] 4.5	c21	c21
14F	P-Charging-Vector	[52] 4.6	c18	c18	[52] 4.6	c19	c19
14H	P-Preferred-Identity	[34] 9.2	x	c69	[34] 9.2	c8	c8
14I	P-Preferred-Service	[121] 4.2	x	x	[121] 4.2	c37	c37
14J	P-Private-Network-Indication	[134]	c50	c50	[134]	c50	c50
14K	P-Profile-Key	[97] 5	c33	c33	[97] 5	c34	c34
14L	P-Served-User	[133] 6	c53	c53	[133] 6	c53	c53
14M	P-User-Database	[82] 4	c32	c32	[82] 4	c32	c32
14N	P-Visited-Network-ID	[52] 4.3	c16	o	[52] 4.3	c17	o
14O	Privacy	[33] 4.2	c11	c11	[33] 4.2	c12	c12
15	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c4	c4
16	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
16A	Reason	[34A] 2	c25	c25	[34A] 2	c26	c26
17	Record-Route	[26] 20.30	m	m	[26] 20.30	c7	c7
17A	Refer-Sub	[173] 4	c54	c54	[173] 4	c55	c55
18	Refer-To	[36] 3	c3	c3	[36] 3	c4	c4
18A	Referred-By	[59] 3	c29	c29	[59] 3	c30	c30
18B	Reject-Contact	[56B] 9.2	c27	c27	[56B] 9.2	c27	c28
18C	Relayed-Charge	7.2.12	n/a	c74	7.2.12	n/a	c74
18D	Request-Disposition	[56B] 9.1	c27	c27	[56B] 9.1	c27	c27
19	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
19A	Resource-Priority	[116] 3.1	c47	c47	[116] 3.1	c47	c47
20	Route	[26] 20.34	m	m	[26] 20.34	m	m
20A	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c24	c24
20B	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c24	c24
20C	Session-ID	[162]	c70	c70	[162]	c70	c70
21	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
21A	Target-Dialog	[184] 7	c71	c71	[184] 7	c72	c72
22	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
23	To	[26] 20.39	m	m	[26] 20.39	m	m
23A	Trigger-Consent	[125] 5.11.2	c48	c48	[125] 5.11.2	c49	c49
24	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
25	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c4: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN m ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/30A OR A.162/30C THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c9: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c10: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c11: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c12: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c13: IF A.162/37 THEN m ELSE n/a – – the P-Called-Party-ID header extension. c14: IF A.162/37 THEN i ELSE n/a – – the P-Called-Party-ID header extension. c15: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a – – the P-Called-Party-ID header extension and P-CSCF or (I-CSCF or IBCF (THIG). c16: IF A.162/38 THEN m ELSE n/a – – the P-Visited-Network-ID header extension. c17: IF A.162/39 THEN m ELSE i – – reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c18: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c19: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c20: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c21: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c22: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c23: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/47 OR A.162/47A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c25: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c26: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c27: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c28: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a – – caller preferences for the session initiation protocol, and S-CSCF. c29: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c30: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c31: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c32: IF A.162/60 THEN m ELSE n/a – – the P-User-Database private header extension. c33: IF A.162/66A THEN m ELSE n/a – – making the first query to the database in order to populate the P-Profile-Key header. c34: IF A.162/66B THEN m ELSE n/a – – using the information in the P-Profile-Key header. c35: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c36: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c37: IF A.162/84A THEN m ELSE n/a – – act as authentication entity within the trust domain for asserted service. c38: IF A.162/84 THEN m ELSE n/a – – SIP extension for the identification of services. c39: IF A.162/84 OR A.162/30B THEN m ELSE i – – SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network.
c40: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c41: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c47: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c48: IF A.162/85 THEN m ELSE n/a – – a framework for consent-based communications in SIP. c49: IF A.162/85 THEN i ELSE n/a – – a framework for consent-based communications in SIP. c50: IF A.162/87 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header). c53: IF A.162/88 THEN m ELSE n/a – – the SIP P-Served-User private header. c54: IF A.162/105 THEN m ELSE n/a – – suppression of session initiation protocol REFER method implicit subscription. c55: IF A.162/105 THEN i ELSE n/a – – suppression of session initiation protocol REFER method implicit subscription. c69: IF A.162/30C THEN m ELSE x – – act as entity passing on identity transparently independent of trust domain. c70: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c71: IF A.162/109 THEN m ELSE n/a – – request authorization through dialog Identification in the session initiation protocol. c72: IF A.162/109 THEN i ELSE n/a – – request authorization through dialog Identification in the session initiation protocol. c73: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c74: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c75: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c76: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c77: IF A.162/131 THEN o ELSE n/a – – the Additional-Identity header field extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/16 – – REFER request

Table A.262: Supported message bodies within the REFER request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	application/vnd.3gpp.mid-call+xml	[8M] D	n/a	i	[8M] D	n/a	i
2	application/vnd.3gpp.mcptt-info+xml	[8ZE]	n/a	c1	[8ZE]	n/a	i
c1: 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 m ELSE n/a – – I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG).

Table A.263: Void

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.263A: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/17 – – REFER response for all remaining status-codes

Table A.264: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
1A	Cellular-Network-Info	7.2.15	n/a	c22	7.2.15	n/a	c23
1B	Contact	[26] 20.10	m	m	[26] 20.10	i	i
1C	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
2	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
3	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
4	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
5	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
6	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
7	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
8	From	[26] 20.20	m	m	[26] 20.20	m	m
8A	Geolocation-Error	[89] 4.3	c16	c16	[89] 4.3	c17	c17
8B	History-Info	[66] 4.1	c15	c15	[66] 4.1	c15	c15
9	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
10	Organization	[26] 20.25	m	m	[26] 20.25	c2	c2
10A	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c12	c12	[52] 4.4, [52A] 4, [234] 2	c13	c13
10B	P-Asserted-Identity	[34] 9.1	c4	c4	[34] 9.1	c5	c5
10C	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c10	c10	[52] 4.5, [52A] 4	c11	c11
10D	P-Charging-Vector	[52] 4.6, [52A] 4	c8	c8	[52] 4.6, [52A] 4	c9	c9
10F	P-Preferred-Identity	[34] 9.2	x	x	[34] 9.2	c3	n/a
10G	Privacy	[33] 4.2	c6	c6	[33] 4.2	c7	c7
10H	Relayed-Charge	7.2.12	n/a	c21	7.2.12	n/a	c21
10I	Require	[26] 20.32	m	m	[26] 20.32	c14	c14
10J	Server	[26] 20.35	m	m	[26] 20.35	i	i
10K	Session-ID	[162]	c20	c20	[162]	c20	c20
11	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
12	To	[26] 20.39	m	m	[26] 20.39	m	m
12A	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
13	Via	[26] 20.42	m	m	[26] 20.42	m	m
14	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c3: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c4: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c5: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c6: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c8: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c9: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c10: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c11: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c12: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c13: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c15: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c16: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c17: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c20: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c21: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c22: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c23: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.265: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Accept-Resource-Priority	[116] 3.2	c12	c12	[116] 3.2	c12	c12
1	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
2	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
3	Feature-Caps	[190]	c14	c14	[190]	c14	c14
5	Record-Route	[26] 20.30	m	m	[26] 20.30	c3	c3
6	Refer-Sub	[173] 4	c4	c4	[173] 4	c5	c5

8	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c3: IF A.162/15 THEN m ELSE i – – the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/105 THEN m ELSE n/a – – suppression of session initiation protocol REFER method implicit subscription. c5: IF A.162/105 THEN I ELSE n/a – – suppression of session initiation protocol REFER method implicit subscription. c12: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c14: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy.

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.265A: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Table A.266: Void

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/8 OR A.164/9 OR A.164/10 OR A.164/11 OR A.164/12 – – Additional for 401 (Unauthorized) response

Table A.267: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
10	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/17 – – REFER response

Table A.268: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
6	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.269: Void

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.270: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
8	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Table A.270A: Void

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type) response

Table A.271: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.271A: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.272: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
8	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.272A: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Table A.273: Void

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/29H – – Additional for 470 (Consent Needed) response

Table A.273A: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Permission-Missing	[125] 5.9.3	m	m	[125] 5.9.3	m	m

Prerequisite A.163/17 – – REFER response

Prerequisite: A.164/46 – – Additional for 504 (Server Time-out) response

Table A.273AA: Supported header fields within the REFER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Restoration-Info	subclause 7.2.11	n/a	c1	subclause 7.2.11	n/a	n/a
c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.163/17 – – REFER response

Table A.274: Supported message bodies within the REFER response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.12 REGISTER method

Prerequisite A.163/18 – – REGISTER request

Table A.275: Supported header fields within the REGISTER request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
3A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
4	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
5	Authorization	[26] 20.7, [49]	m	m	[26] 20.7, [49]	i	i
6	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
7	Call-Info	[26] 20.9	m	m	[26] 20.9	c2	c2
7A	Cellular-Network-Info	7.2.15	n/a	c39	7.2.15	n/a	c40
8	Contact	[26] 20.10	m	m	[26] 20.10	i	i
9	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
10	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
11	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
12	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
13	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
14	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
15	Date	[26] 20.17	m	m	[26] 20.17	m	m
16	Expires	[26] 20.19	m	m	[26] 20.19	i	i
16A	Feature-Caps	[190]	c36	c36	[190]	c36	c36
17	From	[26] 20.20	m	m	[26] 20.20	m	m
17A	Geolocation	[89] 4.1	c26	c26	[89] 4.1	c27	c27
17B	Geolocation-Routing	[89] 4.1	c26	c26	[89] 4.1	c27	c27
17C	History-Info	[66] 4.1	c24	c24	[66] 4,1	c24	c24
17D	Max-Breadth	[117] 5.8	c31	c31	[117] 5.8	c32	c32
18	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
19	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
20	Organization	[26] 20.25	m	m	[26] 20.25	c3	c3
20A	P-Access-Network-Info	[52] 4.4, [234] 2	c16	c16	[52] 4.4, [234] 2	c17	c17
20B	P-Charging-Function-Addresses	[52] 4.5	c14	c14	[52] 4.5	c15	c15
20C	P-Charging-Vector	[52] 4.6	c12	c12	[52] 4.6	c13	c13
20E	P-User-Database	[82] 4	c25	c25	[82] 4	n/a	n/a
20F	P-Visited-Network-ID	[52] 4.3	c10	c10	[52] 4.3	c11	c11
20G	Path	[35] 4.2	c6	c6	[35] 4.2	c6	c6
20H	Privacy	[33] 4.2	c8	c8	[33] 4.2	c9	c9
21	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c7	c7
22	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
22A	Reason	[34A] 2	c19	c19	[34A] 2	c20	c20
22B	Recv-Info	[25] 5.2.3	c33	c33	[25] 5.2.3	c34	c34
22C	Referred-By	[59] 3	c22	c22	[59] 3	c23	c23
22D	Relayed-Charge	7.2.12	n/a	c37	7.2.12	n/a	c37
22E	Request-Disposition	[56B] 9.1	c21	c21	[56B] 9.1	c21	c21
23	Require	[26] 20.32	m	m	[26] 20.32	c4	c4
23A	Resource-Priority	[116] 3.1	c28	c28	[116] 3.1	c28	c28
23B	Resource-Share	Subclause 4.15	n/a	c38	Subclause 4.15	n/a	c38
24	Route	[26] 20.34	m	m	[26] 20.34	m	m
24A	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c18	c18
24B	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c18	c18
24C	Session-ID	[162]	c35	c35	[162]	c35	c35
25	Supported	[26] 20.37	m	m	[26] 20.37	c5	c5
26	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
27	To	[26] 20.39	m	m	[26] 20.39	m	m
28	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
29	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c3: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c4: IF A.162/11 OR A.162/12 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c5: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c6: IF A.162/29 THEN m ELSE n/a – – PATH header support. c7: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c8: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c9: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c10: IF A.162/38 THEN m ELSE n/a – – the P-Visited-Network-ID header extension. c11: IF A.162/39 THEN m ELSE i – – reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c12: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c13: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c14: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c15: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c16: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c17: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c18: IF A.162/47 OR 162/47A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c19: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c20: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c21: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c22: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c23: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c24: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c25: IF A.162/60 THEN m ELSE n/a – – the P-User-Database private header extension. c26: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c27: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c28: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c31: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c32: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c33: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c34: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c35: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c36: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c37: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c38: IF A.162/122 THEN m ELSE n/a – – resource sharing. c39: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c40: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/18 – – REGISTER request

Table A.276: Supported message bodies within the REGISTER request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	3GPP IM CN subsystem XML body	subclause 7.6	n/a	m	subclause 7.6	n/a	i

Table A.277: Void

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.277A: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/19 – – REGISTER response for all remaining status-codes

Table A.278: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
1A	Call-Info	[26] 20.9	m	m	[26] 20.9	c2	c2
2	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
3	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
4	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
5	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
6	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
7	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
8	Date	[26] 20.17	m	m	[26] 20.17	m	m
9	From	[26] 20.20	m	m	[26] 20.20	m	m
9A	Geolocation-Error	[89] 4.3	c13	c13	[89] 4.3	c14	c14
9B	History-Info	[66] 4.1	c12	c12	[66] 4.1	c12	c12
10	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
11	Organization	[26] 20.25	m	m	[26] 20.25	c1	c1
11A	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c9	c9	[52] 4.4, [52A] 4, [234] 2	c10	c10
11B	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c7	c7	[52] 4.5, [52A] 4	c8	c8
11C	P-Charging-Vector	[52] 4.6, [52A] 4	c5	c5	[52] 4.6, [52A] 4	c6	c6
11E	Privacy	[33] 4.2	c3	c3	[33] 4.2	c4	c4
11F	Relayed-Charge	7.2.12	n/a	c18	7.2.12	n/a	c18
11G	Require	[26] 20.32	m	m	[26] 20.32	c11	c11
11H	Server	[26] 20.35	m	m	[26] 20.35	i	i
11I	Session-ID	[162]	c17	c17	[162]	c17	c17
12	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
13	To	[26] 20.39	m	m	[26] 20.39	m	m
13A	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
14	Via	[26] 20.42	m	m	[26] 20.42	m	m
15	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c2: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c3: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c4: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c5: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c6: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c7: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c8: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c9: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c10: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c11: IF A.162/11 OR A.162/12 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c12: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c13: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c14: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c17: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c18: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension.

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.279: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
1A	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
1B	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
1C	Accept-Resource-Priority	[116] 3.2	c11	c11	[116] 3.2	c11	c11
2	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
3	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
5	Contact	[26] 20.10	m	m	[26] 20.10	i	i
5A	Feature-Caps	[190]	c16	c16	[190]	c16	c16
5B	Flow-Timer	[92] 11	c12	c12	[92] 11	c13	c14
5C	P-Associated-URI	[52] 4.1	c8	c8	[52] 4.1	c9	c10
6	Path	[35] 4.2	c3	c3	[35] 4.2	c4	c4
7	Security-Server	Subclause 7.2A.7	n/a	c15	Subclause 7.2A.7	n/a	n/a
8	Service-Route	[38] 5	c5	c5	[38] 5	c6	c7
9	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c3: IF A.162/29 THEN m ELSE n/a – – Path extension support. c4: IF A.162/29 THEN i ELSE n/a – – Path extension support. c5: IF A.162/32 THEN m ELSE n/a – – Service-Route extension support. c6: IF A.162/32 THEN i ELSE n/a – – Service-Route extension support. c7: IF A.162/32 THEN (IF A.3/2 THEN m ELSE i) ELSE n/a – – Service-Route extension and P-CSCF. c8: IF A.162/36 THEN m ELSE n/a – – the P-Associated-URI extension. c9: IF A.162/36 THEN i ELSE n/a – – the P-Associated-URI extension. c10: IF A.162/36 AND A.3/2 THEN m ELSE IF A.162/36 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a – – the P-Associated-URI extension and P-CSCF or I-CSCF or IBCF (THIG). c11: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c12: IF A.162/67 THEN m ELSE n/a – – managing client initiated transactions in SIP. c13: IF A.162/67 THEN m ELSE n/a – – managing client initiated transactions in SIP, P-CSCF, I-CSCF. c14: IF A.162/67 AND A.3/2 THEN m ELSE IF A.162/67 AND A.3/3 THEN i ELSE n/a – – managing client initiated transactions in SIP, P-CSCF, I-CSCF. c15: IF A.162/47A THEN m ELSE n/a – – mediasec header field parameter for marking security mechanisms related to media. c16: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy.

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.279A: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/103 OR A.164/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.280: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Contact	[26] 20.10	m	m	[26] 20.10	c2	c2
c2: IF A.162/19E THEN m ELSE i – – deleting Contact headers.

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/14 – – Additional for 401 (Unauthorized) response

Table A.281: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
6	Security-Server	[48] 2	x	c1	[48] 2	n/a	n/a
10	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.163/19 – – REGISTER response

Table A.282: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
6	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.283: Void

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.284: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
5	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
9	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type) response

Table A.285: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.285A: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80B THEN m ELSE n/a – – inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol.

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.286: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
8	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/17 THEN m ELSE i.

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.286A: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.163/19 – – REGISTER response

Prerequisite: A.164/29 – – Additional for 423 (Interval Too Brief) response

Table A.287: Supported header fields within the REGISTER response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
5	Min-Expires	[26] 20.23	m	m	[26] 20.23	i	i

Table A.288: Void

Prerequisite A.163/19 – – REGISTER response

Table A.289: Supported message bodies within the REGISTER response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.13 SUBSCRIBE method

Prerequisite A.163/20 – – SUBSCRIBE request

Table A.290: Supported header fields within the SUBSCRIBE request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
1A	Accept-Contact	[56B] 9.2	c27	c27	[56B] 9.2	c27	c28
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
3A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
4	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
5	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
6	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
6A	Call-Info	[26] 20.9	m	m	[26] 20.9	c73	c73
6B	Cellular-Network-Info	7.2.15	n/a	c76	7.2.15	n/a	c77
6C	Contact	[26] 20.10	m	m	[26] 20.10	i	i
7	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
8	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
9	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
10	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
11	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
12	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
13	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
14	Event	[28] 8.2.1	m	m	[28] 8.2.1	m	m
15	Expires	[26] 20.19	m	m	[26] 20.19	i	i
15A	Feature-Caps	[190]	c74	c74	[190]	c74	c74
16	From	[26] 20.20	m	m	[26] 20.20	m	m
16A	Geolocation	[89] 4.1	c35	c35	[89] 4.1	c36	c36
16B	Geolocation-Routing	[89] 4.1	c35	c35	[89] 4.1	c36	c36
16C	History-Info	[66] 4.1	c31	c31	[66] 4.1	c31	c31
16D	Max-Breadth	[117] 5.8	c47	c47	[117] 5.8	c48	c48
17	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
18	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
18A	Organization	[26] 20.25	m	m	[26] 20.25	c3	c3
18B	P-Access-Network-Info	[52] 4.4, [234] 2	c22	c22	[52] 4.4, [234] 2	c23	c23
18C	P-Asserted-Identity	[34] 9.1	c9	c9	[34] 9.1	c10	c10
18D	P-Asserted-Service	[121] 4.1	c39	c39	[121] 4.1	c40	c40
18E	P-Called-Party-ID	[52] 4.2	c13	c13	[52] 4.2	c14	c15
18F	P-Charging-Function-Addresses	[52] 4.5	c20	c20	[52] 4.5	c21	c21
18G	P-Charging-Vector	[52] 4.6	c18	c18	[52] 4.6	c19	c19
18I	P-Preferred-Identity	[34] 9.2	x	c69	[34] 9.2	c8	c8
18J	P-Preferred-Service	[121] 4.2	x	x	[121] 4.2	c38	c38
18K	P-Private-Network-Indication	[134]	c43	c43	[134]	c43	c43
18L	P-Profile-Key	[97] 5	c33	c33	[97] 5	c34	c34
18M	P-Served-User	[133] 6	c44	c44	[133] 6	c44	c44
18N	P-User-Database	[82] 4	c32	c32	[82] 4	c32	c32
18O	P-Visited-Network-ID	[52] 4.3	c16	o	[52] 4.3	c17	o
18P	Priority	[26] 20.26	m	m	[26] 20.26	i	c50
18Q	Privacy	[33] 4.2	c11	c11	[33] 4.2	c12	c12
19	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c4	c4
20	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
20A	Reason	[34A] 2	c25	c25	[34A] 2	c26	c26
21	Record-Route	[26] 20.30	m	m	[26] 20.30	c7	c7
21A	Referred-By	[59] 3	c29	c29	[59] 3	c30	c30
21B	Reject-Contact	[56B] 9.2	c27	c27	[56B] 9.2	c27	c28
21C	Relayed-Charge	7.2.12	n/a	c75	7.2.12	n/a	c75
21D	Request-Disposition	[56B] 9.1	c27	c27	[56B] 9.1	c27	c27
22	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
22A	Resource-Priority	[116] 3.1	c37	c37	[116] 3.1	c37	c37
23	Route	[26] 20.34	m	m	[26] 20.34	m	m
23A	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c24	c24
23B	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c24	c24
23C	Session-ID	[162]	c70	c70	[162]	c70	c70
24	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
24A	Target-Dialog	[184] 7	c71	c71	[184] 7	c72	c72
25	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
26	To	[26] 20.39	m	m	[26] 20.39	m	m
26A	Trigger-Consent	[125] 5.11.2	c41	c41	[125] 5.11.2	c42	c42
27	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
28	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c4: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN m ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/30A OR A.162/30C THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c9: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c10: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c11: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c12: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c13: IF A.162/37 THEN m ELSE n/a – – the P-Called-Party-ID header extension. c14: IF A.162/37 THEN i ELSE n/a – – the P-Called-Party-ID header extension. c15: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a – – the P-Called-Party-ID header extension and P-CSCF or I-CSCF or IBCF (THIG). c16: IF A.162/38 THEN m ELSE n/a – – the P-Visited-Network-ID header extension. c17: IF A.162/39 THEN m ELSE i – – reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c18: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c19: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c20: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c21: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c22: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c23: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/47 OR A.162/47A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c25: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c26: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c27: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c28: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a – – caller preferences for the session initiation protocol, and S-CSCF. c29: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c30: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c31: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c32: IF A.162/60 THEN m ELSE n/a – – the P-User-Database private header extension. c33: IF A.162/66A THEN m ELSE n/a – – making the first query to the database in order to populate the P-Profile-Key header. c34: IF A.162/66B THEN m ELSE n/a – – using the information in the P-Profile-Key header. c35: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c36: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c37: IF A.162/80A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c38: IF A.162/84A THEN m ELSE n/a – – act as authentication entity within the trust domain for asserted service. c39: IF A.162/84 THEN m ELSE n/a – – SIP extension for the identification of services. c40: IF A.162/84 OR A.162/30B THEN m ELSE i – – SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network.
c41: IF A.162/85 THEN m ELSE n/a – – a framework for consent-based communications in SIP. c42: IF A.162/85 THEN i ELSE n/a – – a framework for consent-based communications in SIP. c43: IF A.162/87 THEN m ELSE n/a – – the SIP P-Private-Network-Indication private-header (P-Header). c44 IF A.162/88 THEN m ELSE n/a – – the SIP P-Served-User private header. c47: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c48: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c50: IF A.162/115 THEN m ELSE i – – PSAP callback indicator. c69: IF A.162/30C THEN m ELSE x – – act as entity passing on identity transparently independent of trust domain. c70: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c71: IF A.162/109 THEN m ELSE n/a – – request authorization through dialog Identification in the session initiation protocol. c72: IF A.162/109 THEN i ELSE n/a – – request authorization through dialog Identification in the session initiation protocol. c73: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header field. c74: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c75: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c76: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c77: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/20 – – SUBSCRIBE request

Table A.291: Supported message bodies within the SUBSCRIBE request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	application/vnd.3gpp.mcptt-info+xml	[8ZE]	n/a	c1	[8ZE]	n/a	i
2	application/simple-filter+xml	[243]	o	c1	[243]	n/a	i
c1: 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 m ELSE n/a – – I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG).

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.291A: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/21 – – SUBSCRIBE response for all remaining status-codes

Table A.292: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
1A	Call-Info	[26] 20.9	m	m	[26] 20.9	c23	c23
1B	Cellular-Network-Info	7.2.15	n/a	c25	7.2.15	n/a	c26
2	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	i
3	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	i
4	Content-Language	[26] 20.13	m	m	[26] 20.13	i	i
5	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
6	Content-Type	[26] 20.15	m	m	[26] 20.15	i	i
7	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
8	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
9	From	[26] 20.20	m	m	[26] 20.20	m	m
9A	Geolocation-Error	[89] 4.3	c20	c20	[89] 4.3	c21	c21
9B	History-Info	[66] 4.1	c15	c15	[66] 4.1	c15	c15
10	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	i
10A	Organization	[26] 20.25	m	m	[26] 20.25	c2	c2
10B	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c12	c12	[52] 4.4, [52A] 4, [234] 2	c13	c13
10C	P-Asserted-Identity	[34] 9.1	c4	c4	[34] 9.1	c5	c5
10D	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c10	c10	[52] 4.5, [52A] 4	c11	c11
10E	P-Charging-Vector	[52] 4.6, [52A] 4	c8	c8	[52] 4.6, [52A] 4	c9	c9
10G	P-Preferred-Identity	[34] 9.2	x	x	[34] 9.2	c3	n/a
10H	Privacy	[33] 4.2	c6	c6	[33] 4.2	c7	c7
10I	Relayed-Charge	7.2.12	n/a	c24	7.2.12	n/a	c24
10J	Require	[26] 20.32	m	m	[26] 20.32	c14	c14
10K	Server	[26] 20.35	m	m	[26] 20.35	i	i
10L	Session-ID	[162]	c22	c22	[162]	c22	c22
11	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
12	To	[26] 20.39	m	m	[26] 20.39	m	m
12A	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
13	Via	[26] 20.42	m	m	[26] 20.42	m	m
14	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c3: IF A.162/30A THEN m ELSE n/a – – act as first entity within the trust domain for asserted identity. c4: IF A.162/30 THEN m ELSE n/a – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c5: IF A.162/30A or A.162/30B THEN m ELSE i – – extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c6: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c8: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c9: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c10: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c11: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c12: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c13: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c15: IF A.162/57 THEN m ELSE n/a – – an extension to the session initiation protocol for request history information. c16: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c17: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c20: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c21: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c22: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c23: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header field. c24: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c25: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c26: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.293: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Accept-Resource-Priority	[116] 3.2	c4	c4	[116] 3.2	c4	c4
0B	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	i	i
1	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
1A	Contact	[26] 20.10	m	m	[26] 20.10	i	i
2	Expires	[26] 20.19	m	m	[26] 20.19	i	i
2A	Feature-Caps	[190]	c6	c6	[190]	c6	c6
3	Record-Route	[26] 20.30	m	m	[26] 20.30	c3	c3

6	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c3: IF A.162/15 THEN m ELSE i – – the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/80A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c6: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy.

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.293A: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/103 OR A.164/35 – – Additional for 3xx or 485 (Ambiguous) response

Table A.294: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Contact	[26] 20.10	m	m	[26] 20.10	c1	c1
c1: IF A.162/19E THEN m ELSE i – – deleting Contact headers.

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/14 – – Additional for 401 (Unauthorized) response

Table A.295: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
8	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 – – Additional for 404 (Not Found), 413 (Request Entity Too Large), 480 (Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response

Table A.296: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.297: Void

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.298: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
6	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Table A.298A: Void

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type) response

Table A.299: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.299A: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80A THEN m ELSE n/a – – inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol.

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.300: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
5	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.300A: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/29 – – Additional for 423 (Interval Too Brief) response

Table A.301: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Min-Expires	[26] 20.23	m	m	[26] 20.23	i	i

Table A.302: Void

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/29H – – Additional for 470 (Consent Needed) response

Table A.302A: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Permission-Missing	[125] 5.9.3	m	m	[125] 5.9.3	m	m

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/39 – – Additional for 489 (Bad Event) response

Table A.303: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
		Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Table A.303A: Void

Prerequisite A.163/21 – – SUBSCRIBE response

Prerequisite: A.164/46 – – Additional for 504 (Server Time-out) response

Table A.303B: Supported header fields within the SUBSCRIBE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Restoration-Info	subclause 7.2.11	n/a	c1	subclause 7.2.11	n/a	n/a
c1: IF A.4/110 THEN o ELSE n/a – – HSS based P-CSCF restoration.

Prerequisite A.163/21 – – SUBSCRIBE response

Table A.304: Supported message bodies within the SUBSCRIBE response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

A.2.2.4.14 UPDATE method

Prerequisite A.163/22 – – UPDATE request

Table A.305: Supported header fields within the UPDATE request

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
1A	Accept-Contact	[56B] 9.2	c21	c21	[56B] 9.2	c22	c22
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
4	Allow	[26] 20.5	m	m	[26] 20.5	i	i
5	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
6	Authorization	[26] 20.7	m	m	[26] 20.7	i	i
7	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
8	Call-Info	[26] 20.9	m	m	[26] 20.9	c8	c8
8A	Cellular-Network-Info	7.2.15	n/a	c52	7.2.15	n/a	c53
9	Contact	[26] 20.10	m	m	[26] 20.10	i	i
10	Content-Disposition	[26] 20.11	m	m	[26] 20.11	c4	c4
11	Content-Encoding	[26] 20.12	m	m	[26] 20.12	c4	c4
12	Content-Language	[26] 20.13	m	m	[26] 20.13	c4	c4
13	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
14	Content-Type	[26] 20.15	m	m	[26] 20.15	c4	c4
15	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
16	Date	[26] 20.17	m	m	[26] 20.17	c2	c2
16A	Feature-Caps	[190]	c49	c49	[190]	c49	c49
17	From	[26] 20.20	m	m	[26] 20.20	m	m
17A	Geolocation	[89] 4.1	c26	c26	[89] 4.1	c27	c27
17B	Geolocation-Routing	[89] 4.1	c26	c26	[89] 4.1	c27	c27
17C	Max-Breadth	[117] 5.8	c32	c32	[117] 5.8	c33	c33
18	Max-Forwards	[26] 20.22	m	m	[26] 20.22	m	m
19	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	c4
19A	Min-SE	[58] 5	c23	c23	[58] 5	c23	c23
20	Organization	[26] 20.25	m	m	[26] 20.25	c3	c3
20A	P-Access-Network-Info	[52] 4.4, [234] 2	c16	c16	[52] 4.4, [234] 2	c17	c17
20B	P-Charging-Function-Addresses	[52] 4.5	c14	c14	[52] 4.5	c15	c15
20C	P-Charging-Vector	[52] 4.6	c12	c12	[52] 4.6	c13	c13
20E	P-Early-Media	[109] 8	o	c28	[109] 8	o	c28
20EA	Priority-Share	Subclause 7.2.16	n/a	c54	Subclause 7.2.16	n/a	c54
20F	Privacy	[33] 4.2	c10	c10	[33] 4.2	c11	c11
21	Proxy-Authorization	[26] 20.28	m	m	[26] 20.28	c9	c9
22	Proxy-Require	[26] 20.29	m	m	[26] 20.29	m	m
22A	Reason	[34A] 2	c19	c19	[34A] 2	c20	c20
23	Record-Route	[26] 20.30	m	m	[26] 20.30	c7	c7
23A	Recv-Info	[25] 5.2.3	c34	c34	[25] 5.2.3	c35	c35
23B	Referred-By	[59] 3	c24	c24	[59] 3	c25	c25
23C	Reject-Contact	[56B] 9.2	c21	c21	[56B] 9.2	c22	c22
23D	Relayed-Charge	7.2.12	n/a	c50	7.2.12	n/a	c50
23E	Request-Disposition	[56B] 9.1	c21	c21	[56B] 9.1	c22	c22
24	Require	[26] 20.32	m	m	[26] 20.32	c5	c5
24A	Resource-Priority	[116] 3.1	c47	c47	[116] 3.1	c47	c47
24B	Resource-Share	Subclause 4.15	n/a	c51	Subclause 4.15	n/a	c51
25	Route	[26] 20.34	m	m	[26] 20.34	m	m
25A	Security-Client	[48] 2.3.1	x	x	[48] 2.3.1	c18	c18
25B	Security-Verify	[48] 2.3.1	x	x	[48] 2.3.1	c18	c18
25C	Session-Expires	[58] 4	c23	c23	[58] 4	c23	c23
25D	Session-ID	[162]	c48	c48	[162]	c48	c48
26	Supported	[26] 20.37	m	m	[26] 20.37	c6	c6
27	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
28	To	[26] 20.39	m	m	[26] 20.39	m	m
29	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
30	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c4: IF A.3/2 OR A.3/4 THEN m ELSE i – – P-CSCF or S-CSCF. c5: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i – – reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i – – the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c9: IF A.162/8A THEN m ELSE i – – authentication between UA and proxy. c10: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c11: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c12: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c13: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c14: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c15: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c16: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c17: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c18: IF A.162/47 OR A.162/47A THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c19: IF A.162/48 THEN m ELSE n/a – – the Reason header field for the session initiation protocol. c20: IF A.162/48 THEN i ELSE n/a – – the Reason header field for the session initiation protocol. c21: IF A.162/50 THEN m ELSE n/a – – caller preferences for the session initiation protocol. c22: IF A.162/50 THEN i ELSE n/a – – caller preferences for the session initiation protocol. c23: IF A.162/52 THEN m ELSE n/a – – the SIP session timer. c24: IF A.162/53 THEN i ELSE n/a – – the SIP Referred-By mechanism. c25: IF A.162/53 THEN m ELSE n/a – – the SIP Referred-By mechanism. c26: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c27: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c28: IF A.162/76 THEN m ELSE n/a – – the SIP P-Early-Media private header extension for authorization of early media. c32: IF A.162/81 THEN m ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies. c33: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a – – addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c34: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c35: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c47: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c48: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c49: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c50: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c51: IF A.162/122 THEN o ELSE n/a – – resource sharing. c52: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c53: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c54: IF A.162/124 THEN o ELSE n/a – – priority sharing.
NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY.

Prerequisite A.163/22 – – UPDATE request

Table A.306: Supported message bodies within the UPDATE request

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/1 – – Additional for 100 (Trying) response

Table A.306A: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
2	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
3	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
4	Date	[26] 20.17	c1	c1	[26] 20.17	c2	c2
5	From	[26] 20.20	m	m	[26] 20.20	m	m
6	To	[26] 20.39	m	m	[26] 20.39	m	m
7	Via	[26] 20.42	m	m	[26] 20.42	m	m
c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a – – stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m – – Stateless proxy passes on.

Prerequisite A.163/22 – – UPDATE response for all remaining status-codes

Table A.307: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Allow	[26] 20.5	m	m	[26] 20.5	i	i
1	Call-ID	[26] 20.8	m	m	[26] 20.8	m	m
1A	Call-Info	[26] 20.9	m	m	[26] 20.9	c4	c4
1B	Cellular-Network-Info	7.2.15	n/a	c22	7.2.15	n/a	c23
1C	Contact	[26] 20.10	m	m	[26] 20.10	i	i
2	Content-Disposition	[26] 20.11	m	m	[26] 20.11	i	c3
3	Content-Encoding	[26] 20.12	m	m	[26] 20.12	i	c3
4	Content-Language	[26] 20.13	m	m	[26] 20.13	i	c3
5	Content-Length	[26] 20.14	m	m	[26] 20.14	m	m
6	Content-Type	[26] 20.15	m	m	[26] 20.15	i	c3
7	CSeq	[26] 20.16	m	m	[26] 20.16	m	m
8	Date	[26] 20.17	m	m	[26] 20.17	c1	c1
9	From	[26] 20.20	m	m	[26] 20.20	m	m
9A	Geolocation-Error	[89] 4.3	c14	c14	[89] 4.3	c15	c15
10	MIME-Version	[26] 20.24	m	m	[26] 20.24	i	c3
10A	Organization	[26] 20.25	m	m	[26] 20.25	c2	c2
10B	P-Access-Network-Info	[52] 4.4, [52A] 4, [234] 2	c11	c11	[52] 4.4, [52A] 4, [234] 2	c12	c12
10C	P-Charging-Function-Addresses	[52] 4.5, [52A] 4	c9	c9	[52] 4.5, [52A] 4	c10	c10
10D	P-Charging-Vector	[52] 4.6, [52A] 4	c7	c7	[52] 4.6, [52A] 4	c8	c8
10F	Privacy	[33] 4.2	c5	c5	[33] 4.2	c6	c6
10G	Recv-Info	[25] 5.2.3	c18	c18	[25] 5.2.3	c19	c19
10H	Relayed-Charge	7.2.12	n/a	c21	7.2.12	n/a	c21
10I	Require	[26] 20.32	m	m	[26] 20.32	c13	c13
10J	Server	[26] 20.35	m	m	[26] 20.35	i	i
10K	Session-ID	[162]	c20	c20	[162]	c20	c20
11	Timestamp	[26] 20.38	m	m	[26] 20.38	i	i
12	To	[26] 20.39	m	m	[26] 20.39	m	m
12A	User-Agent	[26] 20.41	m	m	[26] 20.41	i	i
13	Via	[26] 20.42	m	m	[26] 20.42	m	m
14	Warning	[26] 20.43	m	m	[26] 20.43	i	i
c1: IF A.162/9 THEN m ELSE i – – insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i – – reading, adding or concatenating the Organization header. c3: IF A.3/2 OR A.3/4 THEN m ELSE i – – P-CSCF or S-CSCF. c4: IF A.162/19C OR A.162/19D THEN m ELSE i – – reading, adding or concatenating the Call-Info header. c5: IF A.162/31 THEN m ELSE n/a – – a privacy mechanism for the Session Initiation Protocol (SIP). c6: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a – – application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c7: IF A.162/45 THEN m ELSE n/a – – the P-Charging-Vector header extension. c8: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a – – adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c9: IF A.162/44 THEN m ELSE n/a – – the P-Charging-Function-Addresses header extension. c10: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a – – adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c11: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c12: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c13: IF A.162/11 OR A.162/13 THEN m ELSE i – – reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c14: IF A.162/70 THEN m ELSE n/a – – SIP location conveyance. c15: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a – – addition or modification of location in a SIP method, passes on locations in SIP method without modification. c18: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c19: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c20: IF A.162/101 THEN m ELSE n/a – – the Session-ID header. c21: IF A.162/121 THEN m ELSE n/a – – the Relayed-Charge header field extension. c22: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c23: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a – – act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension.

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/102 – – Additional for 2xx response

Table A.308: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
0A	Accept	[26] 20.1	m	m	[26] 20.1	i	i
0B	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
0C	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i
0D	Accept-Resource-Priority	[116] 3.2	c12	c12	[116] 3.2	c12	c12
1	Allow-Events	[28] 8.2.2	m	m	[28] 8.2.2	c1	c1
2	Authentication-Info	[26] 20.6	m	m	[26] 20.6	i	i
3	Contact	[26] 20.10	m	m	[26] 20.10	i	i
3A	Feature-Caps	[190]	c14	c14	[190]	c14	c14
3B	P-Early-Media	[109] 8	o	c10	[109] 8	o	c11
3BA	Priority-Share	Subclause 7.2.16	n/a	c16	Subclause 7.2.16	n/a	c16
3C	Record-Route	[26] 20.30	m	m	[26] 20.30	c3	c3
3D	Recv-Info	[25] 5.2.3	c5	c5	[25] 5.2.3	c6	c6
3E	Resource-Share	Subclause 4.15	n/a	c15	Subclause 4.15	n/a	c15
4	Session-Expires	[58] 4	c4	c4	[58] 4	c4	c4
6	Supported	[26] 20.37	m	m	[26] 20.37	i	i
c1: IF A.4/20 THEN m ELSE i – – SIP specific event notification extension. c3: IF A.162/15 THEN o ELSE i – – the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/52 THEN m ELSE n/a – – the SIP session timer. c5: IF A.162/20 THEN m ELSE n/a – – SIP INFO method and package framework. c6: IF A.162/20 THEN i ELSE n/a – – SIP INFO method and package framework. c10: IF A.162/76 THEN m ELSE n/a – – the SIP P-Early-Media private header extension for authorization of early media. c11: IF A.162/76 THEN (IF A.3/2 THEN m ELSE i) ELSE n/a – – P-CSCF, using the information in the P-Early-Media header. c12: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol. c14: IF A.162/110 THEN m ELSE n/a – – indication of features supported by proxy. c15: IF A.162/122 THEN o ELSE n/a – – resource sharing. c16: IF A.162/124 THEN o ELSE n/a – – priority sharing.

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 – – Additional for 3xx – 6xx response

Table A.308A: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Error-Info	[26] 20.18	m	m	[26] 20.18	i	i
2	Response-Source	7.2.17	n/a	c1	7.2.17	n/a	c1
c1: IF A.162/125 THEN o ELSE n/a – – use of the Response-Source header field in SIP error responses?

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/103 or A.164/35 – – Additional for 3xx, 485 (Ambiguous) response

Table A.309: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
2	Contact	[26] 20.10	m	m	[26] 20.10	c1	c1
c1: IF A.162/19E THEN m ELSE i – – deleting Contact headers.

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/14 – – Additional for 401 (Unauthorized) response

Table A.309A: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
6	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/23 – – UPDATE response

Table A.310: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
5	Retry-After	[26] 20.33	m	m	[26] 20.33	i	i

Table A.311: Void

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/20 – – Additional for 407 (Proxy Authentication Required) response

Table A.312: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
4	Proxy-Authenticate	[26] 20.27	m	m	[26] 20.27	m	m
8	WWW-Authenticate	[26] 20.44	m	m	[26] 20.44	i	i

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/25 – – Additional for 415 (Unsupported Media Type) response

Table A.313: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept	[26] 20.1	m	m	[26] 20.1	i	i
2	Accept-Encoding	[26] 20.2	m	m	[26] 20.2	i	i
3	Accept-Language	[26] 20.3	m	m	[26] 20.3	i	i

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/26A – – Additional for 417 (Unknown Resource-Priority) response

Table A.313A: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Accept-Resource-Priority	[116] 3.2	c1	c1	[116] 3.2	c1	c1
c1: IF A.162/80 THEN m ELSE n/a – – communications resource priority for the session initiation protocol.

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/27 – – Additional for 420 (Bad Extension) response

Table A.314: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
7	Unsupported	[26] 20.40	m	m	[26] 20.40	c3	c3
c3: IF A.162/18 THEN m ELSE i – – reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER.

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/28 OR A.164/41A – – Additional for 421 (Extension Required), 494 (Security Agreement Required) response

Table A.314A: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
3	Security-Server	[48] 2	c1	c1	[48] 2	n/a	n/a
c1: IF A.162/47 THEN m ELSE n/a – – security mechanism agreement for the session initiation protocol.

Prerequisite A.163/23 – – UPDATE response

Prerequisite: A.164/28A – – Additional for 422 (Session Interval Too Small) response

Table A.314B: Supported header fields within the UPDATE response

Item	Header field	Sending			Receiving
Item	Header field	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1	Min-SE	[58] 5	c1	c1	[58] 5	c1	c1
c1: IF A.162/52 THEN m ELSE n/a – – the SIP session timer.

Table A.315: Void

Prerequisite A.163/23 – – UPDATE response

Table A.316: Supported message bodies within the UPDATE response

Item	Header	Sending			Receiving
Item	Header	Ref.	RFC status	Profile status	Ref.	RFC status	Profile status
1