
7-5
Cisco IP Telephony Network Design Guide
78-11103-03
Chapter 7 Multisite WAN with Centralized Call Processing
Dial Plan Considerations
does not use E.164 addresses in the admission request (ARQ) when it queries
the gatekeeper for admission. This restriction may change in future releases
of Cisco CallManager.
Dial Plan Considerations
A centralized call processing cluster must be able to handle three primary types
of calls:
• Intracluster calls between IP phones within the cluster.
• Intercluster calls between Cisco CallManager clusters.
• PSTN calls through a local gateway at each site.
In this section, generalized design guidelines are provided for each of these cases.
Note Where location-based call admission control is used, automatic
alternate routing through the PSTN is not possible. Instead, the
calling party hears a busy tone and, on devices with a display, sees
an out-of-bandwidth message.
Interlocation Calls
Interlocation calls are generally made between IP phones and other devices such
as fax machines and analog phones connected to gateway devices based on Media
Gateway Control Protocol (MGCP) or the Skinny Gateway Protocol. As within a
cluster, all devices register with a single Cisco CallManager so that the
availability of all devices is known. When a call is attempted, the outcome is one
of the following:
• The call succeeds.
• A busy tone is issued due to the remote device being active.
• A busy tone is issued due to insufficient WAN resources. A configurable
message is also displayed on the device.
No configuration of a dial plan is required for intracluster calls in the majority of
cases.
Comentarios a estos manuales