[asterisk-bugs] [Asterisk 0011557]: Asterisk segfault coincides with the "locking" when attempting to receiving inbound calls

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11557 
====================================================================== 
Reported By:                FuriousGeorge
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11557
Category:                   General
Reproducibility:            unable to reproduce
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:            1.4.12  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-14-2007 16:51 CST
Last Modified:              12-18-2007 16:23 CST
====================================================================== 
Summary:                    Asterisk segfault coincides with the "locking" when
attempting to receiving inbound calls
Description: 
Every few weeks, we stop getting incoming calls because after we call out
via POTS and hangup the channel stays open and must be hung up on.  When
this happens to one of our three FXO channels, it will soon happen to all
of them.

When it happened this time I was lucky enough to have it coincide with a
segfault and core dump shortly after the soft hangups.  Im hoping the two
things are in some way related
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0011558 Asterisk segfault coincides with the &q...
====================================================================== 

---------------------------------------------------------------------- 
 FuriousGeorge - 12-18-07 16:23  
---------------------------------------------------------------------- 
file, ive attached the output of the commands as you requested.

Also, today, the lines "locked up" again.  I've always used 9 to force the
use of a landline, and after my users do that once, the snom phones will
automatically insert 9 into the number unless the user stops it from doing
so (its the number guessing feature).

So, inadvertently, they have been using the landlines more today, and as I
am discovering, the more we use chan zap, the greater the likelihood we
lock some channels.

Here is the output of 'core show channels' today:
claudia*CLI> show channels
Channel              Location             State   Application(Data)
IAX2/voicepulse01-2  (None)               Up      Bridged
Call(SIP/Register-0082
SIP/Register-00829d7 s at macro-voip_call:3  Up     
Dial(IAX2/voicepulse01/1908227

IAX2/voicepulse01-5  (None)               Up      Bridged
Call(SIP/Carmen-0084a6

SIP/Carmen-0084a660  s at macro-voip_call:3  Up     
Dial(IAX2/voicepulse01/1201618

Zap/8-1              (None)               Up      Bridged
Call(SIP/Carmen-008214

SIP/Carmen-00821410  919737325516 at outboun Up     
Dial(ZAP/g1/ww19737325516|60)

SIP/carmen-00817600  (None)               Up      Bridged Call(Zap/7-1)
Zap/7-1              s at inbound:3          Up      

Dial(zap/1&zap/2&sip/carmen&si
SIP/carmen-008b94b0  (None)               Up      Bridged Call(Zap/5-1)

Zap/5-1              s at inbound:3          Up     
Dial(zap/1&zap/2&sip/carmen&si

Zap/6-1              (None)               Up      Bridged
Call(SIP/Carmen-b5321e
SIP/Carmen-b5321e90  919737325516 at outboun Up     
Dial(ZAP/g1/ww19737325516|60)
12 active channels

It seems more often than not that the 919737325516 number is the culprit
too!  am i going crazy?

To be honest, I dont care if asterisk crashes from time to time, as
running it via safe_asterisk protects me.  Users just think a call was
dropped.

On the other hand, this issue with the locking of zap channels is a major
problem causing much frustration to all parties involved.  Im a little
worried that the issues are not related now. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-18-07 16:23  FuriousGeorge  Note Added: 0075679                          
======================================================================