[asterisk-bugs] [Asterisk 0015356]: After a few thousand calls, or at random, Asterisk stops receiving events from the network

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Jun 24 11:57:03 CDT 2009


The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15356 
====================================================================== 
Reported By:                falves11
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15356
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!): 201533 
Request Review:              
====================================================================== 
Date Submitted:             2009-06-18 17:59 CDT
Last Modified:              2009-06-24 11:57 CDT
====================================================================== 
Summary:                    After a few thousand calls, or at random, Asterisk
stops receiving events from the network
Description: 
The application is up, you may do "core restart now", "core show channels",
etc.,  but no new calls entert and I think no packests are delivered. Other
times it is dead and only a "killall asterisk" will restart it.
====================================================================== 

---------------------------------------------------------------------- 
 (0106908) lmadsen (administrator) - 2009-06-24 11:57
 https://issues.asterisk.org/view.php?id=15356#c106908 
---------------------------------------------------------------------- 
The standard debugging information applies here in regards to chan_sip:

* sip debug
* sip history
* potentially a wireshark trace
* enable MALLOC_DEBUG and provide "core show locks"
* if Asterisk crashes, provide a backtrace with DONT_OPTIMIZE enabled

This sounds like a deadlock to me.

Additionally, this is not a blocking issue just because it affects your
network :) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-24 11:57 lmadsen        Note Added: 0106908                          
2009-06-24 11:57 lmadsen        Status                   new => feedback     
======================================================================




More information about the asterisk-bugs mailing list