-Natraj
-----Original Message----- From: Vivek Srivastava (WT01 - TELECOM & INTER-NETWORKING SOLUTIONS) Sent: Thursday, July 29, 2004 3:35 PM To: [EMAIL PROTECTED]; Nataraju Alilaghatta (WT01 - TELECOM & INTER-NETWORKING SOLUTIONS) Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [Sip-implementors] Some doubt on timers in transaction Hi Nataraju, Timer Ta is started for retransmission and Tb is started for Transaction. If Client transaction is in "calling" state and Ta expires, INVITE is retransmitted[ABN] . If Client transaction is in "calling" state and Tb expires, state is changed to ?Terminated? state. If client transaction receives Provisional response, state is changed to ?proceeding? state and Ta is stopped. But Tb is still running and it should run because transaction still exists. Rfc does not talk about the expiration of Tb when client transaction is in ?Proceeding state?. What will happen if client transaction is in ?Proceeding ?state and no final response is sent by Server? [ABN] It's intuitive that timer Tb will be running till the transaction receives final response.... Yes it's not been explicitly told about the TimerB handling in proceeding state. I perceive it as to to be running even when its in PROCEEDING state... when Tb expires in proceeding state it should move to COMPLETED state (as if 408 received from Network...) and proceed further as described in sec 17.1.1.2 Formal Description of Rfc3261. Vivek -----Original Message----- From: [EMAIL PROTECTED] on behalf of Mukul Purohit Sent: Thu 7/29/2004 1:59 PM To: Nataraju Alilaghatta (WT01 - TELECOM & INTER-NETWORKING SOLUTIONS) Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] 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 > > _______________________________________________ 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
