[asterisk-bugs] [Asterisk 0015709]: segmentation fault when using mixmonitor with two calls

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15709 
====================================================================== 
Reported By:                covici
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   15709
Category:                   Applications/app_mixmonitor
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 211583 
Request Review:              
====================================================================== 
Date Submitted:             2009-08-13 05:46 CDT
Last Modified:              2009-09-09 07:32 CDT
====================================================================== 
Summary:                    segmentation fault when using mixmonitor with two
calls
Description: 
If I use the *1 combination to start mixmonitor on my analog phone
connected via an ata,  and another call is going on using my soft phone, I
get a segmentation fault, after it complains about writing a non voice
frame to the stream.
====================================================================== 

---------------------------------------------------------------------- 
 (0110419) lmadsen (administrator) - 2009-09-09 07:32
 https://issues.asterisk.org/view.php?id=15709#c110419 
---------------------------------------------------------------------- 
Tilghman, please close this issue unless it is clear from the backtrace
what the issue was.

If the reporter can determine the difference between the two sip.conf
files they were running, that would be great, but without the information
about the specific change in the sip.conf that was generated, there isn't
going to be much we can do about this issue. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-09 07:32 lmadsen        Note Added: 0110419                          
======================================================================