On Mon, Jul 12, 2010 at 1:12 PM, WORLEY, Dale R (Dale) <[email protected]> wrote: > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of M. Ranganathan > [[email protected]] > > 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? > _______________________________________________ > > There is no time limit for the UAS to maintain an early dialog, but it is > requried to send a provisional response every 60 seconds. If the UAC does > not see a provisional response for 180 seconds, it can tear down the dialog. > (See section 13.3.1.1.) > > Dale > ----------------------------------------------------------------------
Does a 100 provisional response put the UAC dialog in early state? I think not so my question was mis stated. The situation I was concerned about is UAC sends INVITE UAS sends 100 and dies. In this case Dialog cleanup is not an issue because a Dialog does not yet exist. Transaction will expire when its Expires indicated value header times out.. So that will take care of cleanup of the transaction. As for Dialog state machine, 101 -- 199 responses can push the dialog into early state and as you state above, this must be refreshed every 60 seconds and hence a UAC dialog can be torn down if in early state for > 3 minutes without a 1xx refresh. Ranga -- M. Ranganathan _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
