Cisco Preferred Architecture for Midmarket Video. Design Overview

Transcription

1 Cisco Preferred Architecture for Midmarket Video 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 Endpoints...6 Recommended Deployment... 6 Cisco TelePresence and Video Endpoints... 7 Cisco Jabber... 7 Call Control...8 Recommended Deployment... 9 Benefits... 9 Deployment Best Practices... 9 Cisco Unified Communications Manager and IM and Presence Service... 9 Publisher-Subscriber Deployment Model...9 SIP Trunking Recommendations...10 Dial Plan Endpoint Addressing...10 Call Routing Conferencing...13 Recommended Deployment...14 Benefits...14 Deployment Best Practices...14 Sizing Considerations Video Quality Architecture Redundancy...17 Licensing...17 Table of Contents

3 Collaboration Edge...18 Recommended Deployment Benefits...19 Deployment Best Practices...19 Cisco Expressway Core Cisco Expressway Edge Licensing Applications...21 Cisco Prime Collaboration Provisioning Standard Recommended Deployment Benefits Appendix...23 Product List Licensing Options Sample Order Sample Bill of Materials Personal Multiparty Sample Bill of Materials Screen Licenses Table of Contents

4 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 Voice, Video, and 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 Video Design Overview (CPA for Midmarket Video) is for: Sales teams that sell and design video communications environments Customers and sales teams who want to understand the overall Cisco Video 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 for by: Recommending products in the Cisco Video portfolio that are built for the midmarket and that provide appropriate video feature sets for this market Detailing a midmarket video 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 Collaboration Edge Using Cisco BE 6000 Technology Design Guide page 1

5 Introduction Today s business environment provides numerous challenges for organizations that are trying to expand business while containing expense. Additionally, organizations are more often geographically dispersed because of mergers and acquisitions. This physical separation of team members creates a compelling need for rich communication tools. Introduction Not long ago, organizations realized the added value that video solutions brought to their business through increased employee productivity and enhanced customer relationships. However, interoperability among video solutions was sparse, and most solutions were difficult to deploy and use. Since then, significant advances have been made in video technology that simplify deployment, improve interoperability, and enhance the overall user experience. Additionally, video communication is starting to be widely adopted by individuals in their personal lives. Before personal video tools and social media, many individuals were intimidated, even hesitant, to adopt video communication solutions in their work environments. With advancements in video technology and adoption of new technologies in their personal lives, individuals are not only willing to adopt video in their workplaces, but also starting to expect it. Organizations can now feel comfortable providing video tools that employees will quickly adopt and that provide maximum value. These new 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 Video 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 Video Technologies and use cases is available on Cisco.com. Architectural Overview The CPA for Midmarket Video provides an end-to-end video solution. 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 page 2

6 advanced set of collaboration services that extend to mobile workers, partners, and customers through the following key services: High definition video and content sharing Rich media conferencing Enablement of mobile and remote workers Business-to-business video communications Introduction The CPA for Midmarket Video is designed to work with your existing voice platform whether from Cisco or another vendor or as a standalone video solution. The benefits of connecting voice and video architectures include breaking down barriers to unified communications and preventing installation of another technology island within an organization. Moreover, because of the adaptable nature of Cisco endpoints and their support for IP networks, this design 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 video solution is deployed with proper Quality of Service (QoS) configured throughout the network. 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 Video, 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. Additionally, centralizing services simplifies management and administration of an organization s collaboration deployment. Figure 1 - Cisco Preferred Architecture for Midmarket Video page 3

7 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 Video 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 TelePresence video endpoints and Cisco Jabber Provides endpoint registration, call processing, and media resource management Provides instant messaging and presence services Enables users for real-time voice, video, and instant messaging communications Conferencing Cisco TelePresence Conductor Manages video conferencing resources Cisco TelePresence Server Provides video conferencing resources Collaboration Edge Cisco Expressway Core Enables interoperability with third-party systems and firewall traversal Applications Cisco Expressway Edge Cisco TelePresence ISDN Gateway Cisco Prime Collaboration Provisioning Standard Supports remote endpoint registration to Cisco Unified CM and enables business-to-business communications Enables interoperability with H.320 video endpoints 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 Video 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

8 Figure 2 - Cisco BE 6000 Applications Introduction In this architecture, the following five applications and Cisco Prime Collaboration Provisioning Standard are deployed on one Cisco BE 6000 server while a second instance of each of the five 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 TelePresence Conductor Cisco Expressway, comprised of Expressway Core and Expressway Edge 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 three additional Cisco UC applications on each BE 6000 server. High Availability The CPA for Midmarket Video 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 Video design ensures high availability through the use of redundant power supplies, network connectivity, and disk arrays. page 5

9 Endpoints Cisco provides endpoints with a wide range of features, functionality, and user experiences. Because endpoints range from desktop video phones and softclients to three-screen 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 Presence Instant messages (Cisco Jabber) Desktop sharing Endpoints Figure 3 - Architecture for Endpoints Recommended Deployment Because Cisco Unified CM is the call control server for this deployment, Session Initiation Protocol (SIP) should be used to register Cisco Jabber clients and TelePresence video endpoints directly to the Cisco Unified CM. The Cisco Unified CM cluster s failover mechanism provides endpoint registration redundancy. The following endpoints are recommended because they provide the optimal features for this design at 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. page 6

10 Cisco TelePresence and Video Endpoints Product Description Cisco EX Series 1 Personal TelePresence endpoint for the desktop Cisco MX Series 1 TelePresence multipurpose room endpoint Cisco SX Series 1 Integrator series TelePresence endpoint Endpoints 1. Requires TC 7 or later to support features in this deployment. 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 7

11 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 4 - 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 Provides Cisco Jabber support for instant messaging and presence and third-party federation page 8

12 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 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 for both Cisco TelePresence endpoints and Jabber clients. Single call control and a unified dialing plan exist. 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 5). 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 9

13 Figure 5 - Cisco Unified CM Cluster Call Control Dial Plan 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, and 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, and Cisco Expressway Core. 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. 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 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 have 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 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 page 10

14 The use of both a numeric and alphanumeric dial plan is recommended for video deployments, 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. Call Control 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 video endpoint can be assigned both a numeric address and an alphanumeric alias that the organization s users can reach by dialing either. Additionally, any registered Cisco Unified CM endpoint can be reached by dialing its telephone number followed by the domain. For example, John Smith can also be reached by dialing @company1. com from both internal and external locations on the Internet. Call Routing Numeric Call Routing The +E.164 format for numeric addresses is recommended because it: Is globally unique 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 Enterprise (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 6 provides an example for the endpoint addressing recommendations. page 11

15 Figure 6 - 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. Note that 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 12

16 Conferencing The ability for three or more people to communicate in real time by using video technologies is a core component of any video deployment. Conferencing builds upon existing infrastructure in place for pointto-point calls, offering an organization s users a consistent video experience regardless of how many participants are involved (Figure 7). Conferencing Figure 7 - Architecture for Conferencing Table 3 lists the roles of the components in this architecture and the services that they provide. Table 3 - Components for Conferencing Module Component Description Call Control Cisco Unified CM Communicates with TelePresence Conductor for allocation of video conferencing resources Conferencing Cisco TelePresence Conductor Manages video conferencing resources Cisco TelePresence Server Provides video 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. Scheduled: A conference that guarantees conferencing resources will be available for callers at a predetermined start time. page 13

17 Note The components required for scheduled conferences are not part of this architecture. However, Cisco TelePresence Management Suite (TMS) can be used for scheduled video conferences. See the data sheets for more information. Conferencing Recommended Deployment 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 regardless of endpoint type. Dedicated Cisco Conductor and TelePresence Server resources enable greater scale and redundancy. Cisco Unified CM s Intelligent Bridge Selection ensures the appropriate video resource is allocated for ad-hoc conferences. Deployment Best Practices 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 page 14

18 instances. Up to two of these vts OVAs can be deployed per Cisco UCS C240 M3 server. The Sample Bill of Materials on page 25 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 4 provides guidance for number of required video ports. Conferencing Table 4 - Video Conference Port Recommendations Number of Users Video Conference Ports 100 users users users users users 72 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. 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, Table 5 shows the maximum capacity of the vts 8-core/16vCPU at different video resolutions for planning purposes. Table 5 - 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. page 15

19 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. Conferencing 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 8). Figure 8 - Cisco UCS C240 M3 in the Video Conferencing Architecture 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. page 16

20 Figure 9 - MRGL Ad-hoc Conference Request Conferencing 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. TelePresence Conductor handles ad-hoc and rendezvous conferences on a first-come, first-served basis, making them best-effort services. 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. 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 needed 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 17

21 Collaboration Edge Collaboration with video provides a higher level of user interaction. Providing functionality to mobile users by leveraging the Internet has increased significantly over the past few years, and for many organizations, video 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 Video addresses these needs with the Collaboration Edge architecture in Figure 10. Collaboration Edge Figure 10 - Architecture for Collaboration Edge Table 8 lists the roles of the components in this architecture and the services that they provide. Table 6 - 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 TelePresence ISDN Gateway 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 interoperability with H.320 video endpoints Recommended Deployment Deploy two Cisco Expressway Core and Edge servers in a clustered configuration at headquarters to enable remote Jabber and TelePresence video endpoint registrations, IM and presence, and secure business-tobusiness connectivity through the firewall. page 18

22 Note If full redundancy is not required, a single server may be deployed without loss of functionality. Note If H.320 interoperability is required, the Cisco TelePresence ISDN GW 3241 can be added as an option. This gateway integrates with Unified CM using SIP trunks, providing routing for ISDN video calls to the ISDN GW 3421 gateway. For information about ISDN GW 3241, see the data sheet. If integration with an existing H.323 video network is required, the Cisco Expressway Core can be neighbored to the existing H.323 gatekeeper, providing interoperability between SIP and H.323 video endpoints. Collaboration Edge Benefits This deployment provides the following benefits: Cisco Expressway provides calling, presence, instant messaging, voic , and corporate directory services for Internet-connected Cisco Jabber and TelePresence video endpoints. Cisco Expressway enables video communications between organizations, partners, and vendors via the Internet. Deployment Best Practices 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 11) and secure businessto-business communications (Figure 12). 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 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 11 - Traversal for Registrations Through Firewall with Expressway Core and Expressway Edge page 19

23 Figure 12 - Traversal for Business-to-Business Calls Through Firewall with Expressway Core and Expressway Edge Collaboration Edge Cisco Expressway Core Place Expressway Core in the trusted network inside the organization, and 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 6 for more information. Cisco Expressway Edge Place Expressway Edge in a DMZ because it is reachable directly from the untrusted, external network; the organization s firewall policies control the communication to and from this server. Expressway Edge will: Licensing 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 Cisco Expressway can be used for mobile and remote access with no additional investment. However, if business-to-business calling or integration with an existing on-premise H.323 network is enabled, Rich Media licenses are required. Each business-to-business call requires two Rich Media licenses while on-premise SIP-to-H.323 interworking calls require one. License Cisco Expressway for the anticipated maximum concurrent business-to-business and on-premise SIP-to-H.323 interworked sessions. page 20

24 Applications In addition to the call- and media-processing components, CPA for Midmarket Video includes Cisco Prime Collaboration Provisioning Standard for user and device provisioning (Figure 13) to enhance usability, functionality, and management. Applications Figure 13 - Architecture for Applications Table 7 lists the roles of the components in this architecture and the services that they provide. Table 7 - Components for Applications Module Component Description Applications Cisco Prime Collaboration Provisioning Standard Provides user and service provisioning page 21

25 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 14). Applications Figure 14 - 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. 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. page 22

26 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 Cisco Expressway Core and Expressway Edge Cisco Prime Collaboration Standard Call control, instant messaging, and presence services 10.0 Mobile and remote access and business-to-business communications 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 TelePresence ISDN Gateway H.320 gateway 2.2 Cisco Jabber 1 Soft client with integrated voice, video, voic , and instant messaging and presence functionality for mobile devices and personal computers 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 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 page 23

27 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 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 Cisco TelePresence SX20 room system 1 Cisco TelePresence MX300 systems 2 Cisco TelePresence EX90 desktop systems 2 User, Agent, and Server licenses page 24