El Miércoles, 13 de Enero de 2010, Pandurangan R S escribió: > > A UA cannot send a BYE for a call until it has received an ACK for > > the initial INVITE. This was allowed in RFC 2543 but leads to a > > potential race condition. > > Probably that should read > > A UA cannot send a BYE for a call until it has received an ACK for > the initial INVITE or *server transaction has timed out*. This was > allowed in RFC 2543 but leads to a potential race condition. > > This is appropriately indicated below (RFC 3261) > > 13.3.1.4 The INVITE is Accepted > > If the server retransmits the 2xx response for 64*T1 seconds without > receiving an ACK, the dialog is confirmed, but the session SHOULD be > terminated. This is accomplished with a BYE, as described in Section > 15. > > 15 Terminating a Session > > However, the callee's UA MUST NOT send a BYE on a confirmed dialog > until it has received an ACK for its 2xx response or until the server > transaction times out.
Unfortunatelly this doesn't avoid race conditions as the UAS could use a different T1 than the UAC, and the network delay can also affect. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
