This is the question I'm asking because I've seen this B2BUA that actually has a configurable option to send BYE or CANCEL on early dialogs and I don't see any reasons for it. If someone does, please explain. > CANCEL is only solution here. In case, B2BUA receives 200 OK before it could send CANCEL then, it should confirm this dialog and then send BYE. Could you name B2bua who sends BYE in early dialogs ?
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Damir Reic Sent: Monday, May 11, 2009 4:20 PM To: [email protected] Subject: [Sip-implementors] B2BUA release Hi all, a question from B2BUA perspective. If on incoming side release is started (not necessarily SIP on incoming side) and on outgoing SIP side we have established several early dialogs (no confirmed), is there any sense to send BYE for each of these dialogs? For me it is not. I believe CANCEL is not just preferred but what must be. It can cause several problems in the network and to itself. First it can cause problems to forking proxy which can continue forking until it exhausts all sources. This implies it makes problems to itself because all provisional responses that come in 64*T1 can be received which should initiate early dialogs. Also, if the provisional responses from UASs that were not received (or were not sent) can soon send 200_OK which will lead to confirmed dialog creation. This is the question I'm asking because I've seen this B2BUA that actually has a configurable option to send BYE or CANCEL on early dialogs and I don't see any reasons for it. If someone does, please explain. regards, Damir _______________________________________________ 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
