[asterisk-bugs] [Asterisk 0012663]: Incoming REMOTE_HOLD on Zap is always passed to the bridged channel

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12663 
====================================================================== 
Reported By:                gminet
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12663
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-15-2008 11:40 CDT
Last Modified:              06-19-2008 08:14 CDT
====================================================================== 
Summary:                    Incoming REMOTE_HOLD on Zap is always passed to the
bridged channel
Description: 
We have several customers using PRI E1 lines to connect to the telco
(Digium TE220B cards, E1 PRIs in Belgium).

When someone on ther side calls out using a SIP phone another party
through the telco/pri and gets placed on hold by the remote party, he hears
the local music on hold and not the remote music on hold. That's confusing
our customers as often the company name and products are often said on top
of the music.
In fact he can briefly hear the remote moh that gets replaced after half a
second by the local one.

This happens when the remote party is using a PBX on PRI, some PBX on BRI,
and also mobile phones.

In the logs I see the zap channel is receiving a REMOTE_HOLD control frame
and the the local moh is started on the bridged sip channel.

====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 06-19-08 08:14  
---------------------------------------------------------------------- 
I'm not sure it is.  Certainly the receipt of that signal from the PRI is
having unintended consequences, but the question is, what should happen
when that signal is received?  The intention of the signal for the local
end to provide its own MOH, which is exactly what is happening. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-19-08 08:14  Corydon76      Note Added: 0088904                          
======================================================================