assume a central site that has CCM 5.x cluster, and remote sites connected to this central site, regarding MoH, how much either the end-user MoH or network MoH consumes BW if a user in remote site requests unicast MoH from CCM in central site, and what is the best practice to preserve BW for MoH in this scenario?
Baically, MOH is just another audio stream just like a phone call. The bandwidth consumed will depend on the codec being used. If you're streaming g.711 MOH, the bandwidth will be 64k plus overhead (CCM uses 80k for CAC calculations). If you're streaming g.729 MOH, the bandwidth will be 8k plus overhead (CCM used 24k for CAC calculations).
One way to avoid MOH streams traversing the WAN is to allow the local gateways to stream multicast MOH to local devices. Take a look at the following link.
Yes that is correct. You will also need to make sure that CCM is set to stream g.711 and g.729 by configuring these codecs under the IP Voice Media Streaming Application Service Parameters or you will need a transcoder in place to do the job.
g729 isnt made for music, so you can have degradation in quality of music if you use g729 for music across the wan. Unless you set the service parameter under Cisco IP Voice streaming media service, (select 711 and g729), g729 codec will not be used for MOH.
Brandon already suggested the best solution for wan environments. Use multicast streaming from flash of the remote site router. One catch with this solution is that you can only have one music source defined in the callmanager. Although you can change the moh file in the flash on each remote site router with a different one, if you want different music at different remote sites.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.