Bartosz,
You seem to be ignoring the distinction between 'dialog' and 'dialog
usage' which is clarified in 5057. Most of the things you mention below
terminate the dialog usage. Especially for *early* dialogs its
*generally* the case that the dialog will go away at the same time.
There are potential obscure cases when this isn't true. (If you start an
INVITE, and before it completes you send a subscribe in the same dialog,
then if the invite fails the dialog may still survive until the
subscribe usage ends.)
Most implementors will never get in a situation where this can come up.
But when writing about these things it is good to be careful about the
language, by using dialog usage when that is the pertinent term.
Thanks,
Paul
Bartosz Baranowski wrote:
> What I understood from 5057 and 3261:
>
> When stack receives 300+ response and dialog is in EARLY state - it is
> terminated.
> When stack receives:
> - for INVITE dialog one of (and message is: INVITE, UPDATe, PRACK, INFO,
> BYE):
> 405, 480, 481, 489, 501, 404, 410 ,416, 482, 483, 484, 485, 502 or
> 604 (and 200 for BYE)
> for SUBSCRIBE - 200 depending on message/type and
> 405, 480, 481, 489, 501 - if there is only one usage
> 404, 410 ,416, 482, 483, 484, 485, 502 or 604 - always
>
> By dialog is terminated I mean it moves to TERMINATED state when it
> receives/sends resposes with code above, am I right?
> On Fri, Sep 26, 2008 at 8:11 AM, Avasarala Ranjit-A20990 <
> [EMAIL PROTECTED]> wrote:
>
>> 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; sip-implementors@lists.cs.columbia.edu; 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: sip-implementors@lists.cs.columbia.edu; 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
>> Sip-implementors@lists.cs.columbia.edu
>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>>
>> _______________________________________________
>> Sip-implementors mailing list
>> Sip-implementors@lists.cs.columbia.edu
>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>>
>
>
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
