Sizing the CallManager Cluster
CallManager servers can be grouped together to form a cluster. A cluster can contain a maximum of eight CallManager servers doing the call processing. There can be other servers in the cluster to perform dedicated functions, such as a Publisher server that hosts a read/write database, a dedicated TFTP/DHCP server, a dedicated Music on Hold (MoH) server, and so forth. The publisher database is used as a single point of administration for the cluster configuration changes and to produce Call Detail Records (CDRs). The TFTP server facilitates the download of configuration files, device loads (operating code), and ring types.The information in Table E-5 needs to be collected on a per-site basis to determine the number of clusters, the number of CallManager servers per cluster, and the type of hardware platform required per cluster.
Site Name | IP Phones with Model Numbers | Voice-Mail Ports | TAPI/JTAPI Interfaces | Voice Gateways Include the Model and Number of DS0s | Conferencing, Transcoding, MTP, MoH Resources |
---|---|---|---|---|---|
Notes/Comments
A CallManager cluster consists of two or more CallManager servers. The number of devices that can be supported by a single CallManager server depends on the quantity of device types that need to be registered, such as IP Phones and gateways. To correctly size the CallManager cluster, you need to collect the information given in Table E-5 and follow the CallManager cluster-sizing guidelines given in Cisco IP Telephony Solution Reference Network Design (SRND) at http://www.cisco.com/go/srnd to decide on the hardware platform and number of servers in the cluster.