[asterisk-bugs] [Asterisk 0016115]: Lockup in chan_sip

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16115 
====================================================================== 
Reported By:                fmarie
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16115
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.0-rc3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-22 21:20 CDT
Last Modified:              2009-10-23 11:29 CDT
====================================================================== 
Summary:                    Lockup in chan_sip
Description: 
Hello.

We are using Asterisk 1.6.2.0-rc3 on openSUSE 11.1 mainly for call
recording, fax and IVR. Asterisk is connected to a softswitch as a SIP
peer, the softswitch is connected to the PSTN via SS7 and to MGCP and SIP
phones.

Asterisk is locking up randomly. The console works, but no more SIP
traffic is accepted. This started when we switched (because of fax
problems) from 1.6.1.6 to 1.6.2.0-rc2. At first, it happened about once a
week but has progressed to once-twice per day. No improvement after
upgrading to 1.6.2.0-rc3. Restarting Asterisk via /etc/init.d/asterisk
script helps (until the next lockup).

The last message in the log (set to verbose) before the lockup is
something like
chan_sip.c: Maximum retries exceeded on transmission
23150-AQ-002ecd38-506161c24 at localdomain.com for seqno 2554278 (Critical
Response) -- See doc/sip-retransmit.txt.
However, we have also seen this message without a lockup following.

I attached the output of "core show locks". I will also attach sip debug
output as soon as I get it. What else should I do to help debug this
problem?

Also, until a better solution, is there a way to monitor Asterisk for this
kind of lockup and restart it?

Thanks,

Marie Fischer
====================================================================== 

---------------------------------------------------------------------- 
 (0112667) manuel_wenger (reporter) - 2009-10-23 11:29
 https://issues.asterisk.org/view.php?id=16115#c112667 
---------------------------------------------------------------------- 
We have the exact same problem on a productive system running 1.6.1.6, only
SIP channels, with session-timers=refuse. Unfortunately I don't have a
"core show locks" to attach so far. Being a productive system, support
personnel restarted the server as quickly as possible, but I'll try to get
one.

We have about 2000 registered peers, of which 300 have qualify=10000, and
we use a DAHDI dummy timer source. Peak is 50 simultaneous calls. We use
res_odbc connected to mysql and reload the configuration every 5 minutes
with "dialplan reload" and "sip reload". 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-23 11:29 manuel_wenger  Note Added: 0112667                          
======================================================================