It is not necessary for a UAC to cleanup other early dialogs (i.e. send BYEs) when it receives a 2xx. The forking proxy would have issued a CANCEL to all the other UASs in attempt to prevent them from completing the INVITE. Those UAS's would send a 487 response to the INVITE which would stop at the forking proxy. Any BYEs to those UASes would likely get a 481 response.
If any of the early dialogs were not successfully terminated, the UAC would see a 2xx, which it could BYE at that time. Sending a BYE on other early dialogs would only inject unnecessary messages into the network. cheers, (-:bob Robert F. Penfield Chief Software Architect Acme Packet, Inc. 71 Third Avenue Burlington, MA 01803 [EMAIL PROTECTED] ----- Original Message ----- From: "Manjunath Warad" <[EMAIL PROTECTED]> To: "'Sigrid Thijs'" <[EMAIL PROTECTED]>; <[email protected]> Sent: Tuesday, April 04, 2006 7:50 AM Subject: Re: [Sip-implementors] Forking: early dialog termination > Hi, > I am really sorry, I took the question in a different meaning. > > Since a UAC can potentially reach multiple hosts using the same INVITE and > therefore multiple calls can be created. Which one it accepts and which > ones > it dosen't is its own decision. If early dialogs are created and a 2xx is > received on one of them, then the UAC > > (1) Can wait for an implementation defined "Ringing Timer" (the time it > allows the terminal to ring after getting a 1xx). Maybe 64*T1 for 2xx > responses on other dialogs, in case it decides not to finalize the dialog > on > which the 2xx was first received. > > (2) Can terminate the Dialog immediately after getting a 2xx by sending a > BYE implying the first 2xx received was finalized. > > Either ways, I feel the UAC SHOULD send a BYE to clean up the Peer Network > early dialogs gracefully which have nbot been responded at the time of > making the cleanup decision. > > Rgds, > Manju > > > **************************************************************************** > *********** > > > This e-mail and attachments contain confidential information > from HUAWEI, which is intended only for the person or entity whose address > is listed above. Any use of the information contained herein in any way > (including, but not limited to, total or partial disclosure, reproduction, > or dissemination) by persons other than the intended recipient's) is > prohibited. If you receive this e-mail in error, please notify the sender > by > phone or email immediately and delete it! > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sigrid > Thijs > Sent: Tuesday, April 04, 2006 3:53 PM > To: [email protected] > Subject: [Sip-implementors] Forking: early dialog termination > > > Hi, > > I'm sorry if this has been asked before, but I haven't found a real > answer to this question. > According to RFC 3261: > > If the forwarded response was a final response, the proxy MUST > generate a CANCEL request for all pending client transactions > associated with this response context. > > What is the desired behavior for the UAC? > - non-2xx response: all early dialogs are considered terminated > - 2xx response: early dialogs are terminated 64*T1 seconds after the > reception of the first 2xx response > > Does the UAC need to terminate these early dialogs by sending a BYE > request, or should it just discard the early dialogs? > > -- > kind regards, > Sigrid Thijs > _______________________________________________ > 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 > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
