It is my understanding Timer C is only relevant to a Proxy server. I am interested in what the UAC should be doing under the following circumstances:
UAC sends INVITE UAS/Proxy sends 1xx UAS/Proxy dies. I think Hanifa Mohammed pointed me to the right section here (i.e. section 20.19 ). The Expires header tells the Stack what to to do. Thanks Ranga On Sat, Jul 10, 2010 at 12:25 PM, Brett Tate <[email protected]> wrote: > See RFC 3261's use of Timer C. > >> -----Original Message----- >> From: [email protected] [mailto:sip- >> [email protected]] On Behalf Of M. Ranganathan >> Sent: Friday, July 09, 2010 10:51 PM >> To: sip-implementors >> Subject: [Sip-implementors] How long can a Dialog be in Early state. >> >> Consider the following scenario : >> >> UAC sends INVITE, receives 1xx response and creates a Dialog which is >> now in Early state. >> >> UAS dies and no final response is received. >> >> Client Transaction is stuck in Proceeding state and Dialog is stuck in >> early state. >> >> I would like to generate a timeout alert at this point so that the >> application can be alerted that the UAS died and hence it should >> perform cleanup. What is the recommended timeout period for this? In >> other words what is the max time for which the Dialog can remain in >> Early state? >> >> Ranga. >> >> >> >> -- >> M. Ranganathan >> _______________________________________________ >> Sip-implementors mailing list >> [email protected] >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > -- M. Ranganathan _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
