I agree with Maxim here. If dialog terminates before transaction, RFC3261 does not say clearly if UA need destroy those transactions explicitly or let them complete their lifecycle. I think it's up to implementation.
Regards, -Rockson -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Maxim Sobolev Sent: Tuesday, December 30, 2008 7:36 AM To: Dale Worley Cc: [email protected] Subject: Re: [Sip-implementors] BYE in Confirmed/Moratorium state (RFC 5407) Dale Worley wrote: > Looking at the figure, it appears that Confirmed/Moratorium is allowed > to receive and act on BYE. This seems to be an error to me, but even > if I don't think it's an error. RFC3261 also allows BYE on early dialogs, so that UAS should be prepared to receive and act on BYE even after sending 183 Session Progress, let alone 200 OK. I think people confuse INVITE transaction state and dialog state. While related, still they are separate entities and this example shows, the dialog could finish earlier than INVITE transaction. Regards, -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts T/F: +1-646-651-1110 Web: http://www.sippysoft.com MSN: [email protected] Skype: SippySoft _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
