The UAC and UAS can act however they want. However it would be wise to not implement the annoy-the-neighbor feature and ring forever when no CANCEL is received.
> -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of M. Ranganathan > Sent: Tuesday, March 20, 2012 12:40 PM > To: [email protected] > Subject: [Sip-implementors] Does Dialog Lifetime affect dialog creating > transaction lifetime? > > Consider the following two scenarios: > > Scenario 1 > ========= > Invite Client Transaction sent by UAc creates a Dialog. > - Sends INVITE > - Server side sends RINGING periodically once every 30 seconds for > ever. > > Dialog remains in early state for 3 minutes and times out. > > What happens to the INVITE Client Transaction ? Should the SIP stack > automatically terminate it? > > Scenario 2 > ========= > Invite Server transaction gets INIVTE. > Application creates a dialog. > Application keeps sending 180 periodically once every 30 seconds for > ever. > Server Dialog times out after 3 minutes in early state. > What should the SIP stack do with the invite Server Transaction? > Should it be automatically deleted after the Dialog times out? > > Thanks > > 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
