The ACK for a 2xx constitutes a separate transaction, see for example
the definition of transaction:
SIP Transaction: A SIP transaction occurs between a client and a
server and comprises all messages from the first request
sent from the client to the server up to a final (non-1xx)
response sent from the server to the client. If the
request is INVITE and the final response is a non-2xx, the
transaction also includes an ACK to the response. The ACK
for a 2xx response to an INVITE request is a separate
transaction.
Anders
Nils Henrik Lorentzen wrote:
> In bis-09, 17.2.3: Matching Requests to Server Transactions
>
> "The ACK request matches a transaction if the Request-
> URI, From tag, Call-ID, CSeq number (not the method), and top Via
> header field match those of the INVITE request which created the
> transaction, and the To tag of the ACK matches the To tag of the
> response sent by the server transaction."
>
> But couldn't the ACK request Request-URI perfectly well be different
> from that of the INVITE ? AFAI have understood, the UAC should
> send the ACK to the url given in the Contact field of the
> 200 OK or possibly the first Route header.
>
> Am I missing something, or is this a spec typo ?
>
> Nils Henrik
>
>
>
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
