Right, for early dialog for no-response, 4xx, 5xx or 6xx one can terminate the dialog. For confirmed dialog no-response, 408 and 481 will triger the dialog termination.
Kamal Cisco, Bangalore India -----Original Message----- From: Avasarala Ranjit-A20990 [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2008 11:41 AM To: Kamalakanta Palei (kpalei); Bartosz Baranowski; [email protected]; M. Ranganathan Subject: RE: [Sip-implementors] In dialog error response I think not receiving any response will trigger a timeout and automatic dialog termination. But for a 4xx, an explicit dialog termination needs to be initiated by the UAC. Regards Ranjit -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kamalakanta Palei (kpalei) Sent: Friday, September 26, 2008 6:01 AM To: Bartosz Baranowski; [email protected]; M. Ranganathan Subject: Re: [Sip-implementors] In dialog error response If you receive response 408, 481 or no response then initiate dialog termination. Other than above cases you need not to close the dialog necessarily, though it is implementation dependent. If dialog was created by INVITE, dialog termination starts with sending BYE to remote side. Kamal Cisco, Bangalore India -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bartosz Baranowski Sent: Thursday, September 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: 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 _______________________________________________ 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
