Sorry about the resend... I think that I may have misunderstood aspects of your questions (and likely still do). :)
> > 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. If dialog timeout was because of Session-Expires, see RFC 4028. > > What happens to the INVITE Client Transaction ? If the UAC gives up on the transaction, it sends CANCEL. If it gives up only on the early dialog, it can send BYE. > > Should the SIP stack automatically terminate it? Not unless it also wants to cancel the INVITE. > > 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? It should complete the transaction (unless a reason to otherwise). For instance, it can reply with 408 or 199. > > Should it be automatically deleted after the Dialog times out? No; however since I'm not positive about which aspect you are asking... see RFC 3261 figure 7 and letter timers. I don't recall if RFC 6026 would be relevant to your question. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
