[asterisk-bugs] [Asterisk 0014355]: [patch] Segfault if you transfer a call into a meetme room

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14355 
====================================================================== 
Reported By:                sodom
Assigned To:                rmudgett
====================================================================== 
Project:                    Asterisk
Issue ID:                   14355
Category:                   Channels/chan_misdn
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-01-28 08:44 CST
Last Modified:              2009-07-14 11:44 CDT
====================================================================== 
Summary:                    [patch] Segfault if you transfer a call into a
meetme room
Description: 
Asterisk crashes with a seg fault if you transfer a call (via ISDN
Transfer) into a meetme room. 
Hold/Retrive between PRI-Zaptel and/or other mISDN channels works.

e.g. 
Phone No: 10 connected to port 3
Phone No: 11 connected to port 4
Meetme: Call No: 771 routes into Meetme-Room 9991 (static)

You connect 11 to 10 (success)
-> then press R for hold on 11 (success), 10 gets MOH
-> dial 771 on 11 (success) you get anouncement of MeetMe
-> hang up 11 to transfer 10 to MeetMe -> (crash, seg fault)
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-14 11:44 svnbot         Status                   assigned => resolved
2009-07-14 11:44 svnbot         Resolution               open => fixed       
======================================================================