SIP ACK - Revision history

Pchero: /* Basic */

2020-02-03T16:17:24Z

Basic

← Older revision		Revision as of 16:17, 3 February 2020
Line 8:		Line 8:

	For 2xx responses, the ACK is end-to-end, but for all other final responses, it is done on a hop-by-hop basis when stateful proxies are involved. As a result, a proxy will generate an ACK for a 3xx, 4xx, 5xx, or 6xx response to an INVITE, as well as forwarding the response. The end-to-end nature of ACKs to 2xx responses allows a message body to be transported. An ACK generated in a hop-by-hop acknowledgment will contain just a single Via header with the address of the proxy server generating the ACK. The difference between hop-by-hop acknowledgments and response end-to-end acknowledgments is shown in the message.		For 2xx responses, the ACK is end-to-end, but for all other final responses, it is done on a hop-by-hop basis when stateful proxies are involved. As a result, a proxy will generate an ACK for a 3xx, 4xx, 5xx, or 6xx response to an INVITE, as well as forwarding the response. The end-to-end nature of ACKs to 2xx responses allows a message body to be transported. An ACK generated in a hop-by-hop acknowledgment will contain just a single Via header with the address of the proxy server generating the ACK. The difference between hop-by-hop acknowledgments and response end-to-end acknowledgments is shown in the message.

			A hop-by-hop ACK reuses the same branch ID as the INVITE since it is considered part of the same transaction. An end-to-end ACK uses a different branch ID as it is considered a new transaction.

			A stateful proxy receiving an ACK message must determine whether or not the ACK should be forwarded downstream to another proxy or user agent. That is, is the ACK a hop-by-hop ACK or an end-to-end ACK? This is done by comparing the branch ID for a match pending transaction branch IDs. If there is not an exact match, the ACK is proxied toward the UAS. Otherwise, the ACK is for this hop and is not forwarded by the proxy.

			=== Mandatory headers ===
			These items are mandatory for ACK request.
			<pre>
			* Via
			* To
			* From
			* Call-ID
			* CSeq
			* Max-Forwards
			</pre>

	[[category:SIP protocol]]		[[category:SIP protocol]]

Pchero: /* Basic */

2020-02-03T16:08:53Z

Basic

← Older revision		Revision as of 16:08, 3 February 2020
Line 6:		Line 6:

	An ACK may contain a application/sdp message body. This is permitted if the initial INVITE did not contain a SDP message body. If the INVITE contained an SDP offer message body, the ACK may not contain an SDP message body. The ACK may not be used to modify a media description that has already been sent in the initial INVITE; a re-INVITE or UPDATE must be used for this purpose. SDP in an ACK is used in some interworking scenarios with other protocols where the media characteristics may not be known when the initial INVITE is generated and sent.		An ACK may contain a application/sdp message body. This is permitted if the initial INVITE did not contain a SDP message body. If the INVITE contained an SDP offer message body, the ACK may not contain an SDP message body. The ACK may not be used to modify a media description that has already been sent in the initial INVITE; a re-INVITE or UPDATE must be used for this purpose. SDP in an ACK is used in some interworking scenarios with other protocols where the media characteristics may not be known when the initial INVITE is generated and sent.

			For 2xx responses, the ACK is end-to-end, but for all other final responses, it is done on a hop-by-hop basis when stateful proxies are involved. As a result, a proxy will generate an ACK for a 3xx, 4xx, 5xx, or 6xx response to an INVITE, as well as forwarding the response. The end-to-end nature of ACKs to 2xx responses allows a message body to be transported. An ACK generated in a hop-by-hop acknowledgment will contain just a single Via header with the address of the proxy server generating the ACK. The difference between hop-by-hop acknowledgments and response end-to-end acknowledgments is shown in the message.

	[[category:SIP protocol]]		[[category:SIP protocol]]

Pchero at 16:04, 3 February 2020

2020-02-03T16:04:17Z

← Older revision		Revision as of 16:04, 3 February 2020
Line 1:		Line 1:
	== Overview ==		== Overview ==
	SIP ACK request 내용 정리.		SIP ACK request 내용 정리.

			== Basic ==
			The ACK method is used to acknowledge final responses to INVITE requests. Final responses to all other requests are never acknowledged. Final responses are defined as 2xx, 3xx, 4xx, 5xx, or 6xx class responses. The CSeq number is never incremented for an ACK, but the CSeq method is changed to ACK. This is so that a UAS can match the CSeq number of the ACK with the number of the corresponding INVITE.

			An ACK may contain a application/sdp message body. This is permitted if the initial INVITE did not contain a SDP message body. If the INVITE contained an SDP offer message body, the ACK may not contain an SDP message body. The ACK may not be used to modify a media description that has already been sent in the initial INVITE; a re-INVITE or UPDATE must be used for this purpose. SDP in an ACK is used in some interworking scenarios with other protocols where the media characteristics may not be known when the initial INVITE is generated and sent.

	[[category:SIP protocol]]		[[category:SIP protocol]]

Pchero at 13:35, 3 February 2020

2020-02-03T13:35:00Z

← Older revision		Revision as of 13:35, 3 February 2020
Line 2:		Line 2:
	SIP ACK request 내용 정리.		SIP ACK request 내용 정리.

	[[category:~~telephony~~]]		[[category:SIP protocol]]

Pchero: Created page with "== Overview == SIP ACK request 내용 정리. category:telephony"

2020-02-03T13:33:25Z

Created page with "== Overview == SIP ACK request 내용 정리. category:telephony"

New page

== Overview ==
SIP ACK request 내용 정리.

[[category:telephony]]