[asterisk-bugs] [Asterisk 0016382]: [patch] SIP OPTIONS qualify message forever

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16382 
====================================================================== 
Reported By:                lftsy
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   16382
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Target Version:             1.4.38
Asterisk Version:           SVN 
JIRA:                       SWP-478 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-12-03 10:04 CST
Last Modified:              2010-11-02 15:48 CDT
====================================================================== 
Summary:                    [patch] SIP OPTIONS qualify message forever
Description: 
Hello, I have a trouble with different Asterisk versions (1.4.26, 1.4.27,
1.4.27.1). When I use the steps below, Asterisk starts to send SIP OPTIONS
to the previous IP/port used by a SIP realtime peer (that has been pruned)
and will keep trying to send SIP OPTIONS pings forever, event if the peer
is connected with a new IP/port address.

I have just checked with my old Asterisk 1.2.27 with the same sip.conf and
I do not have the problem, the SIP OPTIONS stops once register timer has
expired.

During my experience to reproduce the bug, I have been able to have 10
IP/port currently pinged by the Asterisk server for one single peer.
And the only way to stop it is to restart Asterisk...

Thank you for your attention!
Marc Leurent
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0016764 Sip Channels Colapse
related to          0015716 [patch] chan_sip fails to destroy chann...
related to          0015627 [patch] Asterisk runs out of sockets
related to          0017643 [patch] dialplan reload deadlocks in as...
related to          0017779 [patch] tcptls.c:350 Unable to connect ...
====================================================================== 

---------------------------------------------------------------------- 
 (0128572) jpeeler (administrator) - 2010-11-02 15:48
 https://issues.asterisk.org/view.php?id=16382#c128572 
---------------------------------------------------------------------- 
Upon further examination the rtautoclear option does work properly, and
really the value shouldn't ever be set to 0. I'm not sure how you hard
coded it, but setting it to "no" should work. Hard coding rtautoclear to 0
would cause registrations to expire prematurely, which I think is related
to the problem. So results from the hard coding removed and rtautoclear on
(and off actually) would be appreciated. Leaving rtautoclear on should make
the problem happen faster so definitely test that first. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-02 15:48 jpeeler        Note Added: 0128572                          
======================================================================