Sounds okay; however the CANCEL is typically still needed to cancel the INVITE (when appropriate) since the BYE received on early dialog isn't adequate to communicate/trigger cancellation of INVITE.
The lack of CANCEL can trigger useless forking by proxy/b2bua upon receiving INVITE 487 (or other failure response because BYE) when the caller no longer cares about INVITE. > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of BONNAERENS Ben > Sent: Monday, May 11, 2009 10:16 AM > To: Damir Reic; [email protected] > Subject: Re: [Sip-implementors] B2BUA release > > Hello, > > Don't forget CANCEL is hop by hop while BYE is end to end. > > In a BYE, a Reason header, a body, proprietary information, etc can be > passed to the UAS. > > Best regards, > > Ben. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
