[asterisk-bugs] [Asterisk 0011231]: [patch] Many retransmits when chan_sip generates multiple outstanding requests

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11231 
====================================================================== 
Reported By:                flefoll
Assigned To:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   11231
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 89184 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2007-11-13 08:08 CST
Last Modified:              2008-10-23 01:56 CDT
====================================================================== 
Summary:                    [patch] Many retransmits when chan_sip generates
multiple outstanding requests
Description: 
I opened issue 10946 in october http://bugs.digium.com/view.php?id=10946 on
the same subject, but it was closed last week, together with issue 9567 and
issue 10915 (sorry, I was away last week).

All 3 issues were closed when chan_skip rev 89097 was committed. This
revision adds support for one outgoing transaction with the new
"lastnoninvite" field.

So, I have given a try to modification brought by chan_skip rev 89097. But
it does not solve the retransmit problem for me.

Typically, try with a series of SendText(ABC) in your extensions.conf :
the SIP peer will never respond quickly enough, and all (except last)
MESSAGE messages will be retransmitted. Silly test, but easy to reproduce
!
The problem also most probably still occurs when REFER handling provokes
too many and too quick NOTIFY messages (not re-tried yet, but new
"lastnoninvite" can handle one NOTIFY only).

Consequently, I propose another patch : this one won't remove code :-) but
it will add a few more lines instead, in order to cancel retransmits when
chan_sip receives a "late" response.

I know, it does not respond to file's dream of "a chan_sip with real
transaction support" :-)

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0010915 Problems when doing an attended and una...
related to          0010052 NOTIFY race condition when state change...
====================================================================== 

---------------------------------------------------------------------- 
 (0094184) flefoll (reporter) - 2008-10-23 01:56
 http://bugs.digium.com/view.php?id=11231#c94184 
---------------------------------------------------------------------- 
As described in 2008-02-04 note, I tested the patch for NOTIFY after REFER
and, with a few modifications (explained in the note), it worked. But it
only addresses NOTIFY after REFER scenarios, while retransmission problem
is more general.

As far as I'm concerned, I still use the patch I proposed in Nov. 2007,
that handles "late" responses in order to cancel retransmission mechanism. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-23 01:56 flefoll        Note Added: 0094184                          
======================================================================