Re: Possible bug in "Non-INVITE Client Transaction" - 17.1.2.2

2011/4/8 Peter Hanratty <[email protected]>:
> While youre at it, the INVITE server transaction could use some rethinking.
> Terminating on a 2xx but on no other final response is a bit daft and makes
> people like me want to cut corners rather than use other objects such as the
> dialog or session to handle the ACK, which doesn't really make for a nice
> logical model :)  The ACK is attached to a single transaction and should
> handled by that transaction (as it is for a non-2xx final response).

Hi Peter, you should take a look to RFC 6026 "Correct Transaction
Handling for 2xx Responses to SIP INVITE Requests".
;)

-- 
Iñaki Baz Castillo
<[email protected]>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is essentially closed and only used for finishing old business.
Use [email protected] for questions on how to develop a SIP implementation.
Use [email protected] for new developments on the application of sip.
Use [email protected] for issues related to maintenance of the core SIP specifications.