CISCO IPT培训.ppt

* To support up to 7,500 phones you should have at least 2 servers. As you can see from the figure above, one server will be the publisher and the secondary or backup Cisco CallManager. The second server will be a subscriber server and the primary Cisco CallManager to handle all the call processing. * In order to support up to 15,000 users, the cluster will be built with four servers. As the figure above shows, you will have a stand-alone publisher (A), also known as the “glass house” because it does not do call processing, two primary Cisco CallManagers (B and C), and a dedicated backup Cisco CallManager (D). When there are over 7,500 users on one server, dial tone and call processing is slowed dramatically. It may take 2 to 3 seconds after you go off-hook to hear the dial tone. If this ever happens, focus on getting one primary server up as fast as possible, then the next and use the information from alarms and logs to troubleshoot why this happened. * To support 30,000 users, just add four more servers and duplicate the primary backup scenario for 15,000 users. The device redundancy scheme is a little different and now we can have a secondary and tertiary. In the cluster to support 30,000 users there are 8 servers. One server is the publisher (glass house) that does database processes and does no call processing. One server is the Cisco TFTP server that serves device configuration files and does no call processing. Four servers will be primary Cisco CallManagers and two servers will be backup Cisco CallManagers. The redundancy scheme uses both backup servers as secondary and tertiary for the primary Cisco CallManagers. As shown in the figure above, “B” is the primary, “D” is the secondary and “H” is the tertiary for a device that is assigned to the “BDH” Cisco CallManager Group. * If the connections between the publishing Cisco CallManager database and the subscribers within a cluster are broken for any reason, you cannot replicate the database to the subscri