[asterisk-bugs] [Asterisk 0012581]: Asterisk crashes when a call comes in from a Mediatrix 2102

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12581 
====================================================================== 
Reported By:                dlynes
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12581
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-04-2008 17:01 CDT
Last Modified:              05-06-2008 14:13 CDT
====================================================================== 
Summary:                    Asterisk crashes when a call comes in from a
Mediatrix 2102
Description: 
Call is made from a Mediatrix 2102, Asterisk dumps core on connect.
All registrations and authentications are fine.
====================================================================== 

---------------------------------------------------------------------- 
 dlynes - 05-06-08 14:13  
---------------------------------------------------------------------- 
I have determined what the issue was.

I was trying to strip down the memory footprint on this particular box,
and in so doing, I did a noload on a module (res_features.so) that was
apparently needed by chan_sip.so to be able to use the dial application. 
However, the warning for that was not listed on the screen in core set
verbose 100, nor was it listed in sip debug ip logging to the screen.

I only found the error/warning after using 'asterisk
-vvvvvvvvvvvvvvvvvvvvvg'

What should happen, instead is that it should at least fail with an error
to the screen in normal running mode, if it's going to exit with code 127
like it does. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-06-08 14:13  dlynes         Note Added: 0086472                          
======================================================================