2009/5/14 kishore sowdi <[email protected]>: > Hi, > Section 15 of RFC 3261 says - "The caller’s UA MAY send a BYE for > eitherconfirmed or early dialogs, and the callee’s UA MAY send a BYE > onconfirmed dialogs, but MUST NOT send a BYE on early dialogs". > Section 12.1 of RFC 3261 says - "A dialog established by a non-final response > to a request is in the "early" state and it is called an early dialog". > Section 9.1 of RFC 3261 says - "If no provisional response has been received, > the CANCEL request MUST NOT be sent; rather, the client MUST wait for the > arrival of aprovisional response before sending the request. If the > original request has generated a final response, the CANCEL SHOULD NOT > be sent, as it is an effective no-op, since CANCEL has no effect on requests > that have already generated a final response". > So , How In early dialog state can UAC send BYE?
Why not? there is no issue in what you describe, not at all. The UAC can send a BYE after a UAS has replies a1XX response (with To tag and Route headers), no problem at all. > I want to know the used case when caller's UA will send a BYE for a early > dailog case. - Alice calls Bob through a proxy. - The proxy receives the INVITE and orkes it to Bob1 and Bob2. - Bob1 and Bob2 start ringing (180) => two early dialogs. - Alice wants to discard the early dialog with Bob2. - So Alice sends a BYE with RURI being th eContact received in the 180 from Bob2 and route set. - Bob2 stops ringing but Bob1 remains on it. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
