> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, November 18, 2001 11:28 PM
> To: 'Thiagarajan Venkatachalam'; '[EMAIL PROTECTED]'
> Subject: [Sip-implementors] Timer logic in bis-05
>
>
>
>
> Hi All,
>
> This relates to the chapter 17 of bis-05.
>
> For INVITE client Transactions we have a timer D that times out in T3
> seconds for unreliable transports.
> This is the total amount of time that the server transaction
> can remain in
> the "completed " state when unreliable transports are used.
>
> For Non-Invite client transactions we have a timer F that
> also times out in
> T3 seconds. Timer F is for determining at which point
> retransmissions of
> the non-INVITE requests stop.
>
> The functionality of the timer F is different from the timer
> D, however
> both time out at T3. Is there any specific reason for having
> both these
> timers time out at "T3"?
This was what what the timers were previously. It simply provided a
reasonably consistent timeout value.
>
> Do we need to use a common variable varT3 in our implementations?
Timer D and timer F need not have the same value. They merely share the same
default.
-Jonathan R.
---
Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PHONE: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
