Thats what I thought, but in the CM7 help pages, for Service Activation Recommendations, it says NOT to activate this on the first node, or any nodes running CM service.

Interesting, thanks for the input.

Hey Pete,

As you nicely noted, one of the design recommendations for very "resource intensive" clusters is to push MOH onto their own "stand-alone" servers. This is why you are seeing the reference to not activate that service. For many of us though, Co-resident MOH Servers in conjunction with the CCM Service are still a very viable solution :)

Co-resident and Standalone MoH

The MoH feature requires the use of a server that is part of a Unified CM cluster. You can configure the MoH server in either of the following ways:

•Co-resident deployment

In a co-resident deployment, the MoH feature runs on any server (either publisher or subscriber) in the cluster that is also running the Unified CM software.

--------------------------------------------------------------------------------

Note The term co-resident refers to two or more services or applications running on the same server.

--------------------------------------------------------------------------------

•Standalone deployment

A standalone deployment places the MoH feature on a dedicated server within the Unified CM cluster. The sole function of this dedicated server is to send MoH streams to devices within the network.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/moh.html

Music On Hold (Revised 12/19/2008)

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_0_1/ccmfeat/fsmoh.html

Hope this helps buddy!

Rob

Thanks for the sanity check