Tested Deployments and Site Models

Transcription

1 Tested Deployments and Cisco Unified Communications Release 9.0(1) testing for IP telephony was designed to test the hardware and software components that work together in a multisite distributed IP telephony deployment. For this testing, the following site models were created. Each site model was designed to test a specific set of features and interactions. The site models can be used in various combinations to create different versions of a multisite distributed deployment model. Site models: Multisite Centralized Call Processing with SRST Router (SFO-ORD) Campus (DFW and SJC/RFD) Multisite with Distributed Call Processing (ICT traffic between all sites, including (YYZ/ATL) Clustering Over the IP WAN (SJC/RFD sites and SFO/ORD) Unified Communications on Virtualized Servers (SJC/RFD and SFO/ORD) Call Routing and Dial Plan Distribution Using Call Control Discovery for the Service Advertisement Framework (MCI-LAX talking to SJC/RFD, SFO/ORD, DFW, ATL, and YYZ) Cisco Unified Communications Manager Session Manager Edition (MCI-LAX) Video Enhancements Large Multisite Centralized with Unified SRST (CDG) Medium Site Centralized with Unified SRST (GVA) Cisco Unified Communications Manager Session Management Edition (CDG-SME, GVA-SME; MLN-SME for Load Testing) Cisco Unified Communications Manager Interoperability Site (Cisco SIP Unified CME Site Aggregated by Cisco Unified SIP Proxy) (RKV) Small Campus Multisite H.323 (WAW) Mid-Market Multisite Centralized Site with Unified CMBE (MAN) Mid-Market Multisite Centralized Site with Cisco Business Edition 3000 (BLR) This topic describes each site model. 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: 1

2 Purpose of Solution Tests Tested Deployments and For a list of the release versions of the components used in the site models, see System Release Notes for IP Telephony: Cisco Unified Communications System, Release 9.0(1) This topic includes the following sections: Purpose of Solution Tests, page 2 Multisite Distributed Deployment Options, page 2, page 3 Purpose of Solution Tests An efficient, effective, and reliable IP telephony solution requires many interrelated hardware and software components. The site models that are described in this manual provide you with models and guidance as you implement an IP telephony system for your organization. Cisco has selected, installed, configured, and tested hardware and software designed to work together seamlessly and to provide a complete and optimized IP telephony solution. Each site model addresses some or all of the following issues: End-to-end functionality Operability in a real-world environment Scalability Stability Stress Load Redundancy Reliability Usability Availability Installability Upgradeability Serviceability Regression Negative Scenario Multisite Distributed Deployment Options The site models within each test group (North America and EUEM) can be implemented in various combinations to create deployment models to meet the needs of a wide range of organizations. For detailed information about the sites used in IP telephony deployments, see the. The Solution integration test bed topologies diagrams for NA and EUEM for IP telephony tested in Cisco Unified Communications Release 9.0(1) is available from the Resource Library tab of the Technical Information Site. 2

3 Tested Deployments and Different site models were created and tested for Cisco Unified Communications Release 9.0(1) testing for IP telephony. Each site model tested specific hardware and software components, features, functions, protocols, and related items. A site model includes one or more sites. Each site has a three-letter name (for example, SFO, ORD, and SJC). Examples throughout this manual refer to these site names. The following sections describe each site model in detail. Each section includes an explanation of the design characteristics of the site model, and includes a table that lists the hardware and software components used in the model. The tables contain the following information for each component: Component Hardware or software component Description Information such as model number release number, protocol, and hardware platform Qty. Quantity of the component used in the model Table 1 lists the site models and references to sections that provide detailed information. Table 1 Site Model and Reference Multisite Centralized Call Processing with SRST Router Campus Multisite with Distributed Call Processing Clustering Over the IP WAN Unified Communications on Virtualized Servers Call Routing and Dial Plan Distribution Using Call Control Discovery for the Service Advertisement Framework Sites Included San Francisco (SFO), Chicago (ORD) San Jose (SJC), Rockford (RFD), and Dallas (DFW) ICT traffic between all sites, including the CME sites Toronto (YYZ), and Atlanta (ATL) San Jose (SJC), Rockford (RFD), and San Francisco (SFO), Chicago (ORD) San Jose (SJC), Rockford (RFD), and San Francisco (SFO), Chicago (ORD) Kansas City (MCI), Los Angeles (LAX) talking to San Jose (SJC), Rockford (RFD), San Francisco (SFO), Chicago (ORD), Dallas (DFW), Toronto (YYZ) and Atlanta (ATL) 3

4 Tested Deployments and Table 1 (continued) Site Model and Reference Cisco Unified Communications Manager Session Management Edition Site Kansas City (MCI), Los Angeles (LAX) Large Multisite Centralized with Unified SRST Paris (CDG) Medium Site Centralized with Unified SRST Geneva (GVA) Cisco Unified Communications Manager Session Management Edition Cisco Unified Communications Manager Interoperability Site (Cisco SIP Unified CME Site Aggregated by Cisco Unified SIP Proxy) Small Campus Multisite H.323 Mid-Market Multisite Centralized (Unified CMBE) Mid-Market Multisite Centralized (Cisco Business Edition 3000) Sites Included Co-located in Paris (CDG-SME) and Geneva (GVA-SME); Milan (MLN-SME) for Load testing Reykjavik (RKV) Warsaw (WAW) Manchester (MAN) Bangalore (BLR) Multisite Centralized Call Processing with SRST Router The Multisite Centralized Call Processing with Remote Site Survivability (SRST Router) site model represents a very large financial company deployment in which two sites, San Francisco (SFO) and Chicago (ORD), are used to cluster Cisco Unified Communications Manager over an IP WAN. In this model, half of the cluster resides in SFO and the other half in ORD. These sites provide centralized call processing to remote Cisco Unified Survivable Remote Site Telephony (Unified SRST) sites. Communication with remote sites takes place over the IP WAN. Remote sites are connected to the WAN. Each site supports approximately equal volumes of network traffic, and each is capable of carrying 100 percent of the traffic in the event of a failure in the other's network. Cisco 2800, 3800, and 2900 series Integrated Services Routers are configured with Hot Standby Routing Protocol (HSRP) and Survivable Remote Site Telephony (SRST). For load sharing between the sites, Multi-group HSRP (MHSRP) is configured. The Cisco Integrated Services Routers provide gateway connectivity to Public Switched Telephone Network (PSTN) providers using T1/E1 primary rate interfaces (2 PRIs). Each remote site is connected to a Cisco Catalyst 37xx series Switch, which connects VoIP endpoints to remote sites, and also includes Power over Ethernet features to power Cisco IP Phones. Packets marking is also done at Cisco Catalyst 37xx Series using Modular QoS CLI (MQC) based configuration using class-map and policy-map. The tested Multisite Centralized site model has the following design characteristics: The site model contains a single Unified Communications Manager cluster. Some centralized call processing deployments may require more than one Cisco Unified Communications Manager cluster. For instance, if scale calls for more endpoints than can be serviced by a single cluster or if a cluster needs to be dedicated to an application such as a call center. For smaller deployments, Cisco Business Edition 3000 may be deployed in centralized call processing configurations for up to 9 remote sites. Cisco Unified Communications Manager Business Edition 5000 or Cisco Unified Communications Manager Business Edition 6000 may be deployed in centralized call processing configurations for up to 19 remote sites. 4

5 Tested Deployments and Maximum of 30,000 configured and registered Skinny Client Control Protocol (SCCP) or Session Initiation Protocol (SIP) IP phones or SCCP video endpoints per cluster. Maximum of 2,000 locations or branch sites per Cisco Unified Communications Manager cluster. Maximum of 2,100 gateways and trunks (that is, the total number of H.323 gateways, H.323 trunks, digital MGCP devices, and SIP trunks) per Cisco Unified Communications Manager cluster. PSTN connectivity for all off-net calls. Digital Signal Processor (DSP) resources for conferencing, transcoding, and Media Termination Point (MTP) are distributed locally to each site to reduce WAN bandwidth consumption on calls requiring DSPs. Capability to integrate with legacy private branch exchange (PBX) and voic systems. Interfaces to legacy voice services such as PBXs and voic systems can connect within the central site, with no operational costs associated with bandwidth or connectivity. Connectivity to legacy systems located at remote sites may require the operational expenses associated with the provisioning of extra WAN bandwidth. The system allows for the automated selection of high-bandwidth audio (for example, G.711, G.722, or Cisco Wideband Audio) between devices within the site, while selecting low-bandwidth audio (for example, G.729 or G.728) between devices in different sites. The system allows for the automated selection of high-bandwidth video (for example, 384 Kbps or greater) between devices in the same site, and low-bandwidth video (for example, 128 Kbps) between devices at different sites. The Cisco Unified Video Advantage Wideband Codec, operating at 7 Mbps, is recommended only for calls between devices at the same site. A minimum of 768 kbps or greater WAN link speed should be used when video is to be placed on the WAN. Cisco Unified Communications Manager locations (static or RSVP-enabled) provide call admission control. For voice and video calls, Automated Alternate Routing (AAR) provides the automated rerouting of calls through the PSTN when call admission control denies a call due to lack of bandwidth. AAR relies on a gateway being available to route the call from the calling phone toward the PSTN, and another gateway to accept the call from the PSTN at the remote site, to be connected to the called phone. Call Forward Unregistered functionality provides the automated re-routing of calls through the PSTN when an endpoint is considered unregistered due to a remote WAN link failure. Call Forward Unregistered relies on a gateway being available to route the call from the calling phone toward the PSTN, and another gateway to accept the call from the PSTN at the remote site, to be connected to the called phone. Survivable Remote Site Telephony (SRST) for video. SCCP video endpoints located at remote sites become audio-only devices if the WAN connection fails. Cisco Unified Communications Manager Express (Unified CME) may be used for remote site survivability instead of an SRST router. Cisco Unified Communications Manager Express (Unified CME) can be integrated with the Cisco Unity server in the branch office or remote site. The Cisco Unity server is registered to the Unified CM at the central site in normal mode and can fall back to Unified CME in SRST mode when Unified CM is not reachable, or during a WAN outage, to provide the users at the branch offices with access to their voic with MWI. Figure 1 provides an overview of the Multisite Centralized Call Processing with SRST site model. 5

6 Tested Deployments and Figure 1 Multisite Centralized, Call Processing with SRST Model Table 2 lists the hardware and software components used in the Multisite Centralized, Clustering over the WAN with Unified SRST site model. Table 2 Multisite Centralized, Clustering over the WAN with Unified SRST Components Nexus Nexus Nexus Nexus 2000 Series Fabric Extender 2 Catalyst Voice Gateways Catalyst 6509 Switch with Supervisor 2 2 Cisco FlexWAN module with 2 Port Adaptor slots 2 48-Port, RJ-45, 10/100BaseTX Ethernet with 2 in-line power Central Core Switch Catalyst 6506 Switch with Supervisor 2 2 Cisco Unified Communications Manager Cisco Unified Computing System 5 Servers Cisco UCS C-Series Rack Mount Server 7 6

7 Tested Deployments and Table 2 Multisite Centralized, Clustering over the WAN with Unified SRST Components Cisco Unity Connection Cisco Unified Computing System 2 Cisco MCS 7845 Unified Communications 1 Manager Appliance Cisco Unified Instant Messaging/Presence Cisco Unified Computing System 2 Servers Music on Hold server Cisco Unified Computing System 1 Cisco UCS C-Series Rack Mount Server 1 TFTP server Cisco Unified Computing System 1 Cisco UCS C-Series Rack Mount Server 1 Router Cisco Cisco Cisco Cisco Cisco Cisco VXR 2 Cisco Cisco Campus The Campus site model represents a very large campus in which two sites, San Jose (SJC) and Rockford (RFD), are used to cluster Cisco Unified Communications Manager over an IP WAN. This site also supports RSVP cluster. The Cisco Unified Communications Manager cluster in this site model consists of the following: One publisher Ten subscribers (five in each site) Two Music on Hold servers (one in each site) Two TFTP servers (one in each site) The campus site model also consists of another site called Dallas (DFW). This site includes a Cisco Unified Communications Manager cluster that includes the following: One publisher Four subscribers Music on Hold and TFTP servers (one each) This deployment model has the following characteristics: This deployment model has a single Cisco Unified Communications Manager cluster. Some campus call processing deployments may require more than one Unified CM cluster, for instance, if scale calls for more endpoints than can be serviced by a single cluster or if a cluster needs to be dedicated to an application such as a call center. 7

8 Tested Deployments and Maximum of 30,000 configured and registered Skinny Client Control Protocol (SCCP) or Session Initiation Protocol (SIP) IP phones or SCCP video endpoints per Unified CM cluster. Maximum of 2,100 gateways and trunks (that is, the total number of H.323 gateways, H.323 trunks, digital MGCP devices, and SIP trunks) per Unified CM cluster. Trunks and/or gateways (IP or PSTN) for all calls to destinations outside the campus. Co-located digital signal processor (DSP) resources for conferencing, transcoding, and media termination point (MTP). Other Unified Communications services, such as messaging (voic ), presence, and mobility are typically co-located. Interfaces to legacy voice services such as PBXs and voic systems are connected within the campus, with no operational costs associated with bandwidth or connectivity. High-bandwidth audio is available (for example, G.722 or Cisco Wideband Audio) between devices within the site. High-bandwidth video (for example, 384 kbps or greater) is available between devices within the site. The Cisco Unified Video Advantage Wideband Codec, operating at 7 Mbps, is also supported. Figure 2 shows the topology of the Campus site model. Figure 2 Campus Table 3 lists the hardware and software components used in the Campus site model. 8

9 Tested Deployments and Table 3 Campus Nexus Nexus Nexus Nexus 2000 Series fabric 7 Extender Access switch Cisco Catalyst 6509 with dual 1 Supervisor 2 Cisco Analog gateway Cisco VG248 3 Cisco VG224 1 Cisco Unified Communications Manager server Cisco Unified Instant Messaging/Presence server Cisco Contact Center Express servers Cisco Unified MeetingPlace IP GW server Cisco Unified MeetingPlace server Cisco Unified MeetingPlace Web Conferencing Server Cisco Unity Unified Messaging server Core/Distribution Switch Cisco UCS C-Series Rack-Mount Servers Cisco Unified Computing System C-Series Cisco Unified Computing System Cisco MCS 7845 Unified Communications Manager Appliance Cisco MCS 7845 Unified Communications Manager Appliance Cisco MCS 7845 Unified Communications Manager Appliance Cisco MCS 7845 Unified Communications Manager Appliance Cisco MCS 7845 Unified Communications Manager Appliance Cisco Catalyst 6506 with Supervisor 2 and 2-port DS3 module Data Center Switch Cisco Cisco DNS/DHCP server Cisco MCS 7845 Unified Communications Manager Appliance 2 Domain controller Cisco MCS 7845 Unified Communications Manager Appliance

10 Tested Deployments and Table 3 Campus Exchange 2000 server Cisco MCS EVV1 Unified Communications Manager Appliance Cisco MCS-7845H-2.4-ECS2 Unified Communications Manager Appliance Gatekeeper Cisco Gateway Cisco 3845 (H.323) 3 Cisco 3945 (MGCP) 2 Cisco 3925 (SIP) 2 Music on hold (MOH) server Cisco MCS 7825 Unified Communications Manager Appliance 2 T1 gateway TFTP server Cisco UCS C-Series Rack-Mount Servers WAN router Cisco 7206 VXR 1 E2E RSVP Agent Cisco Figure 3 shows the topology of the Dallas (DFW) Site model. 10

11 Tested Deployments and Figure 3 DFW Site Model Multisite with Distributed Call Processing The model for a multisite deployment with distributed call processing consists of multiple independent sites, each with its own call processing agent cluster connected to an IP WAN that carries voice traffic between the distributed sites. One of these sites is called Atlanta (ATL). This site includes: Two Cisco Unified Communications Manager Express routers 100 SIP endpoints Another site is called Toronto (YYZ). This site includes: Two Cisco Unified Communications Manager Express routers One H.323 gatekeeper 265 SCCP endpoints The remainder of this model consists of Intercluster Trunk (ICT) traffic between the SFO/ORD, SJC/RFD, and DFW clusters. H.323 gatekeeper controlled trunks and SIP trunks are used. Location-based and End-to-End RSVP call admission control are also included in testing. Figure 4 shows the topology of the Campus site model. 11

12 Tested Deployments and Figure 4 Multisite with Distributed Call Processing Model Clustering Over the IP WAN The Clustering over the IP WAN site model is used in the implementation of the SJC/RFD, SFO/ORD, and MCI-LAX clusters. It is possible to deploy a single Unified Communications Manager cluster across multiple sites that are connected by an IP WAN with QoS features enabled. Clustering over the WAN can support two types of deployments: 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 type of deployment is ideal for two to four sites with Cisco 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 type of deployment, you may have up to eight sites with Cisco Unified Communications Manager subscribers being backed up by Cisco Unified Communications Manager subscribers at another site. A combination of the two deployment models can be used 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. 12

13 Tested Deployments and Unified Communications on Virtualized Servers The clusters for SFO/ORD, SJC/RFD and parts of MCI/LAX run on virtual machines hosted on Cisco UCS B-Series Blade Servers and Cisco UCS C-Series Rack-Mount Servers. SAN based storage is used for the B-series servers and both SAN and direct attached (disk) storage are used with the C-series servers. One publisher/tftp/moh Server One subscriber This site supports a mix of 1000 SIP and SCCP endpoints. Call Routing and Dial Plan Distribution Using Call Control Discovery for the Service Advertisement Framework The Call Routing and Dial Plan Distribution Using Call Control Discovery for the Service Advertisement Framework site model consists of sites Kansas City (MCI), Los Angeles (LAX) talking to San Jose (SJC)/Rockford (RFD), San Francisco (SFO)/Chicago (ORD), Dallas (DFW), Toronto (YYZ) and Atlanta (ATL). When multiple call processing agents are present in the same system, each can be configured manually to be aware of the others. This configuration can be time consuming and error prone. Call routing between the various call processing agents requires the configuration of static routes on the call agents and updating them when changes occur. Instead, the Cisco Service Advertisement Framework (SAF) can be used to share call routing and dial plan information automatically between call agents. SAF allows non-cisco call agents (such as TDM PBXs) to partake in the Framework when they are interconnected through a Cisco IOS gateway. Table 4 lists the hardware and software components used in the Cisco Service Advertisement Framework (SAF) Site. Table 4 Cisco Service Advertisement Framework Site Cisco Unified Communications Manager server Cisco MCS 7825 Unified Communications Manager Appliance SAF Forwarder (HUB) Cisco SAF Forwarders (neighbors) Cisco SAF-Forwarder (DUAL in SFO) Cisco Site switch Cisco WAN router Cisco Cisco Unified Communications Manager Session Management Edition Site The Cisco Unified Communications Manager - Session Management Edition site model contains two sites, Kansas City (MCI) and Los Angeles (LAX), designed to simulate Session Management Edition of the Unified Communications 8.5 system train. This cluster includes: 13

14 Tested Deployments and One publisher and one subscriber (MCI) Two subscribers (LAX) This deployment model has the following characteristics: Mix platform with MCS and UCS MCI site has IBM MCS servers, and LAX site has one IBM MCS server, and one UCS B-series based virtual server. Distributed call processing deployment model with Clustering over the IP WAN configuration. All non-saf ICT SIP and H.323 (Non Gatekeeper) trunks configured on Session Management Edition use Call routing enhancement option to run SIP trunks on every subscriber node in the cluster. All SIP trunks configured on Session Management Edition cluster use SIP option PING to track the status of the configured destination of SIP trunks and only send SIP messages to reachable remote peers. SIP Early Offer Enhancement option is enabled on selected SIP trunks in Session Management Edition and on leaf clusters. End-to-end (E2E) RSVP Call Admission Control In Session Management Edition test bed topology, there is only signaling traffic, and no media traffic between Session Management Edition and leaf clusters. All calls coming in from the leaf clusters and going out to the leaf clusters are not subjected to the location Call Admission Control in Session Management Edition. RSVP agents on leaf clusters represent locations between leaf clusters, and are subjected to the RSVP Call Admission Control. Calls between SJC and DFW leaf clusters perform E2E RSVP Call Admission Control. The Service Advertisement Framework (SAF) deployed in the test bed, co-exists with the Session Management Edition cluster and enables leaf nodes to discover automatically other network services run on other leaf nodes through centralized Session Management Edition cluster. Cisco Unified Border Element Scalability and Load Balancing Cisco Unified SIP Proxy is used to provide a central route point for management of pair of Cisco Unified Border Elements, MCI-CUBE-1 and MCI-CUBE-2 in MCI side and LAX-CUBE-1 and LAX-CUBE-2 in LAX side of Session Management Edition cluster. In Cisco Unified SIP Proxy, load balancing and rule-based routing is applied for ingress and egress traffic. Each pair of the Cisco Unified Border Element uses same configuration. If a Cisco Unified Border Element is unavailable, Cisco Unified SIP Proxy can intelligently re-route to an alternate Cisco Unified Border Element. When the Cisco Unified Border Element returns to service, Cisco Unified SIP Proxy resumes sending traffic to the Cisco Unified Border Element. Figure 5 shows the topology of this site. 14

15 Tested Deployments and Figure 5 Cisco Unified Communications Manager Session Management Edition (SME) Site Topology Table 5 lists the hardware and software components used in this model. Table 5 Cisco Unified Communications Manager Session Management Edition (SME) Components Cisco Unified Communications Manager servers Cisco MCS 7845 Unified Communications Manager Appliance UCS (Unified Computing 1 Systems on B-Series) Distribution Switch WS-C3750G-48PS 2 Wan Router Cisco 7206VXR (NPE-G1) 1 Cisco Unified Border Cisco Element Cisco Unified SIP Proxy Cisco 3845 ISR with NM - Cisco Unified SIP Proxy

16 Tested Deployments and Table 5 Cisco Unified Communications Manager Session Management Edition (SME) Components Pagent Cisco 7206VXR (NPE-G1) for 1 Delay Generation SIP IP PSTN SIP Trunking Tool 1 Video Enhancements During this Release, additional video testing is included in all of the site models. Testing included adding new Tandberg video endpoints and the Cisco TelePresence System Calls between the various video endpoints, including intra-cluster calls and intercluster calls, were tested along with supplementary services such as conference, transfer, and hold. Large Multisite Centralized with Unified SRST The Large Multisite Centralized with Unified SRST site model consists of one site called Paris (CDG). This site model represents an international deployment with up to 21 remote sites deployed across various countries. It includes Cisco Unity Connection and third-party components. Cisco Unified Communications Manager uses QSIG, H.323, and SIP to interoperate between sites. Remote sites are interconnected through the WAN and all are RSVP-enabled to the central site. For Geneva (GVA) and Paris (CDG), inter cluster RSVP is enabled. In this model, a Cisco Unified Communications Manager cluster serves 6000 phone in local and remote locations, with all endpoints and gateways fully encrypted (RTP and signaling). PBXs that support the QSIG ISO and QSIG ECMA variants connect to this cluster through direct QSIG links. The Cluster connects to the rest of the network through MPLS WAN networks. Calls between the CDG site, the LGW site, and the MAD site are provided by H.323 intercluster trunks. Cisco Unity Connection provides voice messaging. PBX users access voice messaging features through the QSIG trunks to Cisco Unified Communications Manager. Access to the PSTN for normal off-net calls is provided by ten E1 ETSI PRI links to the PSTN. Remote sites have either centralized breakout to the PSTN or local PSTN breakout using E1 PRI, BRI, or FXO connections. PSTN access is controlled by Cisco Unified Communications Manager using MGCP, H.323, or SIP. Unified SRST is used in each remote site. Access to the SIP network is provided through a SIP trunk to a remote Cisco Unified SIP Proxy (CUSP). Access to third-party services such as operator console, if available, is provided locally. Some of the sites will also have video endpoints and Cisco Unified Videoconferencing Gateways, and remote QSIG PBXs. Cisco Unified Communications Integration for Microsoft Office Communicator and Cisco Unified Presence Server are tested as part of this site model. Cisco Unified Communications Integration for Microsoft Office Communicator provides interoperability with Microsoft Office Communicator Server 2007 (OCS) R2 version with Microsoft Office Communicator (MOC) clients. The Large Multisite Centralized with Unified SRST site model have these design characteristics: Cisco Unified Communications Manager cluster for redundancy and system scaling Inline power to IP Phones Encryption of RTP, SIP, SCCP, and H.323 where available SIP and SCCP phones 16

17 Tested Deployments and Cisco Unified Communications Integration for Microsoft Office Communicator with Microsoft OCS 2007 R2 version with Microsoft Office Communicator clients Cisco Unified Enterprise Attendant Console Windows 2008 server on Cisco MCS 7825 Unified Communications Manager Appliance Cisco Unified Personal Communicator Quality of service from the desktop Video phones, MCUs, and Cisco Unified Videoconferencing H.320 Gateways in local and remote sites Locally connected third-party applications for attendant console Cisco Unity Connection connected through an SCCP link to Cisco Unified Communications Manager PBX connectivity to Cisco Unified Communications Manager and Cisco Unity through Cisco Unified Communications Manager using a direct QSIG trunks QSIG feature transparency between PBXs to PBX, PBX to Cisco Unified Communications Manager, Cisco Unified Communications Manager to PBX, and Cisco Unified Communications Manager to Cisco Unified Communications Manager clusters Cisco IME server to transport all Cisco IME calls over Cisco IME SIP trunks. Cisco Unified Communications Manager Session Management Edition to consolidate SIP trunks and application interfaces across multi vendor voice deployments Service Advertisement Framework (SAF) to advertise the DN pattern of Cisco Unified Communications Manager and Cisco Unified Communications Manager Express through Call Control Discovery so that other call control entities have access through the SAF network, thereby adapting their routing behavior. Central and remote PSTN breakout for remote sites with MGCP PRI, BRI, and FXO backhaul, and SIP and H.323 control Cisco RSVP Agent Figure 6 shows the topology of the Large Multisite Centralized with Unified SRST Site model. 17

18 Tested Deployments and Figure 6 Large Multisite Centralized with Unified SRST Site Topology Table 6 lists the hardware and software components used in the Multisite Centralized, Clustering over the WAN with Unified SRST site model. Table 6 Large Multisite Centralized with Unified SRST Site Model Components Datacenter Catalyst switch WS-C6509-E 3 Analog gateway Cisco ATA 187 Analog Telephone Adaptor 3 18

19 Tested Deployments and Table 6 Large Multisite Centralized with Unified SRST Site Model Components (continued) Cisco Unified Communications Manager Server Cisco UCS B Series 7, Cisco Wallop C210M2-2, MCS 7835 Unified Communications Manager Appliance - 4 Firewall-ASA Data center Cisco IME Cisco Unified SRST Routers Cisco Cisco Cisco Cisco Cisco Cisco Cisco Cisco Cisco Cisco Cisco Unified Contact Center Express Cisco B-series 2 Cisco Unified IP Phone Cisco Unified IP Phone 7971G-GE 10 Cisco Unified IP Phone 7970G 10 Cisco Unified IP Phone 7961G/7961G-GE 5 Cisco Unified IP Phone 7941G/7941G-GE 5 Cisco Unified IP Phones models 6921, 6941, 5 and 6961 Cisco Unified IP Phone Cisco Unified IP Phone Cisco IP Communicator 2 Cisco Unified Communications Integration 6 for Microsoft Office Communicator Cisco Unified Personal Communicator 2 Cisco Unified IP Phones Cisco Unity Connection Cisco B-series 2 Core Catalyst chassis WS-C6506-E 2 RSVP Agent Cisco Cisco E1 gateway card Cisco

20 Tested Deployments and Table 6 Large Multisite Centralized with Unified SRST Site Model Components (continued) Gateway Cisco Cisco Cisco Cisco Cisco Cisco Cisco Cisco Cisco PSTN Gateway Cisco Access switch WS-C PWR-SMI 3 WS-C PS-S 3 WS-C PS-S 2 Router Cisco 7206-VXR 1 Video conferencing Cisco Unified Videoconferencing MCU Video endpoint Cisco Unified Video Advantage 4 Cisco IP Phone Cisco Unified IP Phones models 9951 and 9971, Tandberg E20, Tandberg EX90 and Tandberg MXP Tandberg Codian MCU Tandberg Codian Video MCU and Gateway IPVC-3545-CHAS 1 1. Divided into two Unified Communications Manager clusters: one main cluster consisting of 11 servers and a second smaller cluster of two servers supporting the Cisco Unified Contact Center Express server and agent phones. Medium Site Centralized with Unified SRST The Medium Site model consists of one centralized site with three SRST remote sites called Geneva (GVA). In this model, a Cisco Unified Communications Manager cluster serves 2000 phones. The Cisco Unified Communications Manager cluster connects to the rest of the network through MPLS WAN networks. A local Cisco Unity Connection provides voice messaging services for local PBX and Cisco Unified Communications Manager users. Access to the PSTN for normal off-net calls is provided by five E1 RTSI PRI links to the PSTN. Access to other sites and to services such as Cisco Unified MeetingPlace Express is provided by H.323 gatekeeper controlled trunks and an IP-to-IP gateway. Access to the SIP network is through a SIP trunk to a remotely located Cisco Unified SIP Proxy (CUSP). Third-party operator consoles are provided on Cisco Unified Communications Manager to serve local phones and to provide backup to the operator console in the CDG site. The Medium Site model has these design characteristics: Cisco Unified Communications Manager cluster for redundancy and system scaling 20

21 Tested Deployments and Inline power to IP Phones SIP and SCCP phones Quality of service from the desktop Locally connected third-party applications for attendant console, billing, and voice recording, if available Cisco Unified Communications Integration for Microsoft Office Communicator with Microsoft OCS 2007 R2 version with Microsoft Office Communicator clients Cisco Unified Personal Communicator Cisco IME server to transport all Cisco IME calls over Cisco IME SIP trunks. Cisco Unified Communications Manager Session Management Edition to consolidate SIP trunks and application interfaces across multi vendor voice deployments Service Advertisement Framework (SAF) to advertise the DN pattern of Cisco Unified Communications Manager and Cisco Unified Communications Manager Express through Call Control Discovery so that other call control entities have access through the SAF network, thereby adapting their routing behavior. Cisco RSVP agent is enabled Cisco Unified Communications Integration for Real Time exchange and Real Time exchange (RTX) server. VG30D Figure 7 shows the topology of the EUEM Medium Site model (GVA). 21

22 Tested Deployments and Figure 7 EUEM Medium Site Topology Table 7 lists the hardware and software components used in the Medium Site model. Table 7 Medium Site Model Components Datacenter Catalyst switch WS-C6509-E 2 Cisco Unified Communications Manager Server Cisco Unified Computing System C210 M2 Wallop Server Cisco Intercompany Media Engine on 7925 server

23 Tested Deployments and Table 7 Medium Site Model Components (continued) Unity Connection Cisco Unified Computing System C210M2 Wallop Server, Cisco Unified Presence on Cisco UCS 210 M2 Wallop Server ASA Data center ASA Cisco IME ASA Cisco Unified IP Phone Cisco Unified IP Phone 7971G-GE 2 Cisco Unified IP Phone 7970G 2 Cisco Unified IP Phone 7961G/7961G-GE 2 Cisco Unified IP Phone 7941G/79461G-GE 2 Cisco Unified IP Phones models 6921, 6941, 6 and 6961 Cisco IP Communicator 1 Cisco Unified Communications Integration 1 for Microsoft Office Communicator Cisco Unified IP Phones models Video endpoints Cisco Unified Video Advantage 1 Cisco Cisco Unified IP Phones models 9951 and Tandberg E20, EX90, and Cisco MXP Cisco TelePresence System Cisco Unity Connection Cisco MCS 7845 Unified Communications 1 Manager Appliance Remote Unified SRST sites Cisco Cisco Cisco PSTN Gateway Cisco Access Switch WS-C PWR-SMI 1 WS-C PS-S 1 Router Cisco 7206-VXR 1 RSVP Agent Cisco Cisco TelePresence Video Communications 1 Server Tandberg Codian MCU Codian 4501 MCU 1 Tandberg Codian ISDN Gateway Codian 3241 Gateway

24 Tested Deployments and Cisco Unified Communications Manager Session Management Edition Milan (MLN-SME) Site The Cisco Unified Communications Manager Session Management Edition deployment is a variation of multisite distributed call processing deployments model, which interconnects large numbers of Cisco Unified Communications systems. In the EUEM sites, the Cisco Unified Communications Manager Session Management Edition deployments consist of two sites: Paris (CDG-SME) and Geneva (GVA-SME). For load testing, another site called Milan (CDG-SME) is used. The MLN-SME cluster is a centralized Session Manager Edition cluster. The MLN-SME cluster consists of MLN (Unified CM servers), MLN Cisco Unity Connection server, and PSTN. The MLN-SME cluster is connected to CDG, GVA, MAD, and RKV leaf through SAF enabled QSIG over SIP trunks. The MLN-SME cluster is connected to CDG, LGW, and GVA, through H.323 Annex M1 trunk. The IPT-SI deployment for Cisco Unified Communications Manager Session Management Edition can be explained as follows: In this deployment there are two Cisco Unified Communications Manager Session Management Edition clusters namely CDG-SME cluster and GVA-SME cluster. CDG-SME cluster is co-located with CDG site and aggregates trunks (SIP, H.323, QSIG, and QSIG over SIP) from the CDG leaf node, MAD leaf node and LGW leaf node. The GVA-SME cluster is co-located with GVA site and aggregates trunks (SIP, H.323, QSIG, and QSIG over SIP) from the GVA leaf node, and RKV leaf node and BRU leaf node. CDG-SME cluster and its leaf nodes (CDG, CDG-remote, and MAD) are running in the SAF Autonomous system 333 and GVA-SME cluster and its leaf nodes (GVA, RKV, and BRU) are running in the SAF Autonomous system 444, at present we have not enabled static re-distribution between the two SAF Autonomous systems. Cisco Unity Connection server provides voice mail services to Unified CM, Unified CM-SME, and remote users. Service Advertisement Framework (SAF) and Session Management Edition (SME) Setup: SAF allows networking applications to discover the existence, location, and configuration of network services (Call Control Discovery) within networks by using the underlying network as a transport for service advertisements. Cisco Unified Communications Manager Session Management Edition: Cisco Unified Communications Manager Session Management Edition is essentially a Cisco Unified Communications Manager cluster supporting a large number of trunk interfaces and enables the aggregation of multiple Unified Communications systems using multiple trunk types for voice, video, and fax calls. The focus of SAF testing for Troy release is centered on combining the CUCM-SME (Centralized Architecture) and SAF (Distributed Architecture). The MLN-SME cluster is a centralized Session Manager Edition cluster. The MLN-SME consists of MLN (Unified CM servers), MLN Cisco Unity Connection server, and PSTN. The MLN-SME cluster is connected to CDG, GVA, MAD, and RKV leaf through SAF enabled QSIG over SIP trunks. The MLN-SME cluster is connected to CDG, LGW, and GVA through H.323 Annex M1 trunk. The MLN-SME cluster Site model has these design characteristics: GVA-SME cluster (Cisco Unified Communications Manager Session Management Edition servers) Cisco Unity Connection for voic PSTN Gateway 24

25 Tested Deployments and Paris (CDG-SME) Site Geneva (GVA-SME) site The CDG-SME cluster consists of CDG leaf cluster (Cisco Unified Communications Manager Servers), Cisco Unity Connection server, Gateways, and Gatekeepers. The CDG-SME cluster is connected to MAD leaf cluster through a QSIG SIP trunk and to the LGW leaf cluster through H.323 Annex M1 trunks. There are two QSIG SIP trunks configured between CGD leaf and CDG-SME cluster and also between CDG-SME and MAD leaf cluster. One of the SIP trunks is a SAF enabled SIP trunk and the other is a static SIP trunk. When a call is made from CDG (leaf) to MAD (leaf) through CDG-SME cluster, first leg from CDG (leaf) to CDG-SME cluster will be SAF trunk and second leg from CDG-SME cluster to MAD (leaf) will be static SIP (QSIG) trunk. The CDG-SME cluster Site model has these design characteristics: CDG Leaf cluster (Unified Communications Manager servers) CDG-SME cluster (Unified Communications Manager Session Management Edition servers) Cisco Unity Connection for voic Gateways (Cisco Unified Border Element, Cisco 3545 MCU) and Gatekeepers (Cisco 3845) Static QSIG SIP trunk between CDG leaf and CDG-SME cluster SAP enabled QSIG SIP trunk between CDG leaf and CDG-SME cluster Static QSIG SIP trunk and SAP enabled QSIG SIP trunk between CDG-SME and MAD leaf cluster H.323 Annex M1 trunk between CDG-SME cluster and LGW leaf The GVA-SME cluster consists of GVA leaf cluster (Unified Communications Manager Servers), Cisco Unity Connection server, Gateways, and Gatekeepers. The GVA-SME cluster is connected to RKV leaf through SAF enabled SIP trunks and to the BRU leaf through both static SIP trunk and SAF enabled SIP trunk. The GVA-SME cluster Site model has these design characteristics: GVA Leaf cluster (Unified Communications Manager servers) GVA-SME cluster (Unified Communications Manager Session Management Edition servers) Cisco Unity Connection for voic Gateways (Cisco Unified Border Element) and Gatekeepers (Cisco 3845) Static QSIG SIP trunk between GVA leaf and GVA-SME cluster SAP enabled QSIG SIP trunk between GVA leaf and GVA-SME cluster Static QSIG SIP trunk and SAP enabled QSIG SIP trunk between GVA-SME and BRU leaf cluster SAP enabled QSIG SIP trunk between GVA-SME cluster and RKV leaf Analog Gateway (VG30D) Figure 8 shows the topology of the Unified Communications Manager Session Management Edition deployment model (EUEM site). 25

26 Tested Deployments and Figure 8 Unified Communications Manager Session Management Edition deployment model (EUEM) site Topology Table 8 lists the hardware and software components used in the Unified Communications Manager Session Management Edition deployment model (EUEM site). Table 8 Unified CM Session Management Edition deployment model Site Components CDG-SME cluster Datacenter Catalyst Switch Cisco Unified Communications Manager server Cisco Unified Communications Manager Session Management Edition server Cisco Unity Connection Cisco MCS 7835 Unified Communications Manager Appliance Cisco MCS 7835 Unified Communications Manager Appliance Cisco MCS 7845 Unified Communications Manager Appliance

27 Tested Deployments and Table 8 Unified CM Session Management Edition deployment model Site Components Gateways MGCP and SIP (Cisco 3845) 2 Cisco Unified Border Element 1 MCU (Cisco 3545) 1 QSIG Phones 2 Remote Routers 3 Gatekeeper 1 GVA-SME cluster Datacenter Catalyst Switch Cisco Unified Communications Manager server Cisco Unified Communications Manager Session Management Edition server Cisco Unity Connection Cisco MCS 7835 Unified Communications Manager Appliance Cisco MCS 7835 Unified Communications Manager Appliance Cisco MCS 7845 Unified Communications Manager Appliance Gateways VG30D 1 SIP (Cisco 3845) 1 Cisco Unified Border Element 1 Gatekeeper 1 QSIG Phones MLN-SME cluster Datacenter Catalyst switch WS-C6509-E 1 Cisco Unified Communications Manager server Cisco Unity Connection Cisco Unified Computing System B200 M2 Blade Server (UCS B200 M2) Cisco Unified Computing System B200 M2 Blade Server (UCS B200 M2) PSTN Gateway Cisco Cisco Unified Communications Manager Interoperability Site (Cisco SIP Unified CME Site Aggregated by Cisco Unified SIP Proxy) The Small Campus SIP only Multisite model consists of one site called Reykjavik (RKV). This model includes three Cisco Unified Communications Manager Express (Unified CME) sites aggregated by a Cisco Unified SIP Proxy (CUSP) module running on a Cisco 3825 gateway router. The Cisco Unified SIP Proxy is a high-performance, highly available stateless Session Initiation Protocol (SIP) server for centralized routing and SIP signaling normalization. Each Cisco Unified Communications Manager Express is connected to Cisco Unified SIP Proxy module through SIP trunks. The Cisco Unified SIP Proxy is connected to other Unified Communications Manager clusters in CDG and GVA sites through 27

28 Tested Deployments and SIP trunks. SIP RSVP features are configured on the Cisco Unified Communications Manager Express routers for RSVP between Cisco Unified Communications Manager Express phones and Cisco Unified Communications Manager cluster phones. The Small Campus SIP only Multisite model has these design characteristics: Inline power to IP Phones Remote access to other Cisco Unified Communications Manager clusters (CDG and GVA) through SIP trunks RSVP between Cisco Unified Communications Manager Express phones and Cisco Unified Communications Manager cluster phones Figure 9 shows the topology of the Non-Cisco Unified Communications Manager Interoperability Site model. Figure 9 Non-Cisco Unified Communications Manager Interoperability Site Topology Table 9 lists the hardware and software components used in the Non-Cisco Unified Communications Manager Interoperability Site model. 28

29 Tested Deployments and Table 9 Non-Cisco Unified Communications Manager Interoperability Site Model Components Cisco Unified IP Phone Cisco Unified IP Phone Cisco Unified IP Phone Cisco Unified SIP Proxy Server (CUSP) Cisco Gateway/Cisco Communications Manager Cisco Express Sites Cisco Access switch WS-C PWR-SMI 1 WS-C PS-S 1 Small Campus Multisite H.323 The Small Campus Multisite H.323 site model consists of one site called Warsaw (WAW). This model includes 13 Cisco Unified Communications Manager Express sites connected to each other and to the rest of the network through H.323 gatekeepers. Each Cisco Unified Communications Manager cluster uses an IP-to-IP gateway and MTP to communicate with the Cisco Unified Communications Manager Express systems in this site. Each Cisco Unified Communications Manager Express system has either Cisco Unity Express installed locally, or accesses Cisco Unity Connection through an MWI relay gateway that is located in the GVA site. The Small Campus Multisite H.323 model has these design characteristics: Inline power to IP phones Quality of service from the desktop Cisco Unity Connection, connected through MWI relay gateway Remote access through H.323 gatekeepers to other Cisco Unified Express clusters and servers Figure 10 shows the topology of the Small Campus Multisite H.323 site model. 29

30 Tested Deployments and Figure 10 Small Campus Multisite H.323 Site Topology Table 10 lists the hardware and software components used in the Small Campus Multisite H.323 model. Table 10 Small Campus Multisite H.323 Model Components Analog gateway ATA Cisco Unified IP Phone Cisco Unified IP Phone 7971G-GE 4 Cisco Unified IP Phone 7970G 4 Cisco Unified IP Phone 6921, 6941, and

31 Tested Deployments and Table 10 Small Campus Multisite H.323 Model Components (continued) Gateway Cisco Cisco Cisco Cisco Cisco Cisco Cisco Cisco Cisco Access switch WS-C PWR-SMI 2 WS-C PS-S 1 WS-C PS-S 1 Mid-Market Multisite Centralized (Unified CMBE) The Mid-Market Multi-Site Centralized cluster consists of one centralized site with five SRST remote sites called Manchester (MAN). This model includes Cisco Unified Communications Manager and Cisco Unity Connection running on co-resident deployment on a single Cisco MCS 7828 Unified Communications Manager Appliance server. A separate Windows 2008 server acts as the DNS server for both central and remote sites. DHCP is provided by the remote and central Cisco ISRs. In this model, a Cisco Unified Communications Manager cluster serves 500 phone users in local and remote locations, with the Cisco Unity Connection in the central site providing the voice mail services. Operator console (Cisco Unified Business Attendant Console) is provided separately on a local server in the central site. The Central site is connected to the remote SRST sites through MPLS WAN networks. All calls within central site or within remote sites are G.711 and calls between remote sites and central site are G.729a with 30 ms packetisation period. If the Unified Communications Manager in central site goes down, all central site phones will re-register to a SRST router in central site and all remote site phones will register to the corresponding remote site SRST routers. Access to the PSTN for normal off-net calls is provided by E1 ETSI PRI/BRI links to the PSTN. The five remote sites are connected through WAN network and have RSVP setup for Call Admission Control to the central site. PSTN access for these remote sites either have centralized breakout to the PSTN, or local PSTN breakout using E1 PRI, BRI, or FXO connections and are controlled by Cisco Unified Communications Manager using either H.323 or SIP. Central site uses MGCP PRI for Central PSTN. The Mid-Market-Multi-Site Centralized site model has these design characteristics: Cisco Unified Communications Manager Business Edition Inline power to IP Phones Cisco Unified Contact Center Express (UCCX) Cisco Unified Presence Server

32 Tested Deployments and Cisco Unified Personal Communicator 7.0 and 8.0 versions SIP endpoints and Video endpoints Microsoft OCS 2007 R2 server Cisco Unified Business Attendant Console Windows 2008 Server on MCS 7825 Unified Communications Manager Figure 11 shows the topology of the Mid-Market-Multi-Site Centralized site model. Figure 11 Mid-Market Multi-Site Centralized Site Topology Table 11 lists the hardware and software components used in the Mid-Market Multi-Site Centralized site model. 32