Hi Sachin,
Quoting from the bis09:-
16.8 Processing Timer C
******************************
If timer C should fire, the proxy ** MUST either reset the timer with any
value it chooses, or terminate the
client transaction**. If the client transaction has received a provisional
response, the proxy MUST generate a
CANCEL request matching that transaction. If the client transaction has not
received a provisional response,
the proxy MUST behave as if the transaction received a 408 (Request
Timeout) response.
Allowing the proxy to reset the timer allows the proxy to dynamically
extend the transaction
�s lifetime
based on current conditions (such as utilization) when the timer fires.
Regarding your question of restarting the TimerC , I feel that the bis
mandates it if the proxy is sending out a
CANCEL. So a proxy MUST restart the TimerC in case the proxy sends a
CANCEL.
-Regards
R.Kamath
Sachin Shenoy <[EMAIL PROTECTED]> on 07/28/2002 08:46:05 PM
To: [EMAIL PROTECTED]
cc: (bcc: P Raghavendra Kamath/HSSBLR)
Subject: [Sip-implementors] Timer C
Hi,
At Proxy, Consider a state where we have recieved 1xx for an
INVITE that we sent out
If now, Timer C fires,
1. Do we send out CANCEL and consider the INVITE as timed-out.
or
2. Do we send out CANCEL and wait for a proper response for the INVITE.
If it is (2), then would'nt it be better to restart timer C, after sending
out
CANCEL. This is to ensure that we do clearup if INVITE is not responded
anymore.
(If the end-point which sent the 1xx crashed, it is not going to send us
any response. Sending CANCEL to it and waiting is not going to help.)
Hope I didn't miss anything over here?
Thanks
Sachin
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
