From: Nina Garaca <[EMAIL PROTECTED]> I have a question about terminating the dialog during the session modifiaction with a reINVITE:
Q: Does this claim also refer to reINVITE ? / / / RFC 3261/15 / / The caller's UA MAY send a BYE for either/ / confirmed or early dialogs, and the callee's UA MAY send a BYE on/ / confirmed dialogs, but MUST NOT send a BYE on early dialogs./ / 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*. If no SIP extensions have defined other/ / application layer states associated with the dialog, the BYE also/ / terminates the dialog./ I strongly believe that this text only refers to dialog-creating INVITEs (and not re-INVITES), because these rules are needed to handle the complexities of when the INVITE forks (because the UAC is not initially aware of the entire set of UASs that may be responding). For instance, the text you have highlighted is to ensure that the UAC has received the 2xx before it receives the BYE. Once a confirmed dialog is created, none of these problems can happen. And so I see no reason that a re-INVITE should require special coordination with BYE. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
