-Natraj -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nagaraj S Sent: Thursday, July 29, 2004 2:32 PM To: [EMAIL PROTECTED] Subject: Re: [Sip-implementors] Some doubt on timers in transaction
Natraj wrote, 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... I guess the INVITE-Client Transaction section describes about this topic in detail... > Dear Natraj, in the RFC 3261, it is mentioned that after sending a INVITE, Tb(= 64*T1) is started and the transaction will be in CALLING state, in this state if the timer Tb fires, it is treated as a REQUEST TIMEOUT and the transaction moved to TERMINATED state... but if a provisional response (101 to 199 ) is recevied in CALLING state, then as per the RFC the transaction is moved to PROCEEDING state, in this state it is not mentioned about the action to be taken if Tb fires for a UA. Is there any standard way to handle the scenario..? I am just repeating the doubt of KrishnaKanth.. [ABN] OK It's not been mentioned how to handle Tb expiration in call proceeding state fine. That is fine we can do the same thing what all other processing done in case of calling state... in this case the timers in server side do the similar (that of client side ) to release the resources allocated for INVITE server transaction... because client can't think of canceling the transaction even after the transaction timeout... Probably this would have mentioned in RFC.... (But still we can infer in this way...) --- Rgds Nagaraj S ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, July 29, 2004 1:26 PM Subject: RE: [Sip-implementors] Some doubt on timers in transaction > > -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... > > I guess the INVITE-Client Transaction section describes about this topic > in detail... > > 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
