Table Of Contents
Deployment Models
Deployment Overview
Single-Site Model
Organization Suitability
Design Characteristics
User Roles and Endpoints
Supported Applications
Multisite Centralized Call Processing Model
Organization Suitability
Design Characteristics
User Roles and Endpoints
Supported Applications
Multisite Distributed Call Processing Model
Organization Suitability
Design Characteristics
User Roles and Endpoints
Supported Applications
Clustering Over IP WAN Call Processing Model
Organization Suitability
Design Characteristics
User Roles and Endpoints
Supported Applications
Major Components of Deployment Models
Deployment Models
This chapter provides an overview of the Cisco Unified Communications deployment models that Cisco has tested and verified. These models are not the only ways in which you can deploy the Cisco Unified Communications system, nor are they design recommendations. Rather, they are designed to provide sample configurations that address typical system-level requirements.
For additional guidelines, recommendations, and best practices for implementing enterprise networking solutions, refer to the Cisco Solution Reference Network Design (SRND) guides and related documents, which are available at this URL:
www.cisco.com/go/srnd
For additional information about the deployment models, including details about all components in each model, refer to the Cisco Unified Communications System Technical Information site at: http://www.cisco.com/go/unified-techinfo.
This chapter includes these sections:
•
Deployment Overview
•Single-Site Model
•Multisite Centralized Call Processing Model
•Multisite Distributed Call Processing Model
•Clustering Over IP WAN Call Processing Model
•Major Components of Deployment Models
Deployment Overview
The sample Cisco Unified Communications deployments demonstrate a variety of business applications based on the following criteria:
•End-to-end IP communications requirement
•Interoperability between sites
•Administrative requirements (centralized or distributed)
•Messaging requirements
•Conferencing requirements
•Availability requirements
•Mobility requirements
•Scalability requirements
•Customer interaction network requirements
Single-Site Model
The Single-Site model is designed for autonomous offices in which most or all employees are IPC users. This model supports up to 30,000 users.
Figure 1-1 shows an example of this model.
Figure 1-1 Single-Site Model
Organization Suitability
The Single-Site model is suitable for medium-sized businesses and government operations that reside at one site and that need basic call processing, some contact center capabilities, and basic messaging and conferencing. Such operations include legal and financial professional offices, and municipal government offices.
Design Characteristics
The Single-Site model is designed to be locally managed and administered. It can operate on a wired or wireless LAN. Local and long distance calling is achieved through gateway connectivity with the PSTN by various combinations of T1/E1 CAS and PRI.
User Roles and Endpoints
The Single-Site model provides flexible communications features for operators and administrative assistants. There are some executive phones, some of which are video-capable. Most other employees use digital telephones, including wireless telephones, and a voice messaging system, which this model also provides. In addition, some staff may take orders or provide technical support. This model provides basic contact center capabilities to handle these requirements.
Some users, such as building services and shipping and receiving employees, may require mobile phones. This model provides on-campus device mobility features for these users.
Supported Applications
The Single-Site model supports applications that provide a wide array of advanced features. These applications include:
•Call processing:
–Cisco Unified Communications Manager
–Cisco Unified Communications Manager Express
–Cisco Unified Communications Manager Business Edition
•Contact Center:
–Cisco Unified Contact Center Express
–Cisco Unified Contact Center Enterprise
–Cisco Unified IP IVR
–Cisco Unified Customer Voice Portal
•Messaging:
–Cisco Unity
–Cisco Unity Connection
–Cisco Unity Express
•Instant messaging and presence: Cisco Unified Presence
•Conferencing:
–Cisco Unified MeetingPlace Express
–Cisco Unified Videoconferencing
•System management:
–Cisco Unified Communications Manager Serviceability Tools
–Cisco Unified Operations Manager
–Cisco Unified Service Monitor
–Cisco Unified Service Statistics Manager
–Cisco Unified Provisioning Manager
–Cisco Monitor Manager and Monitor Director (for small or medium size deployments with Cisco Unified Communications Manager Express and or Cisco Unity Express)
Multisite Centralized Call Processing Model
The Multisite Centralized Call Processing model is designed for distributed operations with a large central or headquarters site and multiple remote or branch sites. This model can support up to a total of 30,000 phones distributed among up to a maximum of 1000 sites. Based upon the bandwidth available, each site can support any number of users up to the overall total of 30,000 phones.
Figure 1-2 shows an example of this model.
Figure 1-2 Multisite Centralized Call Processing Model
Organization Suitability
The Multisite Centralized Call Processing model is suitable for businesses such as banks, which include a corporate headquarters and many local or regional offices.
Design Characteristics
In the Multisite Centralized Call Processing model, each branch site connects to the headquarters site or sites through a WAN. Branch sites receive call processing functions from the headquarters site. Failover capabilities at each branch site ensure that it can continue to operate if the WAN connection to the headquarters site is lost. Branch sites include small contact center capabilities.
The WAN connection between the headquarters and branch sites can be frame relay, MPLS, or site-to-site VPN. Each branch site can operate on a wired or wireless LAN.
Connectivity with legacy PBXs in the headquarters site can be provided T1/E1 CAS, PRI, Q SIG, and DPNSS. Connectivity to the PSTN in the headquarters site is provided through various combinations of T1/E1 CAS and PRI.
Local calling is achieved through gateway connectivity. Long distance calling for branch sites uses the WAN for on-net calling. Off-net long distance traffic is backhauled over the WAN to one or more drop-off gateways.
This model is designed to be administered at the headquarters location.
User Roles and Endpoints
Headquarters roles and endpoints are identical to those described in the "Single-Site Model" section. Branch sites access the call processing capabilities in the headquarters site. While there are some executive phones, most employees use digital telephones and the central voice messaging system.
Some staff may take orders or provide technical support. This model provides basic contact center capabilities in the branches to handle these requirements.
Supported Applications
The Multisite Centralized Call Processing model supports applications that provide comprehensive features for all sites. These applications include:
•Call processing:
–Cisco Unified Communications Manager (in central site)
–Cisco Unified Communications Manager Express for fixed remote teleworker applications (in central site)
–Cisco Unified Communications Manager Business Edition (in central site)
–Unified SRST or Cisco Unified Communications Manager Express in SRST mode (as backup for Cisco Unified Communications Manager in branch sites and for Cisco Unified Communications Manager Business Edition in branch or central sites).
•Contact Center:
–Cisco Unified Contact Center Enterprise (in headquarters)
–Cisco Unified Contact Center Express (based in headquarters)
–Cisco Unified Customer Voice Portal (for queueing and self-service at headquarters or branches). Unified Customer Voice Portal is an interactive voiceXML-based response (IVR) solution that provides carrier-class IVR and IP switching services on Voice over IP (VoIP) networks. You can integrate Unified CVP with Unified Contact Center Enterprise or can deploy as a self-service IVR solution.
–Cisco unified IP IVR for centralized queuing.
•Messaging:
–Cisco Unity (based in headquarters)
–Cisco Unity Connection
–Cisco Unity Express
•Instant messaging and presence: Cisco Unified Presence (based in headquarters)
•Conferencing:
–Cisco Unified MeetingPlace (based in headquarters)
–Cisco Unified Videoconferencing
•System management:
–Cisco Unified Operations Manager (based in headquarters)
–Cisco Unified Service Monitor (based in headquarters)
–Cisco Unified Service Statistics Manager (based in headquarters)
–Cisco Unified Provisioning Manager
–Cisco Monitor Manager and Monitor Director (for monitoring deployments with Cisco Unified Communications Manager Express and Cisco Unity Express or Cisco Unified Communications Manager Express in SRST mode as backup to Cisco Unified Communications Manager)
–Cisco netManager
–LAN Management Solution
Multisite Distributed Call Processing Model
The Multisite Distributed Call Processing model is designed for organizations with large user populations or large numbers of geographically distributed sites resulting in the need for more than a single call processing entity. This model is suited for deployments that require multiple Cisco Unified Communications Manager clusters or Cisco Unified Communications Manager Express platforms. Each call processing entity in this model is configured as a Single-Site Model (see the "Single-Site Model" section) or Multisite Centralized Call Processing Model (see the "Multisite Centralized Call Processing Model" section) and each has a common dial plan and feature set.
Figure 1-3 shows an example of this model.
Figure 1-3 Multisite Distributed Call Processing Model
Organization Suitability
The Multisite Distributed Call Processing model is suitable for business operations that consist of multiple sites in various regions. Such operations include technology, manufacturing, transportation, and distribution and logistics companies.
Design Characteristics
Each site in the Multisite Distributed Call Processing model can operate on a wired or wireless LAN. The intersite WAN connection can be frame relay, MPLS, or site-to-site VPN. Each branch site can operate on a wired or wireless LAN.
Local calling is achieved through gateway connectivity at each site. Long distance calling for each site uses the WAN for on-net calling. Off-net long distance traffic is backhauled over the WAN to one or more drop-off gateways.
User Roles and Endpoints
Each site in the Multisite Distributed Call Processing model has the same user roles and endpoints that are described in the "Multisite Centralized Call Processing Model" section.
Supported Applications
The Multisite Distributed Call Processing model supports applications that provide powerful, flexible, and scalable features. These applications include:
•Call processing:
–Cisco Unified Communications Manager (large sites or deployments)
–Cisco Unified Communications Manager Business Edition
–Cisco Unified Communications Manager Express (smaller sites or deployments)
•Contact Center:
–Cisco Unified Contact Center Enterprise (in one or more locations)
–Cisco Unified IP IVR (for centralized queueing)
–Cisco Unified Customer Voice Portal (for centralized or distributed queuing and self-service). Unified Customer Voice Portal is an interactive voiceXML-based response (IVR) solution that provides carrier-class IVR and IP switching services on Voice over IP (VoIP) networks. You can integrate Unified CVP with Unified Contact Center Enterprise or can deploy as a self-service IVR solution.
•Messaging:
–Cisco Unity
–Cisco Unity Connection
–Cisco Unity Express
•Instant messaging and presence: Cisco Unified Presence (in one or more locations)
•Conferencing:
–Cisco Unified MeetingPlace
–Cisco Unified Videoconferencing
•System management:
–Cisco Unified Operations Manager
–Cisco Unified Service Monitor
–Cisco Unified Service Statistics Manager
–Cisco Unified Provisioning Manager
–Cisco Monitor Manager and Cisco Monitor Director
–Cisco netManager
–LAN Management Solution
Clustering Over IP WAN Call Processing Model
The Clustering Over IP WAN Call Processing model is designed for organizations with large user populations across multiple sites that are connected by an IP WAN with the QoS features enabled. The Clustering Over IP WAN supports the two deployment models:
•Local Failover Deployment Model
Local failover requires that you place the Unified Communications Manager subscriber and backup servers at the same site, with no WAN between them. This deployment model is ideal for two to four sites with Unified Communications Manager.
•Remote Failover Deployment Model
Remote failover allows you to deploy primary and backup call processing servers split across the WAN. Using this deployment model, you may have up to eight sites with Unified Communications Manager subscribers being backed up by Unified Communications Manager subscribers at another site.
You can also use a combination of the two deployment models to satisfy specific site requirements. For example, two main sites may each have primary and backup subscribers, with another two sites containing only a primary server each and utilizing either shared backups or dedicated backups at the two main sites.
Organization Suitability
The Clustering Over IP WAN Call Processing model is suitable for business operations that consist of multiple sites in various regions connected over an IP WAN. Such operations include technology, manufacturing, transportation, and distribution and logistics companies.
Design Characteristics
The local failover and remote failover sites in the Clustering Over IP WAN Call Processing model operates over an IP WAN. The intersite WAN connection can be frame relay, MPLS, or site-to-site VPN.
The IP WAN must conform to the following maximum delay and minimum bandwidth requirements:
•The maximum allowed round-trip time (RTT) between any two servers in the Unified Communication Manager cluster is 80 ms.
•A minimum of 1.544 Mbps (T1) bandwidth is required for Intra-Cluster Communication Signaling (ICCS) for every 10,000 busy hour call attempts (BHCA) between sites that are clustered over the WAN. This is a minimum bandwidth requirement for call control traffic, and it applies to deployments where directory numbers are not shared between sites that are clustered over the WAN.
•In addition to the bandwidth required for Intra-Cluster Communication Signaling (ICCS) traffic, a minimum of 1.544 Mbps (T1) bandwidth is required for database and other inter-server traffic for every remote subscriber server.
The IP WAN network should also be engineered to provide sufficient prioritized bandwidth for all ICCS traffic, especially the priority ICCS traffic. Standard QoS mechanisms must be implemented to avoid congestion and packet loss. If packets are lost due to line errors or other conditions, the ICCS packet will be retransmitted because it uses the TCP protocol for reliable transmission. The retransmission might result in a call being delayed during setup, disconnect (teardown), or other supplementary services during the call.
For additional details on IP WAN delay, bandwidth requirements, and QOS engineering, refer to the Clustering Over the IP WAN section in the Unified Communications Deployment Models chapter of Unified Communications SRND at http://www.cisco.com/go/srnd.
User Roles and Endpoints
The local failover and remote failover sites in the Clustering Over IP WAN Call Processing model has the same user roles and endpoints that are described in the "Multisite Centralized Call Processing Model" section.
Some of the key advantages of clustering over the WAN are:
•Single point of administration for users for all sites within the cluster
•Feature transparency
•Shared line appearances
•Extension mobility
•Unified dial plan
Supported Applications
The Clustering Over IP WAN Call Processing model supports applications that provide powerful, flexible, and scalable features. These applications include:
•Call processing:
–Cisco Unified Communications Manager (subscriber and backup)
–Cisco Unified Communications Manager Express (smaller sites or deployments)
–Unified SRST or Cisco Unified Communications Manager Express in SRST mode.
•Contact Center:
–Cisco Unified Contact Center Enterprise
–Cisco Unified IP IVR (for centralized queueing)
–Cisco Unified Customer Voice Portal (for centralized or distributed queuing and self-service). Unified Customer Voice Portal is an interactive voiceXML-based response (IVR) solution that provides carrier-class IVR and IP switching services on Voice over IP (VoIP) networks. You can integrate Unified CVP with Unified Contact Center Enterprise or can deploy as a self-service IVR solution.
•Messaging:
–Cisco Unity
–Cisco Unity Connection
–Cisco Unity Express
•Instant messaging and presence: Cisco Unified Presence
•Conferencing:
–Cisco Unified MeetingPlace
–Cisco Unified Videoconferencing
•System management:
–Cisco Unified Operations Manager
–Cisco Unified Service Monitor
–Cisco Unified Service Statistics Manager
–Cisco Unified Provisioning Manager
–Cisco Monitor Manager and Cisco Monitor Director (for deployments of Cisco Unified Communications Manager Express in SRST mode as a backup to Cisco Unified Communications Manager)
–Cisco netManager
–LAN Management Solution
Major Components of Deployment Models
Table 1-1 shows the major Cisco components in each Cisco Unified Communications deployment model.
Table 1-1 Deployment Models Components Summary
Components
|
Single-Site Model
|
Multisite Centralized Call Processing Model
|
Multisite Distributed Call Processing Model
|
Clustering Over IP WAN Call Processing model
|
Scale
|
•Up to 30,000 phones with Cisco Unified Communications Manager
•Up to 240 phones with Cisco Unified Communications Manager Express
•Up to 575 phones (and up to 500 users) with Cisco Unified Communications Manager Business Edition
|
•Up to 30,000 phones and 1,000 sites with Cisco Unified Communications Manager
•Up to 240 phones with Cisco Unified Communications Manager Express for small or branch site or fixed remote teleworker applications
•Up to 575 phones (and 500 users) and up to a total of 20 sites with Cisco Unified Communications Manager Business Edition
|
•Up to 30,000 phones per Cisco Unified Communications Manager instance
•Up to 240 phones per Cisco Unified Communications Manager Express instance.
|
•Up to 30,000 phones per Cisco Unified Communications Manager instance
|
Call Processing
|
•Cisco Unified Communications Manager
•Cisco Unified Communications Manager Express
•Cisco Unified Communications Manager Business Edition
|
•Cisco Unified Communications Manager
•Cisco Unified Communications Manager Business Edition (in central site)
•Cisco Unified Communications Manager Express for fixed remote teleworker applications (in central site)
•Unified SRST or Cisco Unified Communications Manager Express (as backup to Cisco Unified Communications Manager and Cisco Unified Communications Manager Business Edition)
|
•Cisco Unified Communications Manager (in one or more locations)
•Cisco Unified Communications Manager Express (in one or more locations)
|
•Cisco Unified Communications Manager (subscriber and backup)
|
Contact Center
|
•Cisco Unified Contact Center Enterprise
•Cisco Unified Contact Center Express
•Cisco Unified IP IVR
•Cisco Unified Customer Voice Portal
|
•Cisco Unified Contact Center Enterprise (based in head- quarters)
•Cisco Unified Contact Center Express (based in headquarters)
•Cisco Unified Customer Voice Portal (in head- quarters or branches)
|
•Cisco Unified Contact Center Enterprise (in one or more locations)
•Cisco Unified IP IVR
•Cisco Unified Customer Voice Portal
|
•Cisco Unified Contact Center Enterprise
•Cisco Unified Customer Voice Portal
|
Messaging
|
•Cisco Unity
•Cisco Unity Connection
•Cisco Unity Express
|
•Cisco Unity (based in head- quarters)
•Cisco Unity Connection
•Cisco Unity Express
|
•Cisco Unity (in one or more locations)
•Cisco Unity Connection
•Cisco Unity Express
|
•Cisco Unity
•Cisco Unity Connection
•Cisco Unity Express
|
Instant Messaging and Presence
|
•Cisco Unified Presence
|
•Cisco Unified Presence (in head- quarters)
|
•Cisco Unified Presence (in one or more locations)
|
•Cisco Unified Presence
|
Conferencing
|
•Cisco Unified Meeting- Place
•Cisco Unified Video- conferencing
|
•Cisco Unified Meeting- Place (based in head- quarters)
•Cisco Unified Video- conferencing
|
•Cisco Unified Meeting- Place (in one or more locations)
•Cisco Unified Video- conferencing
|
•Cisco Unified Meeting- Place
•Cisco Unified Video- conferencing
|
System Management
|
•Cisco Unified Operations Manager
•Cisco Unified Service Monitor
•Cisco Unified Service Statistics Manager
•Cisco Unified Provisioning Manager
•Cisco Monitor Manager and Monitor Director (for small or medium size deployments with Cisco Unified Communications Manager Express and or Cisco Unity Express)
•LAN Management Solution
|
Based in head- quarters:
•Cisco Unified Operations Manager
•Cisco Unified Service Monitor
•Cisco Unified Service Statistics Manager
•Cisco Unified Provisioning Manager
•Cisco Monitor Manager and Monitor Director (for monitoring deployments with Cisco Unified Communications Manager Express and Cisco Unity Express or Cisco Unified Communications Manager Express in SRST mode as backup to Cisco Unified Communications Manager)
•Cisco netManager
•LAN Management Solution
|
Distributed:
•Cisco Unified Operations Manager
•Cisco Unified Service Monitor
•Cisco Unified Service Statistics Manager
•Cisco Unified Provisioning Manager
•Cisco Monitor Manager and Monitor Director
•Cisco netManager
•LAN Management Solution
|
•Cisco Unified Operations Manager
•Cisco Unified Service Monitor
•Cisco Unified Service Statistics Manager
•Cisco Unified Provisioning Manager
•Cisco Monitor Manager and Cisco Monitor Director (for deployments of Cisco Unified Communications Manager Express in SRST mode as a backup to Cisco Unified Communications Manager)
•Cisco netManager
|
Off-Premises Calling
|
•PSTN via gateway
|
•Site to Site over IP WAN
•PSTN as backup for branch sites
|
•Site to Site over IP WAN
•PSTN for off-network calling
|
•Site to Site over IP WAN
|
