CUCM: Single-Site Deployment Best CCIE security Course Training Institute in New Delhi Gurgaon

Network Bulls
www.networkbulls.com
Best Institute for CCNA CCNP CCSP CCIP CCIE Training in India
M-44, Old Dlf, Sector-14 Gurgaon, Haryana, India
Call: +91-9654672192

As illustrated in Figure 2-1, the Single-Site model for CUCM consists of a CUCM cluster
located at a single site, or metropolitan-area network (MAN), with no telephony services
provided over a WAN. All CUCM servers, applications, and digital signal processor (DSP)
resources are located in the same physical location.
Figure 2-1 Single-Site Model
An enterprise would typically deploy the Single-Site model over a LAN or MAN, which
carries the voice traffic within the site. In this model, calls beyond the LAN or MAN use
the public switched telephone network (PSTN).
In a Single-Site deployment model, all CUCM servers, applications, and DSP resources are
located in the same physical location.
The Single-Site model has the following design characteristics:
■ Maximum of 30,000 Skinny Client Control Protocol (SCCP) or Session Initiation
Protocol (SIP) IP phones or SCCP video endpoints per cluster.
■ Maximum of 1100 H.323 devices (gateways, multipoint conference units [MCU],
trunks, and clients) or Media Gateway Control Protocol (MGCP) gateways per CUCM
cluster.
IP
Unified CM
Cluster
SIP/SCCP
PSTN
V
CUCM: Single-Site Deployment 35
■ PSTN for all calls outside the site.
■ DSP resources for conferencing, transcoding, and media termination points (MTP) are
located at the single site.
■ H.323 clients, H.323 MCUs - Cisco Unified Videoconferencing 3500 series, and
H.323/H.320 gateways that must register with a Cisco IOS Gatekeeper (Cisco IOS
Release 12.3(8)T or later). CUCM then uses an H.225 trunk or gatekeeper-controlled
trunk to register with the gatekeeper. The gatekeeper provides call-routing and
bandwidth management services for the H.323 devices registered to it (including
CUCM). Multiple Cisco IOS Gatekeepers may be used to provide redundancy.
■ MCU resources are required for multipoint videoconferencing. Depending on
conferencing requirements, these resources may be either SCCP or H.323 or both.
Follow these guidelines and best practices when implementing the Single-Site model:
■ Provide a highly available, fault-tolerant infrastructure based on a common infrastructure
philosophy. A sound infrastructure is essential for easier migration to Cisco UC,
integration with applications such as video streaming and videoconferencing, and expansion
of your Cisco UC deployment across the WAN or to multiple CUCM clusters.
■ Know the calling patterns for your enterprise. Use the Single-Site model if most of
the calls from your enterprise are within the same site or to PSTN users outside your
enterprise.
■ Use G.711 codecs for all endpoints. This practice eliminates the consumption of DSP
resources for transcoding. Those resources can be allocated to other functions such as
conferencing and MTPs.
■ Use MGCP gateways for the PSTN if you do not require H.323 functionality. This
practice simplifies the dial plan configuration. H.323 might be required to support
specific functionality such as support for nonfacility-associated signaling (NFAS)
or caller identification (CLID) on FXO analog gateways. CLID is supported on all
T1-based MGCP gateways.
■ Implement a network infrastructure for high availability, in-line power for IP phones,
quality of service (QoS) mechanisms, and security.