[asterisk-bugs] [Asterisk 0016901]: Asterisk 1.4.29 musiconhold of remote party doesnt work

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16901 
====================================================================== 
Reported By:                basty
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16901
Category:                   Resources/res_musiconhold
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.29.1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-25 04:36 CST
Last Modified:              2010-02-26 06:13 CST
====================================================================== 
Summary:                    Asterisk 1.4.29 musiconhold of remote party doesnt
work
Description: 
"A" calls an external number (no asterisk pbx), "B" answers the call and
puts "A" on hold. While "A" is on hold, his own asterisk moh is playing
instead of the moh of the external pbx.
====================================================================== 

---------------------------------------------------------------------- 
 (0118595) davidw (reporter) - 2010-02-26 06:13
 https://issues.asterisk.org/view.php?id=16901#c118595 
---------------------------------------------------------------------- 
Actually, I think the argument does apply to DAHDI to SIP, as this issue
isn't really to do with res_musiconhold.  The underlying problem is that
Asterisk can only signal HOLD and UNHOLD events between the source and
destination channel, so when chan_sip receives HOLD, it doesn't know
whether it has come from a phone, which won't be providing any MOH, or from
a PABX, which might.  The only way to stop it trying to source MOH, without
a new features, is for the upstream channel not to generate
AST_CONTROL_HOLD. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-26 06:13 davidw         Note Added: 0118595                          
======================================================================