Additionally even though a forking proxy/B2BUA is not shown within the example... if forking occurs, the caller may not immediately or ever see the INVITE's 487 response associated with the specific early dialog since it may be consumed by the forking proxy/B2BUA while the other dialogs continue to exist and be created.
> -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of Iñaki Baz > Castillo > Sent: Tuesday, February 22, 2011 5:13 AM > To: [email protected] > Cc: [email protected] > Subject: Re: [Sip-implementors] SIP flow for BYE sent for early dialog > > 2011/2/21 Nauman Sulaiman <[email protected]>: > > Hi, If the caller sends a BYE for an early dialog what should the > callee send as response to INVITE. I understand a 200K would be sent > for the BYE. > > > > caller -------------------> Callee > > INVITE > > > > caller <------------------- Callee > > 100 Trying > > > > caller ---------------------> Callee > > BYE > > > > caller <--------------------- callee > > 200 OK (BYE) > > > > ? > > > > ? > > > As Joegen pointed out, the above flow needs a 1XX provisional response > (>100) so there would be a Totag and an early dialog. > Then caller can send a BYE and callee should reply 200 to the BYE and > 487 to the INVITE: > > > RFC 3261 - 15.1.2 UAS Behavior > > A UAS core receiving a BYE request for an existing dialog MUST > follow > the procedures of Section 12.2.2 to process the request. Once done, > the UAS SHOULD terminate the session (and therefore stop sending and > listening for media). The only case where it can elect not to are > multicast sessions, where participation is possible even if the > other > participant in the dialog has terminated its involvement in the > session. Whether or not it ends its participation on the session, > the UAS core MUST generate a 2xx response to the BYE, and MUST pass > that to the server transaction for transmission. > > The UAS MUST still respond to any pending requests received for that > dialog. It is RECOMMENDED that a 487 (Request Terminated) response > be generated to those pending requests. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
