[asterisk-bugs] [Asterisk 0014709]: [patch] chan_local generates MoH instead of just passing HOLD/UNHOLD further

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14709 
====================================================================== 
Reported By:                dimas
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14709
Category:                   Channels/chan_local
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.21.2 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-20 06:27 CDT
Last Modified:              2009-09-18 08:52 CDT
====================================================================== 
Summary:                    [patch] chan_local generates MoH instead of just
passing HOLD/UNHOLD further
Description: 
The fix for the issue 7671 made chan_local to start/stop generation of MoH
for HOLD/UNHOLD indications. Previously chan_local used to just pass these
frames further.

As result of the fix, if a SIP user dials into the MeetMe conference not
directly but by the means of Local channel and then puts the call on hold,
all the participants in the conference hear MoH generated by the
chan_local.
====================================================================== 

---------------------------------------------------------------------- 
 (0110954) lmadsen (administrator) - 2009-09-18 08:52
 https://issues.asterisk.org/view.php?id=14709#c110954 
---------------------------------------------------------------------- 
What is the next step here? Is the patch attached, or the rolling back of
issue https://issues.asterisk.org/view.php?id=7671 desired?

If not, then how should this issue proceed? (This is still an issue right?
This bug has been opened for a while now.) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-18 08:52 lmadsen        Note Added: 0110954                          
2009-09-18 08:52 lmadsen        Status                   new => feedback     
======================================================================