[asterisk-bugs] [Asterisk 0010342]: On Mac OS X PowerPC, Asterisk 1.4.x stops bridging new calls shortly after start

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10342 
====================================================================== 
Reported By:                jcovert
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10342
Category:                   Core/Portability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.0-beta8 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-31-2007 09:10 CDT
Last Modified:              05-08-2008 17:11 CDT
====================================================================== 
Summary:                    On Mac OS X PowerPC, Asterisk 1.4.x stops bridging
new calls shortly after start
Description: 
I have unsuccessfully tried to get every 1.4.x version of Asterisk to work
on Mac OS X PowerPC, most recently Asterisk 1.4.9 on Mac OS X 10.4.10.

Asterisk starts up fine, and works for a short while.  But after about the
third or fourth bridged call (local sip soft client, SJphone, or locally
connected SIP ATAs Cisco ATA 186), RTP read too short errors start
ocurring, or other dead call problems.  It is still possible to connect to
IVRs within asterisk, and inbound IAX2 calls from a 1.2.22 version of
Asterisk to the 1.4.9 version still work, but originating SIP devices are
unable to reliably make outbound calls.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 05-08-08 17:11  
---------------------------------------------------------------------- 
I believe that I have reproduced this issue. I set up a Mac Mini in the
hopes of reproducing this and issue http://bugs.digium.com/view.php?id=10202.
This one I can reproduce
reliably as long as I start asterisk with -vvvvvgc as the arguments. I
place about three SIP-to-SIP calls and then boom, Asterisk gets in an
unusable state. Like jcovert reported, I can still place calls to Asterisk,
but if I try to place calls to a remote Asterisk server, the local server
seems to get "stuck" during the Dial command. When this happens, the
Asterisk console becomes completely unresponsive (i.e. when I type,
characters do not appear on the screen and none of the commands I enter are
executed). One thing that is a bit odd is that verbose messages still
appear on the console. If I attach to the running process with asterisk
-rvvvvv, then I can type commands, but they are apparently ignored. The
absolute worst part is that when Asterisk gets in this state, there's no
apparent way to stop the process. Killing it with the -9 flag doesn't even
do it. I usually just restart the system to get things back to normal
again.

Let me note that I spent the better part of a day attempting to reproduce
this. I was able to make several thousand calls to and from Asterisk with
no trouble at all as long as I started Asterisk using asterisk& and then
connected via a remote console with asterisk -rvvvvvv.

So far I have been able to get a backtrace of the threads when the
situation occurs. I will analyze this further and see if it is apparent if
there's a deadlock or perhaps some sort of system call that is blocking
forever. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-08-08 17:11  putnopvut      Note Added: 0086634                          
======================================================================