Perhaps the right fix for this would be as follows - 1. Invite Server Transaction (IST) enters "Finished" state (instead of Terminated) after sending 2xx from TU and sets a Timer equal to T4. On its expiry IST transitions to Terminated. (Note T4 and not 64*T1 as it is the time in the network to clear any retransmissions).
2. On receipt of INVITE retransmission in "Finished" state the IST sends the request up to TU which retransmits the 2xx response and resets the 2xx retransmission timer back to T1 and overall timeout back to 64*T1. Thanks Nasir Discuss SIP Servlets at http://groups.google.com/group/sipservlets/ > > From: Ivar <[EMAIL PROTECTED]> > Date: May 31, 2007 8:34 AM > Subject: Re: [Sip-implementors] Comments about: > http://bugs.sipit.net/show_bug.cgi?id=769 > To: [EMAIL PROTECTED] > Cc: [email protected] > > > Probably it's right to do, linger in terminated state for 64 * T1, then > all kind of retransmissions must be completed. > > That seems to be good for PRACK too if server transaction live. UAS must > wait 64 * T1 for PRACK and do response mapping (even if terminated), if > transaction exists no duplicate copy of responses needed, must think a > little ... > > > [EMAIL PROTECTED] wrote: > > OpenSIPStack, for one, implements the bug fix. > > > > Joegen > > > > Ivar wrote: > >> hi, > >> > >> > >> How many implementations really do it or consider doing it so ? > >> > >> http://bugs.sipit.net/show_bug.cgi?id=769 > >> _______________________________________________ > >> 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 > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
