Cisco Preferred Architecture for Midmarket Collaboration. Design Overview

Transcription

1 Cisco Preferred Architecture for Midmarket Collaboration Design Overview PA January 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 Video Endpoints... 8 Cisco Jabber... 8 Call Control...9 Recommended Deployment Benefits Deployment Best Practices Cisco Unified Communications Manager and Cisco IM and Presence Service Publisher-Subscriber Deployment Model...10 SIP Trunking Recommendations Cisco Unified Survivable Remote Site Telephony...11 Dial Plan...12 Endpoint Addressing...12 Call Routing...13 Class of Service...14 Conferencing...15 Recommended Deployment Audio Conferencing Video Conferencing Benefits Deployment Best Practices Table of Contents

3 Audio Conferencing Sizing Considerations...17 Architecture...17 Video Conferencing Sizing Considerations...18 Video Quality...19 Architecture...19 Redundancy Licensing Collaboration Edge...21 Recommended Deployment Headquarters Remote Site Mobile Workers Benefits Deployment Best Practices PSTN Firewall Cisco Expressway Expressway Core...26 Expressway Edge...26 Applications...27 Cisco Unity Connection Recommended Deployment Benefits Deployment Best Practices Cisco Unified Contact Center Express Recommended Deployment Benefits Cisco Prime Collaboration Standard Recommended Deployment Benefits Deployment Best Practices Table of Contents

4 Appendix...31 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 the 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) guides help Cisco Partners select appropriate architectures for their customers; understand the products that are used within the architectures; and obtain general design best practices. These guides should be used to support sales processes. 2. Cisco Validated Design (CVD) guides provide detailed steps for deploying components within the Cisco Preferred Architectures and should be used for planning, deployment, and implementation (PDI). 3. The Cisco Collaboration Solution Reference Network Design (SRND) guide provides detailed design options for Cisco Collaboration and should be referenced when an organization s 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 Sales engineers 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 for Cisco Partners 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 Advanced Video Using Cisco BE 6000 Technology Design Guide Help Desk Using Cisco UCCX Technology Design Guide page 1

6 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. Introduction Before personal collaboration tools and social media, many individuals were intimidated, even hesitant, to adopt new collaboration tools in their work environments. With advancements in collaboration applications and adoption of new technology in their personal lives, individuals are not only willing to adopt new collaboration tools in their workplaces, but also starting to expect them. Organizations can now feel comfortable providing collaboration applications that employees will quickly adopt and that provide maximum returns on investment. 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 a return on investment. Additionally, the architecture supports an advanced set of collaboration services that extend to mobile workers, partners, and customers through the following key services: Unified voice messaging Voice communications Instant messaging and presence page 2

7 High definition video and content sharing Rich media conferencing Enablement of remote and mobile workers Business-to-business voice and video communications 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 service availability 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 For simplicity, Table 1 lists the products in this architecture. 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 (Unified CM) Cisco Unified Communications Manager IM & Presence Service (IM and Presence Service) 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 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 Integrated Services Router (Cisco ISR) Modular router providing wide range of services in a single platform Cisco Unified Communications (Cisco UC) Applications Cisco Adaptive Security Appliance (Cisco ASA) Cisco Expressway Core Cisco Expressway Edge Cisco Unity Connection (Unity Connection) Cisco Unified Contact Center Express (Unified CCX) Cisco Prime Collaboration Standard (Cisco Prime) Acts as a firewall and VPN concentrator Enables interoperability with third-party systems Supports remote endpoint registration to Unified CM and enables business to business communications Provides unified messaging and voic services 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 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 CM Cisco 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 UC applications. Clustering allows the administration and configuration of deployed applications to be replicated to backup instances of those applications. If the primary application fails, Cisco UC services such as endpoint registration, call processing, messaging, business-to-business communication, and many others will continue to operate on the backup applications. 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 UC services in a single platform. In this architecture, the Cisco ISR provides the following functions (Figure 3): Audio conference bridge for 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 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 IP phones and video endpoints enable an organization s employees to make calls and connect to each other while mobile devices provide additional collaboration features, such as instant messaging and WebEx (Figure 4). Together, these devices enable users to access a variety of communication services, such as: Voice calls Video calls Conference call participation Voic Presence Instant messages (Cisco Jabber) Desktop sharing Endpoints Figure 4 - Architecture for Endpoints Recommended Deployment Because 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 Unified CM. The Unified CM cluster s failover mechanism provides endpoint registration redundancy. If a WAN failure occurs and endpoints at remote locations cannot register to Unified CM, they will use SRST functionality for local and PSTN calls, though some services, such as voic and presence, might not be available. page 7

12 Note 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 use to address its business needs. Endpoints Cisco Unified IP Phones Product Cisco Unified IP Phone , 2 Cisco Unified IP Phone 7800 Series 1, 2 Cisco Unified IP Phone 8900 or 9900 Series Cisco Unified IP Phone Description Public space, single line phone General office use, multiple-line phone General office use, VPN client, video phone IP conference phone 1. Does not support the mobile and remote access capabilities of Cisco Expressway. For more information about Cisco Expressway, see Collaboration Edge on page Use router-based VPN connectivity for remote locations and teleworkers devices. Cisco TelePresence Video Endpoints Product Cisco DX Cisco EX Series 2 Cisco MX Series 2 Cisco SX Series 2 Description Desktop collaboration video endpoint Desktop TelePresence video endpoint Self-standing collaboration room video endpoint Integrator series TelePresence video endpoint 1. Does not support the mobile and remote access capabilities of Cisco Expressway. 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 Cisco Jabber Release 9.6 or later Description Soft client with integrated voice, video, voic , and instant messaging and presence functionality for mobile devices and personal computers 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; enables Cisco Jabber desk phone control; and enables Cisco Jabber for audio and video deployment only Cisco ISR Provides Survivable Remote Site Telephony (SRST) to support call-control functions during a WAN outage page 9

14 Cisco IM and Presence Service 1 Provides Cisco Jabber support for instant messaging and presence and third-party federation 1. Jabber mobile requires IM and Presence Service Release 9.6 or later. Jabber for Mac requires IM and Presence Service. 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 Cisco 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, video and Cisco Jabber clients. Single call control and a unified dialing plan exist for voice, video, and Cisco Jabber clients. Critical business applications are highly availability and redundant. Deployment Best Practices Cisco Unified Communications Manager and Cisco IM and Presence Service Publisher-Subscriber Deployment Model A Cisco Unified CM or Cisco 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 Unified CM services, such as the ability to receive and process incoming calls (Figure 6). It is recommended that the 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 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. Native SIP trunks do not require SIP to H.323 conversion. 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). Figure 7 - Cisco SRST page 11

16 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. Call Control 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 any successful 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 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 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. 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 page 12

17 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. Figure 8 shows example addressing recommendations. Call Routing Numeric Call Routing Call Control The +E.164 format for numeric addresses is recommended because it: Is globally unique and widely used in voice networks Is widely deployed in directories, such as Active Directory, 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 8 shows example addressing recommendations. Figure 8 - Endpoint Addressing Recommendations 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 page 13

18 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 voice and video services are not affected when multiple addresses are used. Call Control 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 Unified CM and IM and Presence Service with the organization s Active Directory. Though Unified CM allows the creation of local user contacts, Active Directory integration is required when using Cisco Jabber. Cisco Unified CM and IM and Presence Service pull user and contact information from Active Directory and synchronize user parameters name, surname, username, telephone number and SIP URI when changes occur. Use the telephonenumber and mail attribute to populate the Cisco Unified CM directory. 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. Table 3 - Class of Service by Call Type Call Type Emergency Local National International Class of Services Lobby Phones Employee Standard Sales Executives page 14

19 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 PVDMs and 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 Edge Cisco ISR Provides voice conferencing resources There are three types of conferences: Ad hoc 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 15

20 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 Use CUWL-Pro licensing to enable users for personal ad-hoc and rendezvous video conferences. Deploy TelePresence Conductor on the primary Cisco BE 6000 server and integrate with Unified CM. Deploy a redundant TelePresence Conductor on the backup Cisco BE 6000 server and integrate with Unified CM. Deploy 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 resources (PVDMs and TelePresence Server) enable greater scale and redundancy. 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. page 16

21 Using Cisco ISRs for a variety of functions including voice gateway, SRST, conferencing, and WAN 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 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 17

22 Figure 10 - MRGL Example Conferencing Video Conferencing For deployments with 1,000 or fewer users and with the Cisco BE6000 used for Cisco UC applications, we recommend deploying Midmarket Virtual TelePresence Conductor with Cisco TelePresence Server on Virtual Machine (vts) for video conferencing. The following platforms are also available for deployments up to 1,000 users: Cisco Multiparty Media 310 and Cisco Multiparty Media 320. All these platforms offer the following flexible licensing and capacity options: All platforms support pay as you grow licensing. Cisco vts has several 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 BOM on page 34 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 82 page 18

23 Next, consider 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 of the above 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 448p 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 19

24 Figure 11 - Cisco UCS C240 M3 in the Video Conferencing Architecture Conferencing Acting as a conference controller and manager between Unified CM and the TelePresence Server, TelePresence Conductor handles conference creation, deletion, resource selection, and advanced video functionality like Optimized Conferencing and ActiveControl. Cisco Unified CM can (1) invoke the TelePresence Conductor as an ad-hoc conference bridge through media resource groups and (2) direct calls to TelePresence Conductor for rendezvous conferences through route patterns. TelePresence Conductor handles ad-hoc and rendezvous conferences on a first come, first served basis, making them best effort services. Multiple virtual IP addresses are configured on TelePresence Conductor, allowing it to be added as both an ad-hoc conference bridge and as a SIP Trunk to Unified CM. Rendezvous video conferences with TelePresence Conductor rely on the Cisco Unified CMs dial plan to route these calls out the proper 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 16. Redundancy Licensing The Cisco Midmarket Virtual TelePresence Conductor should be deployed in a redundant, two-server cluster configuration with each TelePresence Conductor deployed on a separate Cisco BE 6000 HD server. Database replication ensures both Conductors share the same configuration and will continue to allow video conference capability in the event of a failure on the primary Cisco BE 6000 HD server. Users who require video conferencing should be enabled through CUWL-Pro licenses and the Cisco Personal Multiparty offering. All CUWL-Pro 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 CUWL-Pro 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). page 20

25 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 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 Collaboration addresses these needs with the Collaboration Edge architecture in Figure 12. Collaboration Edge Figure 12 - 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 Internet Edge Expressway Edge Allows secure communication including client registration and business-to-business calling through an organization and provides other services, such as automated service discovery using DNS SRV lookup Expressway Core Firewall 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 Unified CM Controls access into and out of the organization s network and provides other services, such as Network Address Translation (NAT) and DMZ creation page 21

26 Gateway Cisco ISR Enables local PSTN connectivity Cisco Unified Border Element (CUBE) Enables connectivity from an organization s network to the service provider network for SIP trunks (Cisco ISR feature) Remote Site Cisco ISR Enables PSTN and VPN functionality Mobile Worker Virtual Private Network (VPN) Provides secure access to an organization s resources, such as business applications, servers, or , regardless of where the user is when connecting Collaboration Edge 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 a firewall to control access in to and out of the organization s network. Deploy Cisco Expressway Core and Edge to enable remote Jabber and TelePresence endpoint registrations, IM and presence, and secure business-to-business connectivity through the firewall. Enable VPN concentrator functionality on the firewall so that remote sites and mobile workers can connect to headquarters to access business applications. Note For H.323 ISDN video support, deploy a Cisco TelePresence ISDN GW 3241 gateway. Remote Site Deploy Cisco ISR as the PSTN gateway. Enable VPN on the Cisco ISR so that endpoints at this site connect to the headquarters through a VPN tunnel. Note If teleworkers use routers with VPN capabilities, they can connect to headquarters through a VPN tunnel like a remote site. If an organization connects different locations via a dedicated MPLS network, VPN does not need to be enabled to connect to remote sites. Mobile Workers Deploy software-based VPN clients that connect to the VPN concentrator at headquarters. Deploy supported Jabber and video endpoints with Cisco Expressway that register to Unified CM. See Endpoints on page 7. page 22

27 Benefits 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 mobile and remote access capabilities and registration to Unified CM for remote mobile users who use Cisco Jabber or supported Cisco TelePresence video endpoints. Unified communication functionality, such as calling, presence, instant messaging, voic and corporate directory contacts are also available for Cisco Jabber and TelePresence endpoints when registered via Cisco Expressway. VPN enables remote sites and mobile users to connect to the headquarters. Collaboration Edge Deployment Best Practices PSTN 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 13). Figure 13 - PSTN Connectivity 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 9Table 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 page 23

28 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 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. Collaboration Edge Firewall 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. A firewall is the main security device that protects a private network from the outside world. When external access to an organization s internal resources is required, a firewall DMZ is created to host public-facing resources and to control access. The firewall uses NAT to map publicly routed IP addresses to IP addresses in the DMZ and will: Allow communication from the inside network to the DMZ network and from the inside network to the outside network Prohibit communication from the outside network to the inside network Control communication to and from the servers inside and outside networks Using an existing firewall or deploying the Cisco ASA 5500 series at the organization s headquarters as the firewall is recommended (Figure 14). Because this firewall is a security device and a component of the Cisco Expressway deployment, ensure that the Expressway Edge is placed in the DMZ along with any other externally accessible servers that the organization has. For more information, see Cisco Expressway on page 25. For remote sites and mobile workers to connect securely, enable VPN concentrator functionality on the Cisco ASA 5500 firewall at the organization s headquarters. Deploy a Cisco ISR at remote sites and teleworker locations to connect as VPN clients to the VPN concentrator at headquarters, essentially becoming part of the central network at headquarters. This allows devices and endpoints to connect directly to the Unified CM and IM and Presence Service without using VPN software at those locations. If mobile workers require access to the internal data network, as well as voice and video services, then software VPN clients on their mobile devices and personal computers should be used for full network connectivity. Note Remote sites that use MPLS to connect to the organization s network do not need VPN. page 24

29 Figure 14 - Cisco ASA Firewall and VPN Concentrator Collaboration Edge Table 10 lists the recommended VPN devices based on location. Table 10 - Recommended VPN Devices Location Headquarters 1 Remote Sites Teleworker Sites Mobile Devices and Personal Computers VPN Device Cisco ASA 5500 Series concentrator Cisco ISR G Series Cisco ISR G2 880 Series or Cisco Unified 8900/9900 Series IP Phones with VPN client Software VPN client 1. Small deployments with fewer than 5 remote sites can use the Cisco ISR G at headquarters as firewall and VPN concentrator. However, the Cisco ASA 5500 series is recommended for scale and performance. For more information about Cisco ASA 5500 Series, see the data sheet. Cisco Expressway Firewall traversal is required to separate an organization s network and IP addresses from the external network or the Internet and provide a seamless secure path for call and other collaboration traffic through firewalls. For firewall traversal, Cisco Expressway Core and Expressway Edge are recommended (Figure 15 and Figure 16). Deploying these two platforms together enables the following: Endpoints to register to Unified CM without a VPN Business-to-business video communication Figure 15 - Traversal for Registrations Through Firewall with Expressway Core and Expressway Edge page 25

30 Figure 16 - Traversal for Business-to-Business Calls Through Firewall with Expressway Core and Expressway Edge Collaboration Edge 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 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 Unified CM for SIP registration or IM and Presence Service for IM and presence See Endpoints on page 7 for more information. 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 page 26

31 Applications In addition to the call- and media-processing components, CPA for Collaboration includes the following Cisco applications (Figure 17) to enhance the usability, functionality, and management of the midmarket solution: 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 for user and device provisioning Applications Figure 17 - Architecture for Applications Table 11 lists the roles of the components in this architecture and the services that they provide. Table 11 - Components for Applications Module Component Description Cisco UC Applications Unity Connection Provides voic services Unified CCX Cisco Prime Provides customer interaction and interactive voice response (IVR) services Provides user and service provisioning page 27

32 Cisco Unity Connection Cisco Unity Connection enables an organization s employees to access voice messages from an IP phone, mobile phone, web browser, client, or a desktop client like Cisco Jabber. Recommended Deployment As with Unified CM, deploy two Cisco Unity Connection servers in a cluster configuration (Figure 18), also comprised of a Publisher node and a Subscriber node, and then connect to Unified CM via SIP trunks. For information about clustering and SIP trunking, see Cisco Unified Communications Manager and Cisco IM and Presence Service on page 10. Note If full redundancy is not required, a single server may be deployed without loss of functionality. Applications 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 availability 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 similar 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. Unity Connection supports synchronization with LDAP, and the connection from Unity Connection to LDAP is read only. This connection enables end users to use LDAP credentials when accessing the web-based page 28

33 components with Unity Connection. An SSL connection between the LDAP server and Unity Connection is recommended, so user account and password information is encrypted. Cisco Unified Contact Center Express Contact Unified Center Express (Unified CCX) enables organizations to connect easily with the right employees in an organization for help with sales inquiries or product support for example. Applications Recommended Deployment As with Unified CM, deploy two Unified CCX servers in a cluster configuration (Figure 19), also comprised of a Publisher node and a Subscriber node, and then connect to Unified CM via the Java Telephony Application Programming Interface (API). See Cisco Unified Communications Manager and Cisco IM and Presence Service on page 10 for information about clustering and SIP trunking. With SRST enabled, even if a phone is operating in SRST mode, the active Unified CCX node will continue to manage calls without loss of functionality in the event of a WAN failure. Note that this deployment does not support call recording. 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 29

34 Cisco Prime Collaboration Standard Cisco Prime 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). Applications Figure 20 - Cisco Prime Recommended Deployment Deploy Cisco Prime on the primary BE6000 server. A single instance of Cisco Prime is needed per organization. Benefits A consistent, unified approach simplifies the management of multiple Cisco collaboration technologies like Cisco Unified IP Phones, Unified CM, and other application servers. Configuration and administration of users and related services is simplified by features, such as bulkbased provisioning, phone MACDs, and single and consolidated views of user and user services. Eases support by enabling users to make authorized changes via a self-service portal. Deployment Best Practices Ensure that Unified CM is configured to auto-register IP phones. For site and dial plan provisioning, use the Cisco Unified Configurator for Collaboration (CUCC) tool. Though not required, using LDAP is recommended to facilitate user entry and provide a single logon for Cisco Prime services. page 30

35 Appendix Product List This product list identifies the components in this architecture, as well as the software versions and part numbers to use when ordering. Appendix Functional Area Product Description Software Part Number Call Control Cisco Business Edition 6000 with up to 1000 users Call Control and IM and Presence Service Cisco Unified Communication Manager, Cisco Unified Instant Messaging server 10.0 BE6K-STBDL-PLS-K9, BE6K-ST-BDL-K Voic Cisco Unity Connection 10.0 External Connectivity Expressway-C and Expressway-E 8.1 Conference Bridge Controller Cisco Conductor PSTN Gateway ISR G2 IOS M C3925-VSEC/K9, C2951- VSEC/K9, CISCO881-SEC-K9 Video Conference Bridge UCS Server Firewall User Licenses Cisco UCS C240 with additional HDD and RAM ASA 5500 series firewall and VPN concentrator Top level BE6K users license and starter 25 user CUWL licenses Enhanced User Licenses Enhanced user with 1 endpoints for voice, video and IM Enhanced Plus User Licenses Enhanced user with 2 endpoints for voice, video and IM CUWL Business User Licenses CUWL Business user with multiple endpoints for voice, video and IM UCSC-EZ-C , UCS-HDD300GI2F105=, UCS-MR-1X082RY-A= ASA9.1 ASA5505-SSL10-K8 R-CBE6K-K9 BE6K-START-UWL25 BE6K-UCL-ENH BE6K-UCL-ENHP BE6K-UWL-BE User Voic License UC user voic BE6K-VM-UPG TelePresence Room System Licenses Video Conference Bridge Device licenses for the TelePresence video endpoints such as SX series or MX series room systems Virtual TelePresence Server and screen license BE6K-UCL-TP-RM 3.0 R-VTS-K9 TelePresence Conductor TelePresence Conductor 3.0 R-VMCNDTRM-K9 IP Phones VPN Client Phones Unified IP Phone with one or two lines Unified IP Phones with VPN client SIP69xx SIP89xx CP-6901-C-K9=, CP-7821-K9= CP-8941-K9=, CP-9951-C-K9= page 31

36 Functional Area Product Description Software Part Number Video Phones Video Endpoints User Licenses Smart desk video endpoints DX600 series or EX series Collaboration room Endpoints such as SX series or MX series room systems Top level BE6K users license and starter 25 user CUWL licenses Enhanced User Licenses Enhanced user with 1 endpoints for voice, video and IM Enhanced Plus User Licenses Enhanced user with 2 endpoints for voice, video and IM CUWL Business User Licenses CUWL Professional Licenses Contact Center Agent Licenses CUWL Business user with multiple endpoints for voice, video and IM CUWL Professional user with multiple endpoints for voice, video and IM Top level contact center and essential agent license sipdx , TC7.1 TC7.1 CP-DX650-K9, CTS-EX90-K9 CTS-SX20-PHD4X-K9, CTS-MX300-K9 R-CBE6K-K9 BE6K-START-UWL25 BE6K-UCL-ENH BE6K-UCL-ENHP BE6K-UWL-BE CUWL-PRO-K9 NEW-UWL-PRO CCX-90-N-E-LIC SP-ESW-CCX90NEL User Voic Licenses UC user voic BE6K-VM-UPG Appendix 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) Business Supported Device Type Analog / Voice Voice Video Video Video Number of Supported Devices 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 Yes 3, screen licenses for 50 users 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 page 32

37 License Type User Connect Licensing (UCL) Essential User Connect Licensing (UCL) Basic User Connect Licenses (UCL) Enhanced / Enhanced Plus BE6K-UCL-ENH / BE6K-UCL-ENHP Unified Workspace Licensing (UWL) Business BE6K-UWL-BE Unified Workspace Licensing (UWL) Professional CUWL-PRO-K9 NEW-UWL-PRO Appendix 1. CUWL 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 Unified Communications Manager IM and Presence Service on the BE 6000 server. One-year WebEx Messenger subscriptions are available as an option for CUWL users. 3. CUWL Pro enables a 4-port personal video conference per user after the first 50 users. If more devices are required, contact licensing@ cisco.com. 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 BE 6000 HD servers for redundancy 2 UCS 240 M3 server for Virtual TelePresence Server as a conference bridge with add-on disk and memory ISR 3900 series for headquarters PSTN gateway with two hundred (200) SRST and CUBE licenses 1 ISR 2900 series for branches with twenty five (25) SRST licenses each and PSTN interfaces 2 ISR 881 for teleworkers 2 ASA 5505 Firewall for security 2 SX20 TelePresence room system 1 MX300 TelePresence systems 2 Quantity 1 page 33