For what it is worth... As indicated within rfc3261 figure 5, the 100 response places the transaction in progressing state (similar to other 101-198 responses).
Concerning Timer C (or similar expiration timer) not being shown within figure 5, the following is a link to Jonathan's answer. http://bugs.sipit.net/show_bug.cgi?id=706 > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of M. Ranganathan > Sent: Monday, July 12, 2010 1:56 PM > To: WORLEY, Dale R (Dale) > Cc: sip-implementors > Subject: Re: [Sip-implementors] How long can a Dialog be in Early > state. <snip> > 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 _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
