[cisco-voip] MOH not working between clusters

[Scott Voll]

so based on that link

" Distributed Multisite Deployments

Multisite IP telephony deployments with distributed call processing
typically contain WAN or MAN connections between the sites. These
lower-speed links usually cause bandwidth and throughput bottlenecks. To
minimize bandwidth consumption on these links, Cisco recommends use of the
G.729 codec for all MoH audio streams traversing them. Because the
G.729codec is optimized for voice and not music applications, you
should use
G.729 only across the WAN/MAN links, where the bandwidth savings far
outweighs the lower quality afforded by G.729 for MoH transport.

Unlike with centralized multisite deployments, in situations where
G.711might be required for MoH audio streams traveling across a WAN,
MoH audio
streams cannot be forced to G.711 in a distributed multisite deployment.
Even when MoH servers are placed in a separate Unified CM region and the
G.711 codec is configured between this region and the intercluster or SIP
trunk's region, the codec of the original voice call is maintained when a
call between the two clusters is placed on hold by either phone. Because
these intercluster calls are typically encoded using G.729 for bandwidth
savings, a MoH stream from either cluster will also be encoded using G.729.

Furthermore, multicast MoH is not supported for calls between Unified CM
clusters (intercluster calls). Therefore, you must configure at least one
unicast MoH resource in each Unified CM cluster if you want MoH on the
intercluster or SIP trunk.

Proper multicast address management is another important design
consideration in the distributed intercluster environment. All MoH audio
source multicast addresses must be unique across all Unified CM clusters in
the deployment to prevent possible overlap of streaming resources throughout
the distributed network. "



*it just looks like you need a Unicast resource for the ICT.*



Scott

On Fri, Feb 15, 2008 at 10:13 AM, Eric Pedersen <eric.pedersen at sait.ca>
wrote:

>  According to the ucm 5.x srnd, multicast MoH is not supported across an
> intercluster trunk.  Check out:
>
> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/5x/50moh.html
>
>
>
>
>  ------------------------------
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Dana Tong (AU)
> *Sent:* February 14, 2008 19:05
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] MOH not working between clusters
>
>
>
> Hi everyone,
>
>
>
> I have a problem with Music on Hold between two CM clusters. One cluster
> is running CM4 and the other UCM5.1.3.1000-12.
>
> Music on Hold out to the PSTN works fine but not between the two
> clusters.  Phones in the UCM5 cluster hear MOH ok also.
>
>
>
> Testing shows that the remote addresses change to the multicast MOH
> address but only silence is heard.
>
>
>
> Does anyone have any tips to look for with MOH over an intercluster trunk?
>
>
>
> Cheers
>
> D
>
>
>
>
>
>
> ******************************************************************************
>
> - NOTICE FROM DIMENSION DATA AUSTRALIA
>
> This message is confidential, and may contain proprietary or legally
> privileged information. If you have received this email in error, please
> notify the sender and delete it immediately.
>
>
>
> Internet communications are not secure. You should scan this message and
> any attachments for viruses. Under no circumstances do we accept liability
> for any loss or damage which may result from your receipt of this message or
> any attachments.
>
>
> ******************************************************************************
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080215/568a06d3/attachment-0001.html