Cisco Preferred Architecture for Midmarket Collaboration. Design Overview

Transcription

1 Cisco Preferred Architecture for Midmarket Collaboration Design Overview PA March 2014

2 Table of Contents Preface...1 Getting Started with Cisco Preferred Architectures... 1 About This Guide... 1 Introduction...2 Technology Use Cases... 2 Architectural Overview... 2 Cisco Business Edition Core Applications... 4 High Availability... 5 Cisco Integrated Services Router... 6 Endpoints...7 Recommended Deployment... 7 Cisco Unified IP Phones... 8 Cisco TelePresence and Video Endpoints... 8 Cisco Jabber... 8 Call Control...9 Recommended Deployment Benefits Deployment Best Practices Cisco Unified Communications Manager and IM and Presence Service Publisher-Subscriber Deployment Model...10 SIP Trunking Recommendations Cisco Unified Survivable Remote Site Telephony...11 Dial Plan...12 Endpoint Addressing...13 Call Routing...13 Class of Service...15 Conferencing...16 Recommended Deployment...17 Audio Conferencing...17 Video Conferencing...17 Benefits...17 Deployment Best Practices...17 Table of Contents

3 Audio Conferencing...17 Sizing Considerations...18 Architecture...18 Video Conferencing...19 Sizing Considerations...19 Video Quality...20 Architecture...20 Video Conferencing Redundancy Licensing Collaboration Edge...23 Recommended Deployment Headquarters Remote Sites Teleworker Sites Benefits Deployment Best Practices PSTN Gateway Virtual Private Network Cisco Expressway Cisco Expressway Core...26 Cisco Expressway Edge...27 Licensing Applications...28 Cisco Unity Connection Recommended Deployment Benefits Deployment Best Practices Cisco Unified Contact Center Express Recommended Deployment Benefits Deployment Best Practices Cisco Prime Collaboration Provisioning Standard Recommended Deployment Table of Contents

4 Benefits Appendix...33 Product List Licensing Options Sample Order Sample Bill of Materials Table of Contents

5 Preface Cisco Preferred Architectures provide recommended deployment models for specific market segments based on common organizational use cases. They incorporate a subset of products from the total Cisco Collaboration portfolio that is best suited for the targeted market segment and defined use cases. These deployment models are prescriptive, out-of-the-box, and built to scale with an organization as its business needs change. This prescriptive approach simplifies the integration of multiple system-level components and enables an organization to select the deployment model that addresses its business needs. Preface Getting Started with Cisco Preferred Architectures 1. Cisco Preferred Architecture (CPA) design overview guides help customers and sales teams select the appropriate architecture based on an organization s business requirements; understand the products that are used within the architecture; and obtain general design best practices. These guides support sales processes. 2. Cisco Validated Design (CVD) guides provide detailed steps for deploying components within the Cisco Preferred Architectures. These guides support planning, deployment, and implementation (PDI). 3. The Cisco Collaboration Solution Reference Network Design (SRND) guide provides detailed design options for Cisco Collaboration. This guide should be referenced when design requirements are outside the scope of Cisco Preferred Architectures. About This Guide The Cisco Preferred Architecture for Midmarket Collaboration Design Overview (CPA for Midmarket Collaboration) is for: Sales teams that sell and design collaboration environments Customers and sales teams who want to understand the overall collaboration architecture, its components, and general design best practices Readers of this guide should have a general knowledge of Cisco Voice, Video, and Collaboration products and a basic understanding of how to deploy these products. This guide simplifies the design and sales process by: Recommending products in the Cisco Collaboration portfolio that are built for the midmarket and that provide appropriate feature sets for this market Detailing a midmarket collaboration architecture and identifying general best practices for deploying in midmarket organizations Including a sample Bill of Materials (BoM) with products that target the midmarket price point For detailed information about planning, deploying, or implementing this architecture, see the following CVDs: Unified Communications Using Cisco BE 6000 Technology Design Guide Video Conferencing Using Cisco BE 6000 Technology Design Guide Help Desk Using Cisco UCCX Technology Design Guide Collaboration Edge Using Cisco BE 6000 Technology Design Guide page 1

6 Introduction In just a few short years, many new collaborative tools have been introduced to the market, enabling businesses to extend communications outside the walls of their businesses. Providing access to collaborative tools without being physically in the office is no longer a nice to have, it s mandatory for businesses to stay relevant in today s market. Today s users expect immediate access to these tools from a wide variety of portable and mobile devices. Many of these same tools can be extended to customers and partners, helping strengthen these relationships. Introduction Not long ago, organizations realized the added value that collaboration applications brought to their business through increased employee productivity and enhanced customer relationships. However, interoperability among collaboration applications was sparse, and applications were difficult to deploy and use. Since then, significant advances have been made in the collaboration space, simplifying deployment, improving interoperability and enhancing the overall user experience. Additionally, a wave of smart phones, social media, and personal collaboration applications have been developed and widely adopted by individuals in their personal lives. Organizations can now feel comfortable providing collaboration applications that employees will quickly adopt and that provide maximum value. These new collaboration tools will enhance an organization s overall business process, make its employees more productive, and open the door to new and innovative ways for communicating with business partners and customers. Technology Use Cases Organizations are looking to streamline their business processes, optimize employee productivity, and enhance relationships with partners and customers. The CPA for Midmarket Collaboration delivers capabilities that enable organizations to immediately realize gains in productivity and enhanced relationships. Additionally, the following technology use cases offer organizations opportunities to develop new, advanced business processes that deliver even more value in these areas. Incorporate Video into Meetings Improve communications, relationships, and productivity by making it easier to meet face-to-face over distance. Extend Telephony with Video Facilitate face-to-face video communications directly from your phone or softphone application. Support Teleworkers and Branch Offices Let employees work from multiple locations, whether satellite offices, home offices, or when traveling. Collaborate with External Organizations Easily share information, interact in real time, and communicate across channels beyond and telephone. Information about Cisco Collaboration Technologies and use cases is available on Cisco.com. Architectural Overview The CPA for Midmarket Collaboration provides an end-to-end collaboration deployment for up to 1000 users. This architecture ensures high availability for critical applications and uses products developed and priced for the midmarket. The consistent user experience provided by the overall architecture ensures quick user adoption, enabling an organization to immediately recognize value for its investment. Additionally, the architecture supports an advanced set of collaboration services that extend to mobile workers, partners, and page 2

7 customers through the following key services: Voice communications Instant messaging and presence High definition video and content sharing Rich media conferencing Enablement of mobile and remote workers Business-to-business voice and video communications Unified voice messaging Customer care Introduction Because of the adaptable nature of Cisco endpoints and their support for IP networks, this architecture enables an organization to use its current data network to support both voice and video calls. In general, it is a best practice to ensure a collaboration solution is deployed with proper Quality of Service (QoS) configured throughout the network. Voice and video IP traffic should be classified and prioritized to preserve the user experience and avoid negative effects, such as delay, loss and jitter. For more information about LAN and WAN QoS, see Cisco Collaboration SRND. The CPA for Midmarket Collaboration, shown in Figure 1, provides highly available and secure centralized services. These services extend easily to remote offices and mobile workers, ensuring availability of critical services even if communication to headquarters is lost. Centralizing services also simplifies management and administration of an organization s collaboration deployment. Figure 1 - Cisco Preferred Architecture for Midmarket Collaboration page 3

8 Table 1 lists the products in this architecture. For simplicity, products are broken into modules to help categorize and define their roles. The content in this guide is organized in the same modules. Table 1 - Components for the Cisco Preferred Architecture for Midmarket Collaboration Module Component Description Call Control Endpoints Cisco Unified Communications Manager (Cisco Unified CM) Cisco Unified Communications Manager IM & Presence Service (IM and Presence Service) Cisco Integrated Services Router (Cisco ISR) Cisco Unified IP Phones, Cisco TelePresence video endpoints, and Cisco Jabber Provides endpoint registration, call processing, and media resource management Provides instant messaging and presence services Provides Survivable Remote Site Telephony (SRST) functionality Enables users for real-time voice, video, and instant messaging communications Conferencing Cisco TelePresence Conductor Manages video conferencing resources Cisco TelePresence Server Cisco ISR Provides video conferencing resources Provides audio conferencing resources Collaboration Edge Cisco Expressway Core Enables interoperability with third-party systems and firewall traversal Cisco Expressway Edge Cisco ISR Supports remote endpoint registration to Cisco Unified CM and enables business-to-business communications Provides either public switched telephone network (PSTN) or Cisco Unified Border Element (CUBE) connectivity Applications Cisco Unity Connection (Unity Connection) Provides unified messaging and voic services Cisco Unified Contact Center Express (Unified CCX) Cisco Prime Collaboration Provisioning Standard Provides customer interaction management services Provisions Cisco Unified Communications applications Introduction Cisco Business Edition 6000 The Cisco BE 6000 is a purpose built package designed specifically for midmarket organizations with up to 1000 employees, and it is the foundation for this architecture. The Cisco BE 6000 is built on a virtualized Cisco Unified Computing System (Cisco UCS) that is prepared and ready-for-use with a preinstalled virtualization hypervisor and application installation files. The Cisco BE 6000 solution offers premium voice, video, messaging, instant messaging and presence, and contact center features on a single, integrated platform. For more information about the Cisco BE 6000, see the data sheet. Core Applications The CPA for Midmarket Collaboration is built on two Cisco BE 6000 high-density servers, ensuring high availability for applications within the architecture. Virtualizing multiple applications on a single server lowers cost, minimizes rack space, lowers power requirements, and simplifies deployment and management. Virtualization also accommodates redeploying hardware and scaling software applications as organizational needs change. page 4

9 Figure 2 - Cisco BE 6000 Applications Introduction In this architecture, the following seven applications and Cisco Prime Collaboration Provisioning Standard are deployed on one Cisco BE 6000 server while a second instance of each of the seven applications is deployed on a second Cisco BE 6000 server, providing hardware and software redundancy: Cisco Unified Communications Manager Cisco Unified Communications Manager IM and Presence Service Cisco Unity Connection Cisco TelePresence Conductor Cisco Expressway, comprised of Expressway Core and Expressway Edge Cisco Unified Contact Center Express Cisco recommends always deploying redundant configurations to provide the highest availability for critical business applications; however, a non-redundant, Cisco BE 6000 server configuration may be deployed for organizations that do not require full redundancy. Note Space is available on the Cisco BE 6000 for two additional Cisco UC applications, such as Cisco Emergency responder or Singlewire InformaCast. High Availability The CPA for Midmarket Collaboration design includes high availability for all deployed applications. These services will be preserved if a component fails on the primary Cisco BE 6000 server. High availability is accomplished with the underlying clustering mechanism that is present in all deployed Cisco Unified Communications applications. Clustering allows the administration and configuration of deployed applications to be replicated to backup instances of those applications. If either instance of an application fails, Cisco Unified Communications services such as endpoint registration, call processing, messaging, business-to-business communication, and many others will continue to operate on the remaining instance of the application. This process is transparent to an organization s users. In addition to clustering, the CPA for Midmarket Collaboration design ensures high availability through the use of redundant power supplies, network connectivity, and disk arrays. page 5

10 Cisco Integrated Services Router The Cisco Integrated Services Router (Cisco ISR) provides Wide Area Network (WAN) and Cisco Unified Communications services in a single platform. For this architecture, the Cisco ISR can provide the following functions (Figure 3): Audio conference bridge for Cisco Unified CM External connectivity to Internet IP routing and network services, such as DHCP, DNS, NTP and others Cisco Unified Survivable Remote Site Telephony (SRST) to provide calls during WAN failures Voice gateway to the Public Switched Telephone Network (PSTN) or Cisco Unified Border Element (CUBE) for Session Initiation Protocol (SIP) trunks Integrated data and voice connectivity to service providers Multiprotocol Label Switching (MPLS) WAN connectivity for an organization s network Virtual Private Network (VPN) client to establish secure tunnels to VPN concentrator Introduction Figure 3 - Cisco ISR Functions Cisco ISR routers have additional slots that support add-on modules, such as wireless controllers and VMware ESXi servers. Various Cisco ISR router models can be used to support different features, to scale, and to accommodate additional services. This modular design enables the Cisco ISR to be deployed at headquarters, remote locations, or branch locations. For more information about Cisco ISR, see the data sheet. page 6

11 Endpoints Cisco provides endpoints with a wide range of features, functionality, and user experiences. Because endpoints range from low-cost, single-line phones and softclients to three-screen Cisco TelePresence endpoints, an organization can deploy the right variety of endpoints to meet users needs (Figure 4). Additionally, these devices enable users to access multiple communication services, such as: Voice calls Video calls Conferencing Voic Presence Instant messages (Cisco Jabber) Desktop sharing Endpoints Figure 4 - Architecture for Endpoints Recommended Deployment Because Cisco Unified CM is the call control server for this deployment, SIP should be used to register Cisco IP phones and TelePresence video endpoints directly to the Cisco Unified CM. The Cisco Unified CM cluster s failover mechanism provides endpoint registration redundancy. If a WAN failure occurs and endpoints at remote locations cannot register to Cisco Unified CM, they will use SRST functionality for local and PSTN calls, though some services, such as voic and presence, might not be available. The following endpoints are recommended because they provide the optimal features for this design at page 7

12 a mid-market price point. Cisco has a range of endpoints with various features and functionality that an organization can also use to address its business needs. Cisco Unified IP Phones Product Cisco Unified IP Phone Cisco Unified IP Phone 7800 Series 1 Cisco Unified IP Phone 8900 or 9900 Series 1 Cisco Unified IP Phone Description Public space, single line phone General office use, multiple-line phone General office use, video phone IP conference phone Endpoints 1. Does not support Cisco Expressway mobile and remote access capabilities. For more information about Cisco Expressway, see Collaboration Edge on page 23. Cisco TelePresence and Video Endpoints Product Cisco DX Cisco EX Series 2 Cisco MX Series 2 Cisco SX Series 2 Description Smart-desk video endpoint Personal TelePresence endpoint for the desktop TelePresence multipurpose room endpoint Integrator series TelePresence endpoint 1. Does not support Cisco Expressway mobile and remote access capabilities. For more information about Cisco Expressway, see Collaboration Edge on page Requires TC 7 or later to support features in this deployment. SRST is not available for Cisco EX, MX, or SX Series endpoints. Cisco Jabber Product 1 Mobile Jabber for Android Jabber for iphone and ipad Desktop Jabber for Mac Jabber for Windows Description Soft client with integrated voice, video, voic , and instant messaging and presence functionality for mobile devices and personal computers 1. The following minimum versions of Cisco Jabber are required to support Cisco Expressway mobile and remote access capabilities: Jabber Windows 9.7, Jabber Mac 9.6, Jabber ios 9.6.1, and Jabber Android 9.6. page 8

13 Call Control Call control is the core element for any communication deployment. Call control is comprised of endpoint registration, call processing, organizational dial plan, address scheme normalization, and call admission control. Cisco Unified CM provides a common call control for all Cisco communication deployments (Figure 5). Having a highly available and common call control component for a communications infrastructure is crucial to provide consistent services for all devices and communication types and to preserve a uniform dial plan and features among different devices. Call Control Adding the IM and Presence Service to a Cisco Unified CM deployment provides instant messaging, network-based presence, and federation for third-party chat servers and enables the use of Cisco Jabber for instant messaging, presence, and audio and video communications. Figure 5 - Architecture for Call Control Table 2 lists the roles of the components in this architecture and the services that they provide. Table 2 - Components for Call Control Module Component Description Call Control Cisco Unified CM Provides call routing and services, dial plan, bandwidth management, device-based presence and enables Cisco Jabber desk phone control IM and Presence Service Cisco ISR Provides Cisco Jabber support for instant messaging and presence and third-party federation Provides Survivable Remote Site Telephony (SRST) to support call control functions during a WAN outage page 9

14 Recommended Deployment Deploy two Cisco Unified CM servers in a cluster configuration that includes a Publisher node and a Subscriber node for redundancy Deploy two IM and Presence Service servers in a cluster configuration that includes a Publisher node and a Subscriber node for redundancy Enable Cisco SRST on the Cisco ISR as a backup service at remote sites to ensure high availability Note If full redundancy is not required, a single server may be deployed without loss of functionality. Call Control Benefits This deployment provides the following benefits: There is centralized call control at a single location that serves multiple locations. Management is centralized. Common telephony features are available across voice and video endpoints and Cisco Jabber clients. Single call control and a unified dialing plan exist for voice and video endpoints and Cisco Jabber clients. Critical business applications are highly available and redundant. Deployment Best Practices Cisco Unified Communications Manager and IM and Presence Service Publisher-Subscriber Deployment Model A Cisco Unified CM or an IM and Presence Service cluster is comprised of one Publisher node and one Subscriber node. The Publisher node is the server that is installed first. This server contains the cluster s configuration database. Cluster-wide configuration is written to the Publisher s database and replicated on the Subscriber. The Subscriber node is the server that is installed second. It contains a replica of the Publisher s database. The Subscriber is updated automatically when the Publisher s configuration changes. Clustering provides an automatic redundancy mechanism for endpoints and for Cisco Unified CM services, such as the ability to receive and process incoming calls (Figure 6). It is recommended that the Cisco Unified CM cluster be configured with the Subscriber node as the primary call-processing server and the Publisher node as the backup call-processing server. This configuration applies to the IM and Presence Service cluster, too. If the IM and Presence Service Subscriber node goes down, then IM and presence capabilities will still be available for Cisco Jabber clients. page 10

15 Figure 6 - Cisco Unified CM Cluster Call Control SIP Trunking Recommendations A trunk is a collection of communication channels between two different call-processing servers or gateways that is used for server-side communication. Cisco Unified CM uses SIP trunks to communicate with external entities. For deployment consistency, use SIP trunks from Cisco Unified CM to communicate with all the components in this architecture. Using SIP trunks offers the following benefits: SIP trunks are enhanced with presence information. SIP trunks are recommended for video communications. For the Cisco Unified CM cluster, configure a SIP trunk from the Cisco Unified CM cluster to external components in the deployment, such as TelePresence Conductor and IM and Presence Service. Ensure that each server for that external component is specified as a destination in the SIP trunk configuration. This configuration ensures that no service disruption occurs if a node goes down. Cisco Unified Survivable Remote Site Telephony The Cisco SRST feature ensures business continuity and is critical for branch sites that require uninterrupted voice services during WAN outages. SRST runs on the same Cisco ISR that provides WAN and PSTN connectivity for a remote site (Figure 7). page 11

16 Figure 7 - Cisco SRST Call Control Deploying SRST on the Cisco ISR is recommended in the following cases: The site has local PSTN connectivity. The site does not have local PSTN connectivity but has more than 25 users. Local PSTN connectivity should be available to ensure there is no interruption to external voice services if a WAN outage occurs. If a WAN failure occurs at a site with SRST and local PSTN access, the following services will be available: Internal point-to-point voice and video calls External voice calls via PSTN Call hold, transfer, and conference Music on hold Note SRST is not available for Cisco EX, MX, or SX Series endpoints. See the data sheet for information about endpoints that support SRST. Dial Plan A structured, well-designed dial plan is the key to successfully deploying any call control system. Cisco Unified CM uses the dial plan to process calls from all endpoints and gateways. Two main components of the dial plan are: Endpoint addressing Call routing page 12

17 Endpoint Addressing In traditional PBX voice only deployments, all endpoints are addressed with a numeric ID, known as a telephone internal number. However, as new endpoint types and connectivity options have emerged, so did additional addressing schemes. Common addressing schemes are: +E.164 A numeric public telecommunications infrastructure-numbering plan used by telecommunications carriers worldwide in PSTN, such as Call Control URI An address similar to an address, such as usera@company.com, that contains the host portion of either the domain or the call agent s host address. The user portion (user A) identifies the device within the domain (company.com). URIs are alphanumeric and can use numbers instead of names, such as @company.com. Abbreviated dialing An abbreviated dial plan is essentially a subset of the full +E.164 address that simplifies dialing inside an organization. For example, the abbreviated dial string of 1234 can be configured for a device with an +E.164 address of The use of both a numeric and alphanumeric dial plan is recommended, as follows: Use +E.164 numeric addressing for dialing inside the organization. Use both +E.164 and URI for business-to-business communications. Use abbreviated dialing aliases to simplify on-net dialing from internal locations. Using both types of dial plans ensures backward compatibility with endpoints or systems that cannot dial SIP URIs and preserves advantages of SIP URIs. For example, SIP URIs are easy to remember because they usually match a person s name or username followed by the company domain, such as johnsmith@ company1.com. For these reasons, every connected and registered endpoint can be assigned both a numeric address and an alphanumeric alias that the organization s users can reach by dialing either. Call Routing Numeric Call Routing The +E.164 format for numeric addresses is recommended because it: Is globally unique and widely used in voice networks Is widely deployed in corporate Lightweight Directory Access Protocol (LDAP) directories and results in better system integrations Is commonly shared between multiple devices like mobile phones Simplifies the alternate-path routing Cisco Unified CM uses to reach an external device through PSTN or on another network For these reasons, associating endpoints with a globalized +E.164 number ( ) is recommended rather than with a number that is valid only inside the organization (1234). To simplify dialing, use abbreviated dialing with the full +E.164 numbering plan. Doing so enables users to dial either the full +E.164 number from external locations or the abbreviated number from inside the organization. For example, a user can dial from internal or external locations and dial 1212 from an internal location to reach the same person. Figure 8 provides an example for the endpoint addressing recommendations. page 13

18 Figure 8 - Numeric and Alphanumeric Endpoint Addressing Example Call Control Type Number Reachable From... +E.164 address (directory number) Internal locations and external PSTN locations Abbreviated dialing 1234 Internal locations by abbreviated dialing number Alphanumeric SIP URI alice@domain.com Internal locations and external locations over the Internet Numeric SIP URI @domain.com Internal locations and external locations over the Internet Alphanumeric Call Routing and Aliases When an endpoint is enabled for business-to-business calls over the Internet, it is recommended that a SIP URI be associated to the device because Internet communications require a SIP domain for the call to reach its destination, such as room1@domain.com. Voice and video services are not affected when multiple addresses are used. As with numeric routing, if an alias or SIP URI is recognized as an internal destination and associated with a specific device, Cisco Unified CM sends the call to that device. However, if the alias does not match any registered endpoint aliases, Cisco Unified CM uses the SIP route pattern to send the call to its destination. For example, if the dialed alias room1@externaldomain.com is not configured, Cisco Unified CM uses the SIP route pattern to send the call as a business-to-business call to the Expressway Core. If the dialed alias meet.user1@internaldomain.com is the one used for a TelePresence Conductor SIP URI, Cisco Unified CM uses the SIP route pattern internaldomain.com to send the call to the TelePresence Conductor trunk. Directory Integration To enable users to search contacts and dial from the directory, integrate Cisco Unified CM with the organization s LDAP directory. Though Cisco Unified CM allows the creation of local user contacts, LDAP directory integration is required when using Cisco Jabber because it allows a single location for directory management. Additionally, LDAP directory integration enables users to authenticate to Cisco Unified CM and Cisco Jabber by using their LDAP directory credentials. Cisco Unified CM pulls user and contact information from LDAP directories and synchronizes user parameters name, surname, username, telephone number and SIP URI when changes occur. Use the telephonenumber and mail attributes to populate the Cisco Unified CM directory. The IM and Presence Service pulls user and contact information from Cisco Unified CM. page 14

19 Class of Service Class of service is used to differentiate access services for an organization s users, such as to allow only emergency and local calling from lobby phones while allowing unrestricted calls from executive phones. Partitions and calling search spaces can be configured in Cisco Unified CM to provide class of service, and the class of service categories in Table 3 are recommended to provide PSTN access for emergency, local, national, and international dialing. For more information about class of service, see the Cisco Collaboration SRND. Call Control Table 3 - Class of Service by Call Type Call Type Class of Services Includes Lobby Phones Base Emergency Employee Standard Silver Local and Emergency Sales Gold National, Local, and Emergency Executives Platinum International, National, Local, and Emergency page 15

20 Conferencing The ability for three or more people to communicate in real time by using voice and video technologies is a core component of collaboration. Conferencing builds upon existing infrastructure in place for point-to-point calls, offering an organization s users a consistent voice and video experience regardless of how many participants are involved (Figure 9). Conferencing Figure 9 - Architecture for Conferencing Table 4 lists the roles of the components in this architecture and the services that they provide. Table 4 - Components for Conferencing Module Component Description Call Control Cisco Unified CM Manages and allocates audio conferencing resources from Cisco ISR packet voice/data modules (PVDMs) and communicates with TelePresence Conductor for allocation of video conferencing resources Conferencing Cisco TelePresence Conductor Manages video conferencing resources Cisco TelePresence Server Cisco ISR Provides video conferencing resources Provides voice conferencing resources There are three types of conferences: Ad-hoc/Instant: A conference that is not scheduled or organized in advance. For example, a call between two parties who add additional parties to the call is an ad-hoc conference. Rendezvous: A conference that requires callers to dial a predetermined number or URI to reach a shared conferencing resource. Meet-me, static, or permanent are other names for this type of conference. page 16

21 Scheduled: A conference that guarantees conferencing resources will be available for callers at a predetermined start time. Note The components required for scheduled conferences are not part of this architecture. However, Cisco WebEx Cloud s hosted services can be used for scheduled audio conferencing and Cisco TelePresence Management Suite (TMS) can be used for scheduled video conferences. See the data sheets for more information. Conferencing Recommended Deployment Audio Conferencing Deploy packet voice digital signal processor module (PVDM) resources on Cisco ISR routers for ad-hoc conferences and for rendezvous conferences. Video Conferencing Deploy Cisco TelePresence Conductor on the primary Cisco BE 6000 server and integrate with Unified CM. Deploy a redundant Cisco TelePresence Conductor on the backup Cisco BE 6000 server and integrate with Cisco Unified CM. Deploy Cisco TelePresence Server on a dedicated Cisco UCS C240 M3 server for personal multiparty, ad-hoc, and rendezvous conferences. Note If full redundancy is not required, a single server may be deployed without loss of functionality. Benefits This deployment provides the following benefits: There is a consistent user experience for launching and joining conferences. Dedicated PVDMs and Cisco TelePresence Server resources enable greater scale and redundancy. Cisco Unified CM s Intelligent Bridge Selection ensures the appropriate audio or video resource is allocated for ad-hoc conferences. Deployment Best Practices Audio Conferencing For ad-hoc and rendezvous audio conferences, use dedicated packet voice digital signal processor module (PVDM) resources as the audio conference bridges. A Cisco ISR with PVDM is recommended. The Cisco ISR requires a PVDM to support audio conferences, voice interfaces (T1, E1, FXO, FXS), and audio transcoding. Using Cisco ISRs for a variety of functions, such as voice gateway, SRST, conferencing, and WAN page 17

22 connectivity, and combining these voice services into a single platform offers a significant cost savings over individual components. For additional deployment flexibility, PVDM modules are available in different densities and support a range of codecs of different complexities. Sizing Considerations The decision to integrate conferencing resources into an existing router depends on the voice capacity and overall performance of that router. A standalone gateway is recommended if an organization s existing router: Consistently runs above 40% CPU A standalone gateway avoids voice traffic processing delays. Has limited slots available for voice interface cards or digital signal processors A standalone gateway ensures that additional capacity is available when needed. Conferencing Table 5 lists the recommended Cisco ISR platforms and number of audio conference ports to support ad-hoc and rendezvous audio conferences. Use this information as the starting point for deployment planning. Table 5 - Audio Conference Port Recommendations Site Size Cisco ISR Audio Conference Ports 50 users Cisco users Cisco users Cisco users Cisco users Cisco Architecture Rendezvous audio conferences rely on Cisco Unified CM s Meet-me feature. This feature requires a set of directory numbers (DNs) to be allocated exclusively for rendezvous audio conferences. Users invoke the feature by pressing the Meet-Me softkey on their audio endpoints and then dialing DNs within the predetermined range. Subsequent attendees dial the predetermined number directly to join the conference. The existing dial plan is used for controlling access to these DNs. Rendezvous audio conferences are hosted on the same Cisco ISR PVDM resources as ad-hoc audio conferences. Ad-hoc audio conference resources register with Cisco Unified CM and are controlled by Media Resource Group Lists (MRGLs) and Media Resource Groups (MRGs). Endpoints will invoke these ad-hoc resources if their assigned device pool has access to the appropriate MRGL. Configuring MRGLs is recommended, so conference resources that are local to the initiating endpoint are preferred over other resources (Figure 10). page 18

23 Figure 10 - MRGL Example Conferencing Video Conferencing For deployments with 1,000 or fewer users and with the Cisco BE6000 used for Cisco Unified Communications applications, deploy Midmarket Virtual TelePresence Conductor with Cisco TelePresence Server on Virtual Machine (vts) for video conferencing. Cisco Multiparty Media 310 and Multiparty Media 320 are also available for deployments up to 1,000 users. All these platforms offer the following flexible licensing and capacity options: All platforms support pay as you grow licensing. Cisco vts has several Open Virtualization Appliance (OVA) options for capacity. The recommended vts is the 8-core/16vCPU OVA. One or more Cisco UCS C240 M3 servers should be deployed according to the vts requirements for CPU, memory, and hard disk resources to host these vts instances. Up to two of these vts OVAs can be deployed per Cisco UCS C240 M3 server. The Sample Bill of Materials on page 35 contains details of a C240 M3 server capable of running the 8-core/16vCPU OVA vts. Sizing Considerations Generally a ratio of 15:1 or 20:1 is used as a starting point to determine the number of video ports needed for a given number of users. While this holds true for large deployments, those under 1000 users require more ports per user to ensure an acceptable minimum number of video conferences can be run concurrently. Table 6 provides guidance for number of required video ports. Table 6 - Video Conference Port Recommendations Number of Users Video Conference Ports 100 users users users users users 72 page 19

24 Next, consider the following factors and adjust the size accordingly: Are the organization s employees comfortable with using video technology? Does the organization host large all hands type meetings with video endpoints? Will the organization s employees heavily use video soft clients, such as Cisco Jabber? If any one of these statements is true, then more video ports might be necessary. Conferencing Video Quality Video resolution determines the quality of users video experience and the number of video connections that a Cisco TelePresence Server can support. For optimal experiences, it is recommended that High Definition (HD) video calls be enabled at 720p resolution with 30 frames per second. Depending on the budget and capability of an organization s endpoints and network, HD video calls might not always be possible. If not, the Table 7 shows the maximum capacity of the vts 8-core/16vCPU at different video resolutions for planning purposes. Table 7 - Recommendations for Optimal Video Quality and Sizing Number of C240 M3 Servers Number of 8-core/16vCPU TelePresence Servers on Virtual Machine Number of 720p Ports Number of 480p Ports Up to 2 instances of the 8-core/16vCPU vts can be deployed on a single Cisco UCS C240 M3 server. These are separate instances of TelePresence Server that are not clustered together. The maximum number of participants in a single conference is the same as a single 8-core/16vCPU vts. Note With Cisco Conductor and TelePresence Server, a single conference resource can host multiple simultaneous conferences with different resolution limits. There is no need to dedicate a Cisco TelePresence Server to a single resolution. Architecture Cisco TelePresence Conductor manages the TelePresence Server resources that are used for ad-hoc and rendezvous conferences. TelePresence Conductor is one of several options for Cisco BE 6000 UC applications that can ship on the Cisco BE Because Cisco vts requires resources beyond the typical Cisco BE 6000 applications, running the vts software on a dedicated Cisco UCS C240 M3 server is required (Figure 11). page 20

25 Figure 11 - Cisco UCS C240 M3 in the Video Conferencing Architecture Conferencing Acting as a conference controller and manager between Cisco Unified CM and the Cisco TelePresence Server, TelePresence Conductor handles conference creation, deletion, and advanced video functionality like Optimized Conferencing and ActiveControl. Ad-hoc conferences are routed to Cisco TelePresence Conductor through Cisco Unified CM Media Resource Group Lists (MRGLs) and Media Resource Groups (MRGs), which are applied to a group of video devices through Cisco Unified CM Device Pools. Cisco Unified CM relies on Intelligent Bridge Selection, to ensure the appropriate resource is allocated depending on the initiating device s capabilities. Figure 12 how MRGLs and MRGs are used to direct an ad-hoc conference request to TelePresence Conductor. Figure 12 - MRGL Ad-hoc Conference Request Rendezvous conferences are directed to Cisco TelePresence Conductor through Cisco Unified CM route patterns and the existing dial plan. Multiple virtual IP addresses are configured on TelePresence Conductor, allowing it to be added as both an ad hoc resource and a rendezvous destination. This requires configuring at least two SIP trunks from Cisco Unified CM to TelePresence Conductor. Cisco TelePresence Conductor handles ad-hoc and rendezvous conferences on a first-come, first-served basis, making them best-effort services. Video Conferencing Multiple virtual IP addresses are configured on Cisco TelePresence Conductor, allowing it to be added as both an ad-hoc conference bridge and as a SIP trunk to Cisco Unified CM. Rendezvous video conferences with TelePresence Conductor rely on the Cisco Unified CMs dial plan to route these calls out the proper page 21

26 SIP trunk to TelePresence Conductor. Ad-hoc video conferences with TelePresence Conductor will use the same Media Resource Group List and Media Resource Group architecture described in Audio Conferencing on page 17. Redundancy Database replication ensures both Cisco TelePresence Conductors share the same configuration and will continue to allow video conference capability in the event of a failure on either Cisco BE 6000 HD server. Conferencing Licensing Users who require video conferencing should be enabled through Cisco Unified Workspace Licensing (Cisco UWL) Professional and the Cisco Personal Multiparty offering. All Cisco UWL Professional users are entitled to personal, named-host conferences with up to four participants. This enables both ad-hoc and rendezvous video conferencing. To take advantage of the Personal Multiparty offering, a minimum of 50 Cisco UWL Professional users must be provisioned. A single Cisco TelePresence Conductor and all TelePresence Server licenses are supplied to enable these users for named-host, four-person conferences. A second Midmarket Virtual TelePresence Conductor is required for redundancy. The only hardware required are the servers hosting the TelePresence Conductors (Cisco BE 6000 HD primary and backup servers) and the TelePresence Server on Virtual Machine (UCS C240 M3). For video conferences of 5 or more participants, individual Cisco TelePresence Server licenses must be purchased. A TelePresence Server can be licensed either via Personal Multiparty or Screen Licenses; use of both licensing methods on the same instance of TelePresence Server is not allowed. It is supported to have a single UCS C240 M3 hosting two separate instances of TelePresence Server on Virtual Machine, one licensed via Personal Multiparty and the other through Screen Licenses. The Cisco TelePresence Conductor supplied with Cisco UWL licensing is intended only for personal, multiparty conferences. Therefore, if Screen Licenses are purchased to enable larger video conferences, TelePresence Conductor must be purchased separately. In this case, two Midmarket Virtual TelePresence Conductors should be purchased and clustered for redundancy. This TelePresence Conductor cluster would serve both personal multiparty and larger video conferences. page 22

27 Collaboration Edge In addition to the public telephone system, business demand for connectivity to other organizations by leveraging the Internet has increased significantly over the past few years, and for many organizations, this connectivity is a fundamental requirement for conducting day-to-day activities. Moreover, securely connecting mobile workers and remote site workers to each other and to headquarters are critical functions that enable organizations to accomplish their business goals. The CPA for Midmarket Collaboration addresses these needs with the Collaboration Edge architecture in Figure 13. Collaboration Edge Figure 13 - Architecture for Collaboration Edge Table 8 lists the roles of the components in this architecture and the services that they provide. Table 8 - Components for Collaboration Edge Module Component Description Collaboration Edge Expressway Edge Allows secure communication including client registration and business-to-business calling through an organization Expressway Core Cisco ISR Establishes a secure connection to the Expressway Edge through the firewall; provides other services, such as H.323-SIP interworking; and enables mobile and remote access with Cisco Unified CM Enables local PSTN connectivity Enables connectivity from an organization s network to the service provider network for SIP trunks via Cisco Unified Border Element (CUBE) page 23

28 Recommended Deployment Headquarters Deploy Cisco ISR as the PSTN gateway. OR Enable CUBE functionality on the Cisco ISR for voice connectivity from the organization s network to the service provider network through a SIP trunk. Deploy two Cisco Expressway Core and Edge servers in a clustered configuration to enable remote Jabber and TelePresence video endpoint registrations, IM and presence, and secure business-tobusiness connectivity through the firewall. Note If full redundancy is not required, a single server may be deployed without loss of functionality. Collaboration Edge Remote Sites Deploy Cisco ISR as the PSTN gateway. Teleworker Sites Benefits Deploy Cisco 8900 and 9900 Series IP Phones with an existing Cisco Adaptive Security Appliance (ASA) or Cisco IOS-based VPN. For video-enabled sites, deploy a Cisco EX Series TelePresence video endpoint. This deployment provides the following benefits: The Cisco ISR supports standards-based interfaces and different PSTN types, so it can be deployed globally. CUBE functionality can be enabled on the Cisco ISR if a SIP trunk is used rather than traditional PSTN interfaces. The Cisco ISR can be used for WAN connectivity. Cisco Expressway provides calling, presence, instant messaging, voic , and corporate directory services for Cisco Jabber and TelePresence video endpoints. Cisco Expressway enables video communications between organizations, partners, and vendors via the Internet. Deployment Best Practices PSTN Gateway Because landlines and mobile phones use the PSTN for local and international calls, external connectivity to the PSTN from an organization s IP telephony network is a requirement (Figure 14). page 24

29 Figure 14 - PSTN Connectivity Collaboration Edge Use Cisco ISR with a time-division multiplex (TDM) module as the PSTN gateway at headquarters. This configuration enables the gateway to resolve incoming and outgoing calls for an organization to and from the PSTN. Use this gateway for number transformation to PSTN requirements. See Call Control on page 9 for dial plan recommendations. At remote sites, deploy a Cisco ISR for local PSTN connectivity using voice modules. Table 9 lists the recommended Cisco ISR series by deployment location. For information about Cisco ISR, see the data sheet. Table 9 - Recommended PSTN Gateways Location Headquarters Remote Sites PSTN Gateway ISR G series ISR G series If SIP trunks are used to connect to a service provider for voice calls, enable CUBE functionality on the Cisco ISR that is deployed at headquarters. When deploying Cisco ISR with CUBE functionality, the following is recommended: Deploy the CUBE in the demilitarized zone (DMZ). Enable the firewall to NAT the external address to the address of the CUBE. Enable the firewall to inspect voice calls. The Cisco Unified CM will route calls through SIP trunks to gateways, CUBE, or Cisco Expressways based on the dial plan. For dial plan recommendations, see Dial Plan on page 12. Virtual Private Network VPN enables an organization s network to be extended to remote and teleworker sites, allowing those sites full access to corporate services. Use the organization s existing VPN to extend collaboration services to teleworkers or use Cisco IP Phones with VPN clients. The Cisco 8900 and the 9900 Series IP Phones have a built-in VPN client that can connect to the Cisco ASA or Cisco ISR over the Internet and establish a secure connection to access the organization s network. No additional device, such as a CVO router, is needed for this connectivity, and these Cisco IP phones are recommended for teleworkers sites. Cisco Expressway Firewalls are deployed to provide network security to separate an organization s network and mask IP addresses from untrusted networks, such as the Internet. Cisco Expressway provides secure firewall and NAT traversal for mobile Cisco Jabber and TelePresence video endpoints (Figure 15) and secure businessto-business communications (Figure 16). Cisco Expressway consists of two servers: Expressway Core and Expressway Edge. Cisco Expressway Core should be deployed inside the network, and Expressway Edge should be deployed page 25

30 in the Demilitarized Zone (DMZ) by connecting separate network ports on the BE6000 server to the organization s network and to the DMZ. For added security, deploy Expressway Edge in the DMZ on a dedicated server. Figure 15 - Traversal for Registrations Through Firewall with Expressway Core and Expressway Edge Collaboration Edge Figure 16 - Traversal for Business-to-Business Calls Through Firewall with Expressway Core and Expressway Edge Cisco Expressway Core Place Expressway Core in the trusted network inside the organization. Expressway Core will: Function as a traversal client and establish a secure connection to Expressway Edge through the firewall Enable calls to endpoints by using a SIP zone to peer with the Cisco Unified CM, which in turn uses a SIP trunk to peer with Expressway Core for business-to-business communication Integrate with an existing internal video network that uses H.323 Enable business-to-business calls to external entities that communicate using SIP or H.323 Provide interworking between H.323 and SIP protocols for H.323 business-to-business communication Enable mobile and remote access capabilities and call signaling for Cisco-supported endpoints, directing them to Cisco Unified CM for SIP registration or the IM and Presence Service See Endpoints on page 7 for more information. page 26

31 Cisco Expressway Edge Place Expressway Edge in a DMZ because it is reachable directly from the untrusted, external network. Note that the organization s firewall policies control the communication to and from this server. Expressway Edge will: Function as a traversal server and allow secure communication from Expressway Core Enable peering, or neighboring, to other organizations using SIP or H.323 Perform basic call processing and destination-based routing for calls via SIP trunks to the service provider Provide DNS SRV lookup service to resolve outgoing and receive incoming calls Process registration and IM information from Cisco endpoints on the external network and use traversal-secure communication to pass the information to Expressway Core Collaboration Edge Licensing Cisco Expressway can be used for mobile and remote access with no additional investment. However, if business-to-business calling is enabled, Rich Media licenses are required. Each business-to-business call requires two Rich Media licenses. License Cisco Expressway for the anticipated maximum concurrent business-to-business sessions. page 27

32 Applications In addition to the call- and media-processing components, CPA for Midmarket Collaboration includes the following Cisco applications (Figure 17) to enhance usability, functionality, and management: Unity Connection to provide messaging (voic ) Unified CCX to provide sophistication to customer care for the organization in an easy-to-deploy fashion Cisco Prime Collaboration Provisioning Standard for user and device provisioning Applications Figure 17 - Architecture for Applications Table 10 lists the roles of the components in this architecture and the services that they provide. Table 10 - Components for Applications Module Component Description Applications Unity Connection Provides voic services Unified CCX Cisco Prime Collaboration Provisioning Standard Provides customer interaction and interactive voice response (IVR) services Provides user and service provisioning page 28

33 Cisco Unity Connection Unity Connection enables an organization s employees to access and manage voice messages in a variety of ways, including via inbox, web browser, Cisco Jabber, Cisco Unified IP Phone, TelePresence, smartphone, tablet, and more. Applications Recommended Deployment Deploy two Cisco Unity Connection servers in a cluster configuration that includes a Publisher node and a Subscriber node for redundancy (Figure 18). Note If full redundancy is not required, a single server may be deployed without loss of functionality. Benefits This deployment provides the following benefits: Easy access to messages enables fast response to time-sensitive communications. Secure messaging ensures critical business data is protected. Business applications are highly available and redundant. Deployment Best Practices The Unity Connection Automated Attendant feature provides a more interactive caller experience by directing calls without an operator and enabling messaging related to business hours or emergencies for example. Unity Connection provides templates to simplify the creation of automated attendants and holds the recordings for this feature. As such, a menu of the required recordings should be constructed and appropriate recordings made for each step of the call-management process. Figure 18 - Cisco Unity Cluster As a best practice, the majority of client traffic, such as IMAP and backup operations, should be directed to the Publisher node while the majority of call traffic should be directed to the Subscriber node in the Unity Connection cluster. page 29

34 As with other components in this architecture, integration with the organization s LDAP is highly recommended. This connection not only streamlines the initial deployment, but also allows end-user access to messaging functions using common credentials. Integration of Unity Connection with the organization s system enhances the functions of the application. For example, Microsoft s on premise Exchange or its hosted Office 365 offerings provide enhanced handling of voic while IBM Lotus Notes and Google s hosted offerings provide basic message delivery handling. This functionality notifies users of voic s that they have received and provides links to play the messages, enhancing users ability to respond quickly even when away from physical phones. Applications Cisco Unified Contact Center Express Unified CCX enables organizations to provide powerful, agent-based services to internal and external customers. These services enable customers to connect easily with the right employees in an organization for sales inquiries or product support. Recommended Deployment Deploy two Unified CCX servers in a cluster configuration that includes a Publisher node and a Subscriber node for redundancy (Figure 19). Note If full redundancy is not required, a single server may be deployed without loss of functionality. Figure 19 - Cisco Unified Contact Center Express Cluster Benefits This deployment provides the following benefits: Recorded greetings and customized prompts provide sophisticated call handling. External customer interaction is supported. Internal company communication for activities, such as help desk, is facilitated. page 30

35 Deployment Best Practices As with the other components in this architecture, Unified CCX should be deployed in a cluster configuration that includes a Publisher node and a Subscriber node. The cluster will be synchronized with the organization s LDAP and populated with end-user information. This minimal configuration enables external callers to dial a single number into the organization and then use a simple dial-by-name or dial-byextension functionality without the need for telephone operators to connect external calls. Depending on the organization s structure and business model, the following additional workflow configurations should be considered: Sales Customer Support Internal IT helpdesk Human Resources Applications These automated, call-directed workflows provide value to the organization by quickly and easily connecting a person with a need to the appropriate resource within the organization for assistance. For information about Cisco Unified Contact Center Express, see the data sheet. Cisco Prime Collaboration Provisioning Standard Cisco Prime Collaboration Provisioning Standard provides a centralized provisioning interface that simplifies administration of day-to-day activities, such as moves, adds, changes, and deletions (MACD) of user devices and services in an organization (Figure 20). Figure 20 - Cisco Prime Collaboration Provisioning Standard Recommended Deployment Deploy Cisco Prime Collaboration Provisioning Standard on the primary BE6000 server. A single instance of Cisco Prime is supported per organization. page 31

36 Benefits A consistent, unified approach simplifies the management of multiple Cisco collaboration technologies like Cisco Unified IP Phones, Cisco Unified CM, and other application servers. Features, such as bulk-based provisioning, phone MACDs, and consolidated views, simplify user and service-related configuration and administration. A self-service portal eases support by enabling users to make authorized changes. Applications page 32

37 Appendix Product List This product list identifies the Cisco products in this architecture along with their relevant software versions. Appendix Product Product Description Software Cisco Unified CM and IM and Presence Service Call control, instant messaging, and presence services Cisco Unity Connection Voic services 10.0 Cisco Expressway Core and Expressway Edge Mobile and remote access and business-to-business communications Cisco Contact Center Express Customer interaction management services 10.0 Cisco Prime Collaboration Standard Provisioning and monitoring services for voice and video deployments. Cisco TelePresence Conductor Video conferencing resource management Cisco TelePresence Server on Virtual Machine Video conferencing resource 3.1 Cisco ISR G2 PSTN gateway, SRST, audio conference resource, external connectivity to the Internet Cisco Unified IP Phone 6900 Series Public space, single line phone 9.4(1) IOS M Cisco Unified IP Phone 7800 Series General office use, multiple-line phone 10.1(1.9) Cisco Unified IP Phone 8900 Series General office use with available VPN client 9.4(1) Cisco Unified IP Phone 8831 IP conference phone 9.3(3) Cisco Jabber 1 Soft client with integrated voice, video, voic , and instant messaging and presence functionality for mobile devices and personal computers Cisco DX650 Smart-desk video endpoint 10.1(1.78) Cisco TelePresence System EX Series Personal TelePresence endpoint for the desktop TC7.1 Cisco TelePresence MX Series TelePresence multipurpose room endpoint TC7.1 Cisco TelePresence SX Series Integrator Series TelePresence endpoint TC Minimum Cisco Jabber version required to support Cisco Expressway mobile and remote access capabilities. Licensing Options This table identifies the licensing options. License Type Number of User Profiles User Connect Licensing (UCL) Essential User Connect Licensing (UCL) Basic User Connect Licenses (UCL) Enhanced / Enhanced Plus Unified Workspace Licensing (UWL) Standard Supported Device Type Analog / Voice Voice Video Video Video Number of Supported Devices Jabber Windows: 9.7 Jabber Mac: 9.6 Jabber ios: Jabber Android: 9.6 Single Single Single / Dual Multiple 1 Multiple 1 Unified Workspace Licensing (UWL) Professional page 33

38 License Type User Connect Licensing (UCL) Essential User Connect Licensing (UCL) Basic User Connect Licenses (UCL) Enhanced / Enhanced Plus Unified Workspace Licensing (UWL) Standard Unified Workspace Licensing (UWL) Professional Jabber IM & Presence 2 Yes Yes Yes Yes or WebEx Yes or WebEx Jabber Voice & Video Client Personal Video Conference Bridge Yes Yes Yes Optional Yes 3, screen licenses for 50 users or more Voice Messaging Optional Optional Optional Yes Yes WebEx Meetings Optional Optional Optional Optional Yes, 1:10 Meeting Center ports Contact Center Optional Optional Optional Optional Yes, 1:25 Standard Express Agent BE6K-UCL-ENH / BE6K-UCL-ENHP BE6K-UWL-BE CUWL-PRO-K9 NEW-UWL-PRO Appendix 1. Cisco UWL enables the first 10 devices per user on installation. If more devices are required, contact licensing@cisco.com. 2. Available to all users when using the Cisco Unified Communications Manager IM and Presence Service on the BE 6000 server. One-year WebEx Messenger subscriptions are available as an option for Cisco UWL users. 3. Cisco UWL Professional enables a 4-port personal video conference per user with the purchase of 50 or more Cisco UWL Professional licenses. Sample Order This sample order is for a deployment with redundant Cisco BE 6000 servers for an organization with 250 users. The products in this BOM were chosen to address the midmarket price point and to enable organizations to scale. Cisco has a range of products that provide various features and functionality. Organizations can choose different products based on their business needs. Product Quantity Cisco BE 6000 HD servers for redundancy 2 Cisco UCS 240 M3 server for Virtual TelePresence Server 1 page 34