[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    RE: [Sip-implementors] Timeout after INVITE provisional response
From:       "Brett Tate" <brett () broadsoft ! com>
Date:       2003-05-15 20:07:33
Message-ID: 000701c31b1d$a0155520$2b01a8c0 () broadsoft ! com
[Download RAW message or body]

> Is there any way to time out once the 
> client has received a provisional response?

Yes.  RFC 3261 sections 13.3.1.1, 16.6, and 16.7
discuss the usage of timer C.
  
> Should the client wait forever?

The client can if it wants.  RFC 2543 did not make
use of timer C (periodic 1xx).  Prior to RFC 3261
and RFC 3311, some vendors used requests like the
the INFO to traverse a potentially active 
dialog to see if it resulted in a 481.  RFC 3261 
now provides the period 1xx mechanism.
  
> What if no final response is ever received?

It is up to uac to decide.

> Is the RFC assuming the user (or TU) would 
> eventually give up and hang up on the call?

Sometimes yes.  The owner of the UAS likely
does not want there phone to ring forever even 
if the UAC is willing to wait forever for a
final response.  However since someone might
think that this is a neat service or someone
is actually using the 182 response, the rfc 
does not limit how long a call can remain in 
an early dialog state.

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic