Table Of Contents
Small and Medium Business Tested Deployments and Site Models
Multisite Distributed Deployment Options
Medium Business with Remote Locations
Small Sites Using Unified Communications 500 Series
Small Campus Unified Communications Manager Site
Small Campus SIP Unified Communications Manager Express Site
Small Campus H.323 Unified Communications Manager Express Site
Cisco Unified Communications Manager Release 5.1(2) Interoperability Site
Cisco Communications Manager Release 4.2(3) Interoperability Site
Europe and Emerging Markets Site Models
Medium Business with Remote Locations
Cisco Unified Communications Manager Interoperability Site (EUEM)
Non-Cisco Unified Communications Manager Interoperability Site (EUEM)
Small and Medium Business Tested Deployments and Site Models
Cisco Unified Communications Release 6.1(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 small and medium business 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.
•
Small Business Sites
–
–
–
•
–
–
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:
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 6.1(1).
This topic includes the following sections:
•
•
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:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Multisite Distributed Deployment Options
The site models within each test group can be implemented in various combinations to create deployment models to meet the needs of a wide range or organizations.
Figure 1 shows the multisite distributed deployment that was tested for Cisco Unified Communications Release 6.1(1) testing for North America IP telephony.
For more detailed information about the sites used in this deployment, see the North America Site Models.
Figure 1 Multisite Distributed Deployment for North America IP Telephony
Figure 2 shows the multisite distributed deployment that was tested for Cisco Unified Communications Release 6.1(1) testing for EUEM IP telephony. For more detailed information about the sites used in this deployment, see the Europe and Emerging Markets Site Models.
Figure 2 Multisite Distributed Deployment for EUEM IP Telephony
North America Site Models
Nine site models were created and tested for Cisco Unified Communications Release 6.1(1) testing for North America 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:
•
•
•
Table 1 lists the site models and references to sections that provide detailed information.
Table 1 North America Site Models
Kalamazoo (AZO)
Roxboro (RXB)
Hiawatha and Marion
Small Campus SIP Unified Communications Manager Express Site
Atlanta (ATL)
Small Campus H.323 Unified Communications Manager Express Site
Toronto (YYZ)
Cisco Unified Communications Manager Release 5.1(2) Interoperability Site
Raleigh (RDU)
Cisco Communications Manager Release 4.2(3) Interoperability Site
New York (NYC)
Medium Business with Remote Locations
The Medium Business with Remote Locations site model consists of six sites collectively referred to as Kalamazoo (AZO). This site model includes one main site with a Unified Communications Manager Business Edition (Unified CMBE) and five remote sites that are configured to register with Unified CMBE but fail over to local Unified SRST routers.
The Medium Business with Remote Locations site model supports 500 phones.
Figure 3 shows the topology of the Medium Site model.
Figure 3 Medium Business with Remote Locations Site Topology
Table 2 lists the hardware and software components used in the Medium Business with Remote Locations site model.
Small Sites Using Unified Communications 500 Series
The small business sites consist of Hiawatha site integrated to Covington site and Marion site integrated to Robins site. Unified Communication 500 Series is installed in Hiawatha site and Integrated Services Router 1861 is installed in Marion site.
Figure 4 Hiawatha and Marion Sites Using Unified Communications 500 Series
Small Campus Unified Communications Manager Site
The Small Site model for North America consists of one site called Roxboro (RXB). This site includes a Cisco Unified Communications Manager cluster that includes the following:
RXB represents a small RoHS compliant CCM 5.1 site in the IPT model. The site will contain 500 IP phones; H.323, MGCP and SIP GWs; MeetingPlace Express; Unity Connection; Berbee; Cisco Emergency Response; Cisco Mobility Manager; IPCC Express.
WAN connectivity is provided by a Cisco 2691 router and two SIP gateways provide connectivity to PSTN network. This site has 10,000 SIP endpoints.
The Small Site model supports 500 phones.
Figure 5 shows the topology of the Small Site model.
Figure 5 Small Site Topology
Table 5 lists the hardware and software components used in the Small Site model.
Small Campus SIP Unified Communications Manager Express Site
The Small-Campus SIP Site model consists of one site called Atlanta (ATL). This site includes:
•
•
•
This site communicates with Cisco Unified Communications Manager clusters in other sites using a SIP trunk through an IP-to-IP gateway.
Figure 6 shows the topology of the Small-Campus SIP Site model.
Figure 6 Small -Campus SIP Site Topology
Table 6 lists the hardware and software components used in the Small-Campus SIP Site model.
Small Campus H.323 Unified Communications Manager Express Site
The Small-Campus H.323 Unified Communications Manager Express Site model consists of one site called Toronto (YYZ). This site includes:
•
•
•
The Unified Communications Manager Express routers connect to a Unified MeetingPlace server via the H.323 gatekeeper.
This site has four hundred SCCP endpoints. An IP-to-IP gateway between YYZ and ATL provides connectivity between Unified Communications Manager Express routers and Unified Communications Manager clusters. The H.323 gatekeeper in YYZ provides connectivity between Unified Communications Manager Express routers and Unified Communications Manager clusters.
Figure 7 shows the topology of the Small-Campus H.323 Unified Communications Manager Express Site model.
Figure 7 Small-Campus H.323 Unified Communications Manager Express Site Topology
Table 7 lists the hardware and software components used in the Small-Campus H.323 Unified Communications Manager Express Site model.
Cisco Unified Communications Manager Release 5.1(2) Interoperability Site
The Medium Site model for North America consist of one site called Raleigh (RDU). This site was designed to test interoperability between Cisco Unified Communications Manager 5.1(2) and Cisco Unified Communications Manager 6.1(1a). This site includes a Cisco Unified Communications Manager cluster that includes the following:
•
•
The Medium Site model supports 1,000 phones. Figure 8 shows the topology of the Medium Site model.
Figure 8 Medium Site Topology
Table 8 lists the hardware and software components used in the Medium Site model.
Cisco Communications Manager Release 4.2(3) Interoperability Site
The Cisco Unified Communications Manager Interoperability Site model for North America consists of one site called New York (NYC). This site was designed to test interoperability between Cisco Unified Communications Manager 4.2(3) and Cisco Unified Communications Manager 6.1(1a).
This site includes a Cisco Unified Communications Manager cluster that includes the following:
•
•
This site also has one Cisco Emergency Responder server, one VG224 with 24 analog phones, sic SCCP phones, and 600 simulated SCCP phones.
Figure 9 shows the topology of the Cisco Unified Communications Manager Release 4.2(3) Interoperability Site model.
Figure 9 Cisco Unified Communications Manager Release 4.2(3) Interoperability Site Topology
Table 9 lists the hardware and software components used in the Cisco Unified Communications Manager Release 4.2(3) Interoperability Site.
Europe and Emerging Markets Site Models
Six site models were created and tested for Cisco Unified Communications Release 6.1(1) testing for Europe and Emerging Markets (EUEM) IP telephony. Each site model tested specific hardware and software components, features, functions, protocols, and related items.
A site model includes a site with a three-letter name (for example, CDG, GVA, and MAD). 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:
•
•
•
Table 10 lists the site models and references to sections that provide detailed information.
Table 10 EUEM Site Models
Manchester (MAN)
Geneva (GVA)
Madrid (MAD)
Cisco Unified Communications Manager Interoperability Site (EUEM)
London (LGW)
Non-Cisco Unified Communications Manager Interoperability Site (EUEM)
Reykjavik (RKV)
Warsaw (WAW)
For an illustration showing how these site models were deployed for testing, see Figure 2.
Medium Business with Remote Locations
The Medium Business with Remote Locations site model consists of six sites collectively referred to as Manchester (MAN). This site model includes one main site with a Unified Communications Manager Business Edition (Unified CMBE) and five remote sites that are configured to register with Cisco Unified Communications Manager, Business Edition but fail over to local Unified SRST routers. This model supports up to 500 users across 5 locations.
Figure 10 Medium Business Site with Remote Locations
Table 11 lists the hardware and software components used in the Medium Business with Remote Locations site model.
Medium Site (EUEM)
The Medium Site model consists of one site 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 legacy ATM / Frame Relay and 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 CSPS. 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:
•
•
•
•
•
•
•
•
Figure 11 shows the topology of the EUEM Medium Site model.
Figure 11 EUEM Medium Site Topology
Table 12 lists the hardware and software components used in the Medium Site model.
Small Site (EUEM)
The Small Site model for Europe and Emerging Markets consists of one site called Madrid (MAD). In this model, a Cisco Unified Communications Manager cluster serves 750 phones in a single campus. A PBX that supports the ISO QSIG variant connects to this cluster through direct QSIG links.
Cisco Unity Connection connects to the cluster through the QSIG-enabled intercloster trunk via the LGW site and provide voice messaging functions to PBX users and to Cisco Unified Communications Manager users. PBX users have access to Cisco Unified Communications Manager through a QSIG trunk.
The Cluster connects to the rest of the network through legacy ATM/frame relay and MPLS WAN networks. Calls between this site and other sites in the network are made through the WAN with two Annex M1 intercluster trunks to the CDG and LGW sites.
Access to the PSTN as a backup route to other sites and for normal off-net calls is provided by two E1 ETSI PRI links to the PSTN. Access to services such as Cisco Unified MeetingPlace Express, and operator consoles also is provided through the Annex M1 intercluster trunk to the Large Multisite Centralized with Unified SRST site.
The Small Site model has these design characteristics:
•
•
•
•
•
•
•
•
•
Figure 12 shows the topology of the EUEM Small Site model.
Figure 12 EUEM Small Site Topology
Table 13 lists the hardware and software components used in the EUEM Small Site model.
Cisco Unified Communications Manager Interoperability Site (EUEM)
The Cisco Unified Communications Manager Interoperability Site model for EUEM consists of one site called London (LGW). In this model, a Cisco Unified Communications Manager cluster serves 2,000 phones in a single campus. A PBX that supports the ISO QSIG variant connects to this cluster through direct QSIG links.
The Cluster connects to the rest of the network through legacy ATM/frame relay and MPLS WAN networks. Calls between this site and other sites in the network are made through the WAN with two Annex M1 intercluster trunks to the CDG and MAD sites.
Some PBX and Cisco Unified Communications Manager users have voice messaging services provided by Cisco Unity Connection, which is connected to the cluster through an SCCP link. The PBX user access voice messages through QSIG trunks to Cisco Unified Communications Manager.
Other PBX and CCM users have access to Unified messaging with Unity and Domino located in the CDG Site via the Annex M1 Inter Cluster Trunk. MWI events and message store and retrieval for both the connected PBX and the CCM users is all passed Annex M1 between the sites.
Access to the PSTN as a backup route to other sites and for normal off-net calls is provided by 5 E1 ETSI PRI links to the PSTN. Access to Cisco Unified MeetingPlace Express, the Cisco Unified Communications Manager network, and any non-directly connected clusters is provide through remotely located H.323 gatekeepers. Access to the SIP network is provided through a SIP trunk to a remotely located CSPS. Operator console services are provided in the CDG site through the Annex M1 intercluster trunk.
The Cisco Unified Communications Manager Interoperability Site model has these design characteristics:
•
•
•
•
•
•
•
•
•
•
Figure 13 shows the topology of the EUEM Cisco Unified Communications Manager Interoperability site model.
Figure 13 EUEM Cisco Unified Communications Manager Interoperability Site Topology
Table 14 lists the hardware and software components used in the EUEM Cisco Unified Communications Manager Interoperability Site model.
Non-Cisco Unified Communications Manager Interoperability Site (EUEM)
The Non-Cisco Unified Communications Manager Interoperability Site model for EUEM consists of one site called Reykjavik (RKV). This site model is designed to test interoperability of all components in the other models with CSPS controlled endpoints.
The Non-Cisco Unified Communications Manager Interoperability Site model includes a Cisco SIP Proxy Server (CSPS), and SIP phones and PSTN gateways connected to the CSPS. Each Cisco Unified Communications Manager cluster also has connectivity to the CSPS for interoperability.
Figure 14 shows the topology of the Non-Cisco Unified Communications Manager Interoperability Site model.
Figure 14 Non-Cisco Unified Communications Manager Interoperability Site Topology
Table 15 lists the hardware and software components used in the Non-Cisco Unified Communications Manager Interoperability Site model.
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, and with the Cisco Unified MeetingPlace Express system located in the CDG site.
Each Cisco Unified Communications Manager Express system has either Cisco Unity Express installed locally installed, or will access 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:
•
•
•
•
Figure 15 shows the topology of the Small Campus Multisite H.323 site model.
Figure 15 Small Campus Multisite H.323 Site Topology
Table 16 lists the hardware and software components used in the Small Campus Multisite H.323 model.
