-----Original Message-----
From: Krishna Kanth T [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 29, 2004 2:18 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Nataraju Alilaghatta (WT01 -
TELECOM & INTER-NETWORKING SOLUTIONS)
Subject: Re: [Sip-implementors] Some doubt on timers in transaction



hi mukul,



So you say that the Timer C by proxy or user defined timer in case of
end

point should be started by TU and not by client transaction. Please
correct

me if i am wrong.



[ABN] Yes the TimerC started by proxies and similar functionality is
been done by Tb for INVITE client transaction...



There is a similar timer (TimerF) for non-invite client transaction
also...



Rgds

 Krishna

----- Original Message -----

From: "Mukul Purohit" <[EMAIL PROTECTED]>

To: <[EMAIL PROTECTED]>

Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>

Sent: Thursday, July 29, 2004 1:59 PM

Subject: Re: [Sip-implementors] Some doubt on timers in transaction





>

>

> [EMAIL PROTECTED] wrote:

> > -Natraj

> >

> > -----Original Message-----

> > From: [EMAIL PROTECTED]

> > [mailto:[EMAIL PROTECTED] On Behalf Of
Krishna

> > Kanth T

> > Sent: Thursday, July 29, 2004 12:07 PM

> > To: [EMAIL PROTECTED]

> > Subject: [Sip-implementors] Some doubt on timers in transaction

> >

> > Hi,

> >

> > I have one basic doubt in timers in UAC transaction. When a UAC

> > transaction sends an INVITE request and gets a provisional response
it

> > enters a "Proceeding" state. Here rfc3261 says that for a proxy it

> > should restart TIMER C. But however for an endpoint, it does not say

> > anything about whether a timer has to be restarted or not and also
does

> > not say about the value of the timer. So i am assuming that the
endpoint

> > can start a timer of its choice. Now when this timer times out or
when

> > TIMER C times out (and proxy does not want to restart this timer),

> > should we change the transaction state to "TERMINATED" or should we

> > still remain in "PROCEEDING" state?

> >

> > [ABN] when provisional response received the retrans timer will be

> > stopped (Ta). When INVITE sent out the Tb (= 64*T1) also would have
been

> > started which will take care of transaction termination. When Tb
fires

> > the transaction moves to TERMINATED state...

> Tb is not for this purpose. It controls the transaction timeouts i.e.

> when there is no response at all from the other side.

>

> When in proceeding state, the termination of transaction if no further

> response is received, is signalled by TU. TU can start a timer, or it

> can wait for the user( probably human) response. This is beacause a

> timer should handle machine controlled responses, and not the
responses

> (like 200,486 etc) which are dependent on human interaction.

>

> >

> > I guess the INVITE-Client Transaction section describes about this
topic

> > in detail...

> It is not mentioned.

>

> >

> > Rgds

> >  Krishna

> > _______________________________________________

> > Sip-implementors mailing list

> > [EMAIL PROTECTED]

> > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

> >

> >

> >

> >

> > Confidentiality Notice

> >

> > The information contained in this electronic message and any
attachments

to this message are intended

> > for the exclusive use of the addressee(s) and may contain
confidential

or privileged information. If

> > you are not the intended recipient, please notify the sender at
Wipro or

[EMAIL PROTECTED] immediately

> > and destroy all copies of this message and any attachments.

> >

> > _______________________________________________

> > Sip-implementors mailing list

> > [EMAIL PROTECTED]

> > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

> >

> >

>

>








Confidentiality Notice

The information contained in this electronic message and any attachments to this 
message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged 
information. If
you are not the intended recipient, please notify the sender at Wipro or [EMAIL 
PROTECTED] immediately
and destroy all copies of this message and any attachments.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to