[asterisk-bugs] [Asterisk 0014296]: chan_dahdi segfaulting (may be related to Bridge() application).

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14296 
====================================================================== 
Reported By:                kebl0155
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14296
Category:                   Channels/chan_dahdi
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.0.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-21 08:26 CST
Last Modified:              2009-01-27 16:04 CST
====================================================================== 
Summary:                    chan_dahdi segfaulting (may be related to Bridge()
application).
Description: 
Hi,

We changed one of our apps to use the new Bridge() command today.  Since
then we've had two segfault/core dumps in chan_dahdi.

====================================================================== 

---------------------------------------------------------------------- 
 (0098911) blitzrage (administrator) - 2009-01-27 16:04
 http://bugs.digium.com/view.php?id=14296#c98911 
---------------------------------------------------------------------- 
Darn... I can't seem to reproduce this. I've run calls through the Local
channel to try and get it to die, but no luck thus far. I wonder if it has
something to do with masquerading from a DAHDI channel...

Here is a simple dialplan I've been working with. Not sure if this is
really the "right" way of trying to reproduce it, but it was kinda what I
figured out based on what was happening in this bug report.

;
exten => 555,1,MusicOnHold()

exten => 666,1,Dial(Local/777 at default)

exten => 777,1,Answer()
exten => 777,n,Bridge(SIP/110-1871cf00)
exten => 777,n,Hangup()
;

Extension 110 dials 555 which is then an active call, then I take
extension 111 and dial 666 (after updating the Bridge() application to have
the correct channel name), reload the dialplan, then see what happens. I
tried hanging up 111 first and 110 first, but did not result in any crashes
or warnings. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-27 16:04 blitzrage      Note Added: 0098911                          
======================================================================