Hello all, There was yet-another bug of brown paper-bag variety in the way CANCELed INVITE transactions were handled. Looks like they were not timed out properly but restarted and restarted over again in certain scenarios.
When fixing that I also improved the timer C behaved (now CANCELing INVITE transactions that have not received a peep from server for 3 minutes) and also the way nta_outgoing_tagged() aka forked INVITE transactions behave. Quoting from RELEASE: - Timing out CANCELed INVITE client transactions is now done with timer D. Previously, the INVITE client transactions were restarted instead of timing out under certain circumstances. - An INVITE transaction that has been timed out with stack timer C is now CANCELed automatically. Previously, such the INVITE client transactions were restarted instead of timing out under certain circumstances. - Timing out forked INVITE client transactions is now done by stack. The stack generates a 408 response to each INVITE transaction fork that has not received a final response within 32 seconds (or 64 times SIP T1) after first final response to the INVITE was received. While I added some testing to check_nua and started writing check-based test cases for nta, too, it is likely that there are still some problems (especially related to handling of 100rel responses, PRACK and all that jazz). As usual, be vigilant and report any irregularities to the list... -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel