The expires header is used to refresh a created dialog ( sending another INVITE or UPDATE)
In this case INVITE/100 and UAC dies, all provisioning response are not mandatory , then you can clean the context after the answer-timeout ( 90 seconds). Regards! Valdemar -----Original Message----- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of ext WORLEY, Dale R (Dale) Sent: Monday, July 12, 2010 1:50 PM To: M. Ranganathan Cc: sip-implementors Subject: Re: [Sip-implementors] How long can a Dialog be in Early state. ________________________________________ From: M. Ranganathan [mra...@gmail.com] 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. _____________________________________ I'm not sure of the chapter and verse, but I'm sure that the referenced section of 3261 also permits a UAC or proxy to give up on an INVITE if only 100 responses are received for 3 minutes. Similarly, it can enforce any Expires that was present in the outgoing INVITE. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
