No CANCEL or BYE is to be sent by the UAC if you have several early dialogs and you get one or more 2xx response. Refer 13.2.2.4 of 3261
"The UAC core considers the INVITE transaction completed 64*T1 seconds after the reception of the first 2xx response. At this point all the early dialogs that have not transitioned to established dialogs are terminated. Once the INVITE transaction is considered completed by the UAC core, no more new 2xx responses are expected to arrive." Downstream proxies do send CANCELs on remaining proxy branches after receiving first 2xx (but there is a race there and another 2xx may sneak through) and UACs MAY send BYEs but *only* to established dialogs not early. You do not do anything with early dialogs until 64*T1 after first 2xx and then just destroy them without any signaling. - Nasir Discuss SIP Servlets at http://groups.google.com/group/sipservlets/ On 6/6/07, Ivar <[EMAIL PROTECTED]> wrote: > > > >When the forking proxy forwards the 2xx, it will CANCEL all other active > >dialogs. > Yep, but it forwarded multiple provisional responses what caused multiple > early dialogs at UA. > > UA1 > <- proxy 180 Ringing <---- <--------- UA 2 > proxy > > <- proxy 180 Ringing <---- <--------- UA 3 > > At his momenet UA1 > UA1 > <- proxy 200 ok <---- <--------- UA2 > > Proxy will take care of UA 3, thats ok > > UA1 > Dialog 1, confirmed - from UA2 > Dialog 2, early - from UA3 > > or am i missing something. > > > > > Christer Holmberg (JO/LMF) wrote: > > Hi, > > > > > >> UA1 may create multiple dialogs if proxy forks > >> Dialog1(early) > >> Dialog2(early) > >> --> both share same client transaction > >> > >> Now Dialog 1 gets 2xx ok, and client transaction completes. > >> > >> Dialog2(still early) must be shut down ???? Nothing to > >> cancel, Doesn't it need BYE request ? > >> > > > > No. > > > > When the forking proxy forwards the 2xx, it will CANCEL all other active > > dialogs. > > > > The UAC MAY receive additional 2xx responses, and in that case it should > > ACK and BYE, but otherwise it doesn't need to do anything. > > > > Regards, > > > > Christer > > > > > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
