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

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Oct 12 20:35:18 CDT 2010


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-10-12 20:35 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0127923) zerohalo (reporter) - 2010-10-12 20:35
 https://issues.asterisk.org/view.php?id=16382#c127923 
---------------------------------------------------------------------- 
jpeeler: I immediately get a segfault upon load:

Program terminated with signal 11, Segmentation fault.
https://issues.asterisk.org/view.php?id=0  0x00f3c3a9 in
__ast_pthread_mutex_lock (filename=0xf99bf4
"chan_sip.c", lineno=8598, func=0xf9f5bc "sip_poke_peer_s", 
    mutex_name=0xf9f5cc "&(foundpeer)->_lock", t=0x5c) at
/usr/src/asterisk/asterisk-1.4.37-rc1/include/asterisk/lock.h:360
360             int canlog = strcmp(filename, "logger.c") & t->track;

do you need full backtrace on this? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-12 20:35 zerohalo       Note Added: 0127923                          
======================================================================




More information about the asterisk-bugs mailing list