background image
C H A P T E R
6-1
Cisco IP Telephony Solution Reference Network Design
956662
6
Call Processing
This chapter summarizes the following design considerations related to the call processing functions of
a Cisco CallManager cluster:
·
Clustering Guidelines, page 6-1
·
Call Processing with Cisco CallManager Releases 3.1 and 3.2, page 6-2
·
Call Processing with Cisco CallManager Release 3.3, page 6-2
·
Device Weights, page 6-3
·
Dial Plan Weights, page 6-5
·
Call Processing Redundancy, page 6-7
This chapter also contains the following section on gatekeepers, which can be used as additional call
processing agents in combination with Cisco CallManager to expand or enhance the capabilities of your
IP Telephony network:
·
Gatekeeper Considerations, page 6-10
Clustering Guidelines
The following guidelines apply to all Cisco CallManager clusters:
Note
A cluster may contain a mix of server platforms, but all servers in the cluster must run the same
Cisco CallManager software release.
·
Under normal circumstances, place all members of the cluster within the same LAN or MAN.
·
If the cluster spans an IP WAN, follow the specific guidelines for clustering over an IP WAN. (See
Clustering Over the IP WAN, page 1-17
.)
·
Each server in the cluster can support a maximum of 500 H.323 (gateway and client) and digital
MGCP devices.
·
Cisco highly recommends that you ensure all Cisco CallManager servers are connected to the
Ethernet at 100 Mbps Full Duplex. If 100 Mbps is not available on smaller deployments, then use
10 Mbps Full Duplex. You can achieve this configuration by forcing the NIC card to the required
speed and duplex and by manually configuring the Ethernet switch port as well.