2011/7/27 Leo Leo <[email protected]>: > Anyway, the RFC says that a receiving BYE must to finish all transactions of > the associated dialog.
Interesting, never thought about it. So, if I send a re-INVITE for which I have no final reply yet and then I send a BYE, should the UAS reply 200 for the BYE and terminate the remaining re-INVITE transasction without sending a final response? Or should the UAS reply a "491 Request Pending" for the BYE? Anyhow section 14.2 in RFC 3261 just indicates that 491 is useful when there is a pending re-INVITE from A to B and B sends a re-INVITE to A. In that case A should reply 491. > The unique transaction which remains is the BYE transaction for sending > another 200 OK for some retransmission. > > Although, the UAC may send some final response (i.e. 487) before sending the > 200 OK for the BYE. In matter fact, there is some homologating procedures > which requires this behaviour. If the BYE is supposed to "magically" terminate all the pending transactions within the dialog (without requiring a final response for them) then I see no reason to send a 487 (maybe it would fail as the UAC would already terminate the client transaction for the initial INVITE). Interesting topic :) Regards. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
