Table Of Contents
Small and Medium Business Tested Deployments and Site Models
Multisite Distributed Deployment Options
Small Sites Using Unified Communications 500 Series
Small Campus SIP Unified Communications Manager Express Site
Small Campus H.323 Unified Communications Manager Express Site
Europe and Emerging Markets Site Models
Small and Medium Business Tested Deployments and Site Models
Cisco Unified Communications Release 7.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 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
–
Cisco Unified Communications 500 Series
•
Medium Business Sites
–
Small Campus SIP Communications Manager Express Site
–
Small Campus H.323 Communications Manager Express Site
–
Small Campus Multisite H.323
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 for Small and Medium Business: Cisco Unified Communications System, Release 7.0(1). For more information on tested deployments and site models for enterprise and midmarket, see Tested Deployments and Site Models for Enterprise and Midmarket.
This topic includes the following sections:
•
Multisite Distributed Deployment Options
•
Europe and Emerging Markets Site Models
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
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 7.0(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 7.0(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
The site models were created and tested for Cisco Unified Communications Release 7.0(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:
•
Component—Hardware or software component
•
Description—Information such 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 North America Site Models
Site Model and Reference Sites IncludedCovington and Robins
Small Campus SIP Unified Communications Manager Express Site
Atlanta (ATL)
Small Campus H.323 Unified Communications Manager Express Site
Toronto (YYZ)
Small Sites Using Unified Communications 500 Series
The small business sites consist of Covington site and Robins site. Unified Communication 500 Series is installed in Covington site and Integrated Services Router 1861 is installed in Robins site.
Figure 3 Covington and Robins Sites Using Unified Communications 500 Series
Small Campus SIP Unified Communications Manager Express Site
The Small-Campus SIP Site model consists of one site called Atlanta (ATL). This site includes:
•
Four Cisco Unified Communications Manager Express routers
•
Four hundred SIP endpoints
•
On Cisco Unity Express
This site communicates with Cisco Unified Communications Manager clusters in other sites using a SIP trunk through an IP-to-IP gateway.
Figure 4 shows the topology of the Small-Campus SIP Site model.
Figure 4 Small -Campus SIP Site Topology
Table 4 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:
•
Four Cisco Unified Communications Manager Express routers
•
One Cisco Unity Express
•
One H.323 gatekeeper
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 5 shows the topology of the Small-Campus H.323 Unified Communications Manager Express Site model.
Figure 5 Small-Campus H.323 Unified Communications Manager Express Site Topology
Table 5 lists the hardware and software components used in the Small-Campus H.323 Unified Communications Manager Express Site model.
Europe and Emerging Markets Site Models
The site models were created and tested for Cisco Unified Communications Release 7.0(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:
•
Component—Hardware or software component
•
Description—Information such model number, release number, protocol, and hardware platform
•
Qty.—Quantity of the component used in the model
Table 6 lists the site model and references to sections that provide detailed information.
Table 6 EUEM Site Model for Small and Medium Business
Site Model and Reference Sites IncludedWarsaw (WAW)
For an illustration showing how the site model was deployed for testing, see Figure 2.
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:
•
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 Cisco Unified Meeting Place Express servers
Figure 6 shows the topology of the Small Campus Multisite H.323 site model.
Figure 6 Small Campus Multisite H.323 Site Topology
Table 7 lists the hardware and software components used in the Small Campus Multisite H.323 model.





