inline. [EMAIL PROTECTED] wrote: > > Hi, > I am reposting my query. Hoping to receive a response atleast this time. > > Section 16.6 bullet 11 > > "In order to handle the case where an INVITE request never generates a > final response, the TU uses a timer which is called timer C. Timer C > MUST be set for each client transaction when an INVITE request is > proxied. > The timer MUST be larger than 3 minutes. Section 16.7 bullet 2 > discusses how this timer is updated with provisional responses, and > Section > 16.8 discusses processing when it fires." > > >From this it is clear that Timer C should be started when request is > proxied. > > what is the use of Timer B in Proxies?? Because default value of Timer B > seems to 64*T1 whereas minimum value of Timer C should be 3 minutes. > > Starting Timer C after receiving the first 1xx response and refreshing > it > on subsequent provisional responses (non-100) sounds fine. This is the > behaviour given in bis-05. Why has this been changed in bis-09.
Practically speaking there is no difference between starting it on the 1xx or on the request. However, since timer C is not part of the transaction layer any more, it made it easier to describe it as being done when the request is sent. -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 [EMAIL PROTECTED] FAX: (973) 952-5050 http://www.jdrosen.net PH: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
