Hi Thanks for such quick answer. On Thu, Sep 25, 2008 at 3:40 PM, Somesh S. Shanbhag <[EMAIL PROTECTED] > wrote:
> Comments inline with [SSS] > > Somesh S Shanbhag > M G L Bangalore > > > > -----Original Message----- > From: [EMAIL PROTECTED] on behalf of Bartosz > Baranowski > Sent: Thu 9/25/2008 7:08 PM > To: [email protected]; M. Ranganathan > Subject: [Sip-implementors] In dialog error response > > Hi Im facing some doubts about sip implementation we use. Didnt find that > on mailing list and google so... > According to rfc non final 2xx response termiantes dialog if its in early > state. > What is desired behaviour for in dialog response to request? > For instance: > > UAC UAS > | ----- INVITE -----> | > | <-------- 100 ------- | > | <-------- 180 ------- | > | <-------- 200 ------- | > | ----- ACK --------> | > | ----- INFO -------> | > | <-------- 500 -------- | > > > After sending 500 UAS should not receive DialogTerminated event, should > it? > This is what is in rfc, maybe I missed some vital part: > > [SSS] > The 500 Error is for INFO and the Dialog doesn't terminate. > Only that the INFO(example: DTMF) didn't serve the purpose. > To terminate the established dialog, send BYE > Even if the mid-dialog INVITE fails, it resumes to earlier > what has been exchanged. > [/SSS] > > > A dialog can also be in the "early" > state, which occurs when it is created with a provisional response, > and then transition to the "confirmed" state when a 2xx final > response arrives. For other responses, or if no response arrives at > all on that dialog, the early dialog terminates. > > > > 13.2.2.3 4xx, 5xx and 6xx Responses > > A single non-2xx final response may be received for the INVITE. 4xx, > 5xx and 6xx responses may contain a Contact header field value > indicating the location where additional information about the error > can be found. Subsequent final responses (which would only arrive > under error conditions) MUST be ignored. > > All early dialogs are considered terminated upon reception of the > non-2xx final response. > > -- > Bartosz Baranowski > JBoss R & D > ================================== > Word of criticism meant to improve is always step forward. > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > ------------------------------ > EMAIL DISCLAIMER : This email and any files transmitted with it are > confidential and intended solely for the use of the individual or entity to > whom they are addressed. Any unauthorised distribution or copying is > strictly prohibited. If you receive this transmission in error, please > notify the sender by reply email and then destroy the message. Opinions, > conclusions and other information in this message that do not relate to > official business of Mascon shall be understood to be neither given nor > endorsed by Mascon. Any information contained in this email, when addressed > to Mascon clients is subject to the terms and conditions in governing client > contract. > > Whilst Mascon takes steps to prevent the transmission of viruses via > e-mail, we can not guarantee that any email or attachment is free from > computer viruses and you are strongly advised to undertake your own > anti-virus precautions. Mascon grants no warranties regarding performance, > use or quality of any e-mail or attachment and undertakes no liability for > loss or damage, howsoever caused. > > -- Bartosz Baranowski JBoss R & D ================================== Word of criticism meant to improve is always step forward. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
