[SIPForum-discussion] UAC - INVITE Transaction Timeout Timer

sreekant nair sreekant_nair at yahoo.com
Fri Jun 19 13:45:29 UTC 2009

Thanks Tomasz,

Rely on the user to hang up thereby sending a CANCEL to the far end - interesting. So does your statement imply that on receiving a provisional response, we must STOP TIMER B? 

A related query - Any idea how the "session-expires" header works in conjunction with this scenario? The client I use supports this header and uses a default value of 1800 seconds. Does that mean the SIP stack starts another timer for 30mins and hypothetically if the user never ends the call, should this tear down the transaction? Or is this timer only started for Confirmed Dialogs?

Thanks again. 

From: Tomasz Zieleniewski <tzieleniewski at gmail.com>
To: sreekant nair <sreekant_nair at yahoo.com>
Cc: discussion at sipforum.org
Sent: Friday, June 19, 2009 8:50:50 AM
Subject: Re: [SIPForum-discussion] UAC - INVITE Transaction Timeout Timer


Timer B is only relevant while transaction is in the initial "calling" state.
It is used both for reliable and unreliable transports.
When transaction moves to "proceeding" state as it receives 
a provisional response, it is completely up to UAC what to do then.
You can compare it to the situation when You call someone 
and You hear never ending ringing in the phone.
Probably You will eventually give up and hang up.
The same thing happens here, UAC hang up by sending
a CANCEL which cancels the transaction.

Kind regards,
- Tomasz Zieleniewski  

2009/6/18 sreekant nair <sreekant_nair at yahoo.com>

>Hi Everyone,
>Have a query regarding Timers. 
>If a client sends an INVITE and receives a provisional response but does NOT get a Final Response, is there a Timer that clears up the transaction?
>RFC3261 specifies Timer B as the INVITE Transaction Timeout Timer. However in the state transition diagram, there is no mention of whether Timer B is stopped,restarted on moving from the "CALLING" state to the "PROCEEDING" state on receiving a 1xx message. These are my specific queries:
>	1. If while in "PROCEEDING" state no final response is received, what happens?
>	2. Is it implied that Timer B is only stopped/canceled on receiving a final response? 
>	3. What happens when Timer B fires?
> Should the client send a CANCEL or just kill the transaction?Thanks for any inputs in this regard.
>Sreekant Nair
>>This is the SIP Forum discussion mailing list
>>TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
>>Post to the list at discussion at sipforum.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20090619/d60f0158/attachment-0002.html>

More information about the discussion mailing list