[cisco-voip] MOH Multicast vs Unicast

[Ryan Ratliff]

For a single server you put the MOH server in two MRGs, one with multicast enabled, one without.  Those MRGs go into separate MRGLs that will be used by the phones at HQ (unicast) or remote site (multicast).
There is no mechanism to fail back to an alternate MOH server.  Once CUCM has allocated a server and told the phone then you either get MOH or nothing.

-Ryan

On Sep 28, 2010, at 8:02 PM, Jason Aarons (US) wrote:

What if it’s a single server deployment? Can you configure some phones for multicast and others for unicast moh via MRGL? I’m not clear if a multicast stream fails to get to phone (due to MPLS network), will phone switch request to unicast somehow?
 
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Tuesday, September 28, 2010 4:56 PM
To: Mike Lydick
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] MOH Multicast vs Unicast
 
Yes, the MOH server/source combo determines if unicast or multicast is used, and the server part comes from the device getting put on hold.  Enable all of your audio sources for multicast and they can do both.    Then it's just a matter of setting up the MRGLs so that HQ phones get a unicast MOH server and remote ones get a multicast server.
 
 
-Ryan
 
On Sep 28, 2010, at 4:04 PM, Mike Lydick wrote:
 
Is it possible design a blend Multicast environment where the HQ will use primarily unicast from the Software MOH and remote sites use Multicast from local route. I was thinking this was possible by enabling just 1 multicast server (to be used as the spoofed Local Router MOH multicast address) and all other servers are unicast. Limit the hop count to 2 and setup the local routers according (with the multicast config and single file for MOH).
 

Best Regards,

Mike Lydick


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
 



Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100929/95ddaab7/attachment.html>