[asterisk-bugs] [Asterisk 0015817]: crash in local_attended_transfer, likely related to moh - 1.4.26.1

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15817 
====================================================================== 
Reported By:                zerohalo
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15817
Category:                   Channels/chan_sip/Transfers
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.26.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-02 09:42 CDT
Last Modified:              2009-09-10 08:29 CDT
====================================================================== 
Summary:                    crash in local_attended_transfer, likely related to
moh - 1.4.26.1
Description: 
Reopening this as new. Attended SIP transfer from Polycom UA, no queue
involved.

backtrace attached.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015845 Crash during attended transfer occurs
====================================================================== 

---------------------------------------------------------------------- 
 (0110477) lmadsen (administrator) - 2009-09-10 08:29
 https://issues.asterisk.org/view.php?id=15817#c110477 
---------------------------------------------------------------------- 
You just happened to mention you were using 1.4.26.1 - I just wanted to be
100% sure we weren't tracking down an issue that had already been fixed. If
you're using the latest from the branch already (post 15109 close) then
this issue can remain open.

I'd just hate to spend time debugging an issue that was already closed and
fixed. I realize you're not using format_mp3, but there was some discussion
that it may have fixed some other issues not specifically to format_mp3. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-10 08:29 lmadsen        Note Added: 0110477                          
======================================================================