cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
428
Views
0
Helpful
3
Replies

How To Configure Multicast MOH Redundancy?

leh-poh.teo
Level 1
Level 1

I have 1 Publisher and 1 Subscriber. My remote branch has 2 voice gateways for redundancy. In order to prevent MOH tranverses across the WAN, I implement Multicast MOH on the 2 voice gateways. After I set 139.1.1.1 with IP increment method on publisher, I am unable to set 139.1.1.1 for Subscriber. I can only set 139.1.1.5 on Subscriber. With different multicast address on Publisher and Subscriber, how do I have multicast MOH redundancy for my branch?

3 Replies 3

Aaron Harrison
VIP Alumni
VIP Alumni

CallManager will presumably instruct phones to listen to whichever server is most preferred/active...

You could set one address on one voice gateway and the other IP address on the other gateway - each would transmit on it's own IP and phones could then receive regardless of which IP CM instructs them to listen to...

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!

What you mean is set publisher to 139.1.1.1 and subscriber to 139.1.1.5. Voice gateway 1 set to 139.1.1.1 and voice gateway 2 set to 139.1.1.5. If subscriber fails, phone still able to join another multicast group, 139.1.1.1 since there is a voice gateway 1 with 139.1.1.1 configured.

But if voice gateway 2 fails, phone still trying to join 139.1.1.5 because the subscriber MOH have priority over the publisher MOH in Media resource group list. Therefore, the music on hold will fail.

Any other better suggestion?

You're running into an issue where the SRST Multicast MoH feature to save WAN bandwidth only lets you set one IP multicast group and not multiple and has no way to detect a CCM failure really since the 2 don't work together and are seperate configurations. It's always going to stream to the 1 multicast group.

This was more of a neat trick to save WAN bandwidth really. Since it is multicast phones just are tuning in to a mcast stream and that mcast group address is controlled by call manager. But the source doesn't need to be call manager server and can be anywhere on network just as long as the phone can tune in when it is put on hold. In your case, it is the router sourcing the stream.

Ideally for sites where you are doing this, you want to set the MRGL for those users/devices to always use same MOH server/audio source. This way the address is always the same in the phone config since router can only have 1 mcast stream configured. I'm not sure what happens if the MoH server fails on CCM server if it will instruct phone to use that mcast group address or something else during failure of services. Haven't tested that scenario with this yet. You could do unicast on other server for backup then phone would get instructed to use unicast stream during failures but that would use WAN bandwidth then at those times.