Preferred Architecture for Enterprise Collaboration

Transcription

1

2 Preferred Architecture for Enterprise Collaboration Part 2: Collaboration Edge, Core Applications and Sizing Glen Lavers, Luca Pellegrini, Matthew Jordy, Laurent Pham BRKCOL-2421

3 Preferred Architecture for Enterprise Collaboration Cisco Live Session Details There are two Preferred Architecture for Enterprise Collaboration sessions at Cisco Live this week:» BRKCOL-2420 Part 1: Call Control, Conferencing Wednesday, June 10 8 AM You are here» BRKCOL-2421 Part 2: Collaboration Edge, Core Applications, and Sizing Wednesday, June 10 1 PM

4 Agenda What is "Preferred Architecture"? Collaboration Edge Expressway B2B Communications Mobile and Remote Access Design Considerations PSTN Access Voice and Video Gateways Cisco Unified Border Element Design Considerations Core Applications Unity Connection Prime Collaboration Deployment Prime Licensing Manager Simplified Sizing Call Control (Communications Manager and IM & Presence) Conferencing (TMS, Telepresence Server, Conductor) Collaboration Edge Applications

5 What is Preferred Architecture?

6 The Preferred Architecture for Collaboration process was created to simplify selling and designing. It is a design where Cisco experts make the design decisions for you following the 80/20 rule. Its advise from the SRND you would give your best friend if they asked you just tell me what I need to do.

7 What does the PA aim to accomplish? Simplify Empower Simplify selling and deployment Allow generalists to understand collaboration deployment and what is preferred Clarify Guidance Reduce complexity of overall deployment choices Give existing customers a reference to move their deployment toward Influence Feed simplification (and design issues) back to Development

8 PA Process Figure it out: Define Collaboration Preferred Architecture Feedback: Feed gaps found during the build and validate phase back into product teams Build and validate: Build it in the lab and validate concepts Write it down: Document Preferred Architectures for the field and partners Extend: Move it into GB test beds, Cisco on Cisco, Alpha and EFT process Define Define additional Preferred Architectures (Voice, Video)

9 Collaboration Preferred Architectures & CVDs PA Overview PA CVD Cisco Validated Design Cisco Validated Design Applications Coming Soon!!! Pre-Sales Process Design Overview Document Targeted to Presales What (w/ Some Why)! Post-Sales process Detailed Design and Deployment Guidance Post Sales Design and Deployment What, Why, and How! Process Driven Guide Post-Sales Process Detailed, Deployment Guidance Post Sales Design and Deployment What, Why, and How! Process Driven Guide Plugs into the PA CVD

10 Mid Market PA/CVD Document Mapping! Use Case PA Overview CVD Voice Only PA for Midmarket Voice Unified Comm. using BE6000 CVD Collaboration Edge Using BE6000 CVD Standalone Video PA for Video Video Conferencing using BE6000 CVD Full Collaboration * PA for Midmarket Collaboration Collaboration Edge Using BE6000 CVD Unified Comm. using BE6000 CVD Video Conferencing using BE6000 CVD Collaboration Edge Using BE6000 CVD Helpdesk using Cisco UCCX CVD * Fits both Mid-Market and Enterprise

11 Enterprise PA/CVD Document Mapping! Use Case PA CVD Voice N/A N/A Standalone Video PA for Video Video Conferencing using BE6000 CVD Full Collaboration * PA for Enterprise Collaboration PA for Enterprise Collaboration CVD * Fits both Mid-Market and Enterprise

12 Preferred Architecture for Collaboration Enterprise Cisco Validated Design (CVD) Call Control UCM, IM&P, ISR, CUBE Conferencing UCM, Conductor, TS, TMS Edge UCM, Expressway, CUBE, ISR Applications Ucx, PCD, PLM Functions: Dial Plan (Dialing Habits, Endpoints/ILS/GDPR), Trunking, SRST, CTI, DNS, Cert Mgmt, Provisioning, EM Functions: Ad hoc, Rendezvous, Scheduled, CMR, CMR Hybrid, Personal Multiparty Functions: Mobile Remote Access (MRA), B2B, IM&P Federation, PSTN Access, ISDN Video Functions: Applications and Tools: VM Deployment, Licensing, Voice Messaging Architecture: Component Role, HA, Security, Scalability Deployment: Process and Configuration S i z i n g Sizing Functions: Sizing numbers for products built on a set of calculated assumptions

13 Call Control Architecture and Deployment Models: Simplification Recommendation: Centralized Call Processing Model (Single Call Processing Cluster) Full-Mesh Distributed Call Processing Deployment Model (Multiple Call Processing clusters) may be required. This model is based on multiple iterations of the Centralized Call Processing Deployment Model IM&P UCM IM&P UCM IM&P UCM Branch1 Branch2 Branch1 Branch2 Branch1 Branch2

14 Preferred Architectures Benefits Single Collaboration Design (Voice, Video, IM&P, Conferencing, Edge) Collaboration-friendly dial plan which makes easy to add video to voice, IM&P to voice and video Simplified: deployment model, design, dial-plan, video architecture, IM&P integration, sizing, etc. Modular architectural approach for scalability Add additional services avoiding re-configuration costs Future Proof the Architecture Customizing the PA??? GO TO THE SRND FOR GUIDANCE

15 Collaboration Edge

16 Collaboration Edge Design Objectives Connect to customers and partners, independent of the technology they are implementing and the public network they are using. Provide for a resilient, flexible and extendable architecture. Provide any hardware and software client with the ability to access any public network (Internet and PSTN). Provide secure VPN-less access to collaboration services for Cisco mobile and remote clients and endpoints.

17 Introducing Cisco Collaboration Edge Architecture Industry s Most Comprehensive Any-to-Any Collaboration Solution All the capabilities of Cisco Anyto-Any collaboration to-date TDM & analog gateways ISDN Video gateways Session border control Firewall traversal Standards-based & secure B2B Consumers Mobile Workers Teleworkers TDM or IP PBX PSTN or IP PSTN 3rd Parties Branch Office Cloud Services Analog Devices

18 Overview

19 SRV Records for B2B and MRA SRV record format for SIP and H.323 (RFC 2782) _sip. _tcp.example.com IN SRV expe.example.com _collab-edge. _tls.example.com 8443 Name of the service Protocol and domain name (TCP, UDP...) DNS Time-To-Live: how much time the server caches the record before it flushes the cache DNS Class. Always IN Priority: Lowest priority means preferred. Port: TCP or Weight: loadbalances records UDP port for the service with same priority Targed: hostname or IP Address for the host Providing the service

20 Service Discovery _sips._tcp.example.com IN SRV bigbox.example.com. _sips._tcp.example.com IN SRV smallbox.example.com. _sips._tcp.example.com IN SRV backupbox.example.com. Smallbox Backupbox 40% Bigbox 60% _sips._tcp.example.com? Dial: luca@example.com

21 Service Discovery _sips._tcp.example.com IN SRV bigbox.example.com. _sips._tcp.example.com IN SRV smallbox.example.com. _sips._tcp.example.com IN SRV backupbox.example.com. Smallbox Backupbox 40% Bigbox 60% Dial: luca@example.com

22 Cisco Collaboration SRV Records SRV record format for SIP and H.323 (RFC 2782) SIP B2B _sips._tcp.domain 5061 TLS _sip._tcp.domain 5060 TCP _sip._udp.domain 5060 UDP H.323 B2B _h323ls._udp.domain 1719 RAS _h323cs._tcp.domain 1720 H.225 MRA _collab-edge._tls.domain 8443 Jabber login _xmpp-server._tcp.domain 5269 XMPP Federation

23 Expressway Firewall Traversal Basics Enterprise Network DMZ Outside Network Unified CM Expressway-C Firewall Expressway-E Firewall 1. Expressway-E is the traversal server installed in DMZ. Expressway-C is the traversal client installed inside the enterprise network. 2. Expressway-C initiates traversal connections outbound through the firewall to specific ports on Expressway-E with secure login credentials. 3. Once the connection has been established, Expressway-C sends keep-alive packets to Expressway-E to maintain the connection 4. When Expressway-E receives an incoming call, it issues an incoming call request to Expressway-C. 5. Expressway-C then routes the call to Unified CM to reach the called user or endpoint Internet Signaling Media 6. The call is established and media traverses the firewall securely over an existing traversal connection 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 23

24 Business-to-Business Communications

25 B2B Dial Plan Numbers and alphanumeric SIP URIs together on CUCM By default every line has a directory number By assigning one or more alphanumeric SIP URI to a line, a user s line can be reached by dialing: <directory number>@domain <alphanumeric SIP URI>@domain This is independent from the phone/videodevice model type Unified CM ExpC ExpE Unknown edge Internet

26 B2B Call Flow Single Edge SIP to SIP call DNS Hierarchy Expressway-C Forward SIP Invite to companyb.com using IP address received via DNS VCS-E Expressway-E Calls Sends SIP 200 OK Internet VCS-C COMPANY A COMPANY B x.y@companyb.com

27 B2B Call Flow SIP TLS, TCP, UDP or H.323? DNS Zone Expressway-E SIP (TLS,TCP, UDP) and H.323 are enabled globally Expressway always tries SIP TLS/TCP/UDP or H.323 based on the native protocol For SIP: Media encryption mode can be forced. Auto: depends on endpoints request only. Best Effort: will fallback to unencrypted if encryption is not available

28 Outbound Calls Multiple Edges Branch Office RCD HQ San Jose CUCM IM&P Expressway-E_RCD Company B Internet Expressway-E_SJC

29 Outbound Calls Calling Search Space SIP Route Pattern Route List RL_Internet_SJC Partition SJC_Internet SJC_B2B SJC_B2B *.* Route Groups XPY-C_SJC XPY-C_RCD Trunk_To_ XPY-C_SJC XPY-C_SJC Phone in SJC Partition Calling Search Space SIP Route Pattern Route List RL_Internet_RCD RCD_Internet RCD_B2B RCD_B2B *.* Route Groups XPY-C_RCD XPY-C_SJC Trunk_To_ XPY-C_RCD XPY-C_RCD Phone in RCD 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 29

30 Inbound Calls Multiple Edges Company A Site 2 Edge 1 or Edge 2? Company A Site 1 Edge 1 Looking for _sip._tcp.companya.com CUCM cluster Edge 2 Internet

31 Inbound Calls Multiple Edges If the edges are in the same region, resolving the SRV records into multiple edges with same priority and weight would allow load-balancing If one edge has to be used as a backup, SRV records can have higher priority for the active edge, and a lower priority for the stand-by edge If the edges are on different regions, two mechanisms could be put in place Routing based on the minimal distance between the edge and the calling device (maximizes quality) based on GeoDNS: preferred Routing based on the minimal distance between the edge and the called device (minimizes costs) GeoDNS not required: alternative (covered in the PA doc)

32 Inbound Calls Minimal distance between the calling device and nearest edge Company A US Site WAN CUCM cluster Company A EMEA Site Internet Company B US Site

33 Inbound Calls Minimal distance between the edge and the calling device Geo DNS is a service delivered by many Internet organization, such as Godaddy, Amazon Route 53 and others, which allow to forward the inbound call to the edge which is nearest to the calling device We ve chosen Amazon Route 53 as an example but this is not a recommendation Route 53 can route the call based on different metrics, such as: minimal latency: measured between the calling device and the edge geolocation: based on IP addresses

34 Geo DNS: latency routing and round-robin configuration settings for B2B calls and MRA SRV Record CNAME Record A-Records Expressway-E _sips._tcp.example.com _collab-edge._tls.example.com Latency routing expe.example.com location: us-east-1 us-expe.example.com weight: 50 A1.B1.C1.D1 A2.B2.C2.D2 us-expe.example.com weight: 50 A2.B2.C2.D2 A1.B1.C1.D1 Latency routing expe.example.com location: eu-west-1 emea-expe.example.com weight: 50 X1.Y1.W1.Z1 X2.Y2.W2.Z2 emea-expe.example.com weight: 50 X2.Y2.W2.Z2 X1.Y1.W1.Z1

35 IP Address Dialing for H.323 Internet devices: Inbound Calls Fallback alias for point-to-point and multipoint calls: Unity Connection call flow Expressway-C Expressway-E Cisco Unified CM 4. User enters luca, both devices ring at the same time A.B.C.D 2. Fallback alias set to voice mail pilot Cisco Unified Presence Server 3. Please dial the extension or the name 1. Dial A.B.C.D Unity Connection

36 IP Address Dialing: Outbound Calls Cisco Unified CM IP dialing Cisco Unified CM doesn t support native IP address dialing Workaround: instruct the users to append a suffix such as: @ip. This will match the SIP Route Pattern ip Other workarounds: instruct the user to use * instead of. such as 10*10*10*10. This will match one the following Route Pattern pointing to the Expressway:!*!*!*! On Expressway, regex match would be (\d\d?\d?)(\*)(\d\d?\d?)(\*)(\d\d?\d?)(\*)(\d\d?\d?) and replacement string \1\.\3\.\5\.\7

37 Mobile and Remote Access

38 Firewall Traversal Capabilities Expanded X8.1 release and above delivers 3 key capabilities enabling the Expressway Mobile and Remote Access feature XCP Router for XMPP traffic HTTPS Reverse proxy Proxy SIP registration to Unified CM Unity Cisco Unified CM HTTPs (provisioning, visual voic , directory) SIP (audio, video) XMPP (IM&P) IM and Presence Expressway C Firewall Expressway E

39 Split DNS SRV Record Requirements _collab-edge record needs to be available in Public DNS Multiple SRV records (and Expressway-E hosts) can be deployed for HA A GEO DNS service can be used to provide unique DNS responses by geographic region _collab-edge._tls.example.com. SRV expwy1.example.com. _collab-edge._tls.example.com. SRV expwy2.example.com. _cisco-uds record needs be available only in internal DNS _cisco-uds._tcp.example.com. SRV ucm1.example.com. _cisco-uds._tcp.example.com. SRV ucm2.example.com.

40 Expressway & Jabber Service Discovery Collaboration Services Inside firewall (Intranet) DMZ Outside firewall (Public Internet) Public DNS DNS SRV lookup _cisco-uds._tcp.example.com Not Found DNS SRV lookup _collab-edge._tls.example.com Unified CM Expressway C Expressway E expwynyc.example.com TLS Handshake, trusted certificate verification HTTPS: get_edge_config?service_name=_ciscouds&service_name=_cuplogin

41 Global Deployment Topology & Geo DNS expwy.us.example.com Expressway edge access DNS SRV lookup _collab-edge._tls.example.com Geo DNS US Europe Asia expwy.uk.example.com expwy.jp.example.com SIP Trunk SIP Line Expressway Traversal SME global aggregation US SME EU SME Asia SME Unified CM regional clusters SJC RTP PAR LON TKY BGL DFW AMS HKG

42 Features XMPP Federation to other companies SSO compliant via IdP and Reverse HTTPS Proxy in DMZ Multiple UCM and IM&P clusters and domains supported Desktop devices supported (78XX, 88XX, DX, TC series families)

43 Expressway Design Considerations

44 MRA and B2B in the same box Unified CM ExpC B2B Traversal zone Encryption configurable H.323 configurable ExpE Unknown edge MRA Traversal zone Always encrypted SIP, HTTPS, XMPP Internet Not possible to use port 5060 and 5061 for B2B trunk, use others instead (i.e.5560 and 5561) TLS or TCP on B2B Trunk, encrypted or non-encrypted media configurable Two zones for MRA, a TLS and a TCP zoneif mixed mode enabled on UCM.

45 PSTN Access

46 Gateways and CUBE Product Portfolio ASR 1004/6 RP2 ASR 1002-X ISR 4451-X ASR 1001-X ISR E Series ISR-G2 (3925E, 3945E) ISR 4431 CUBE ISR-4K (4321, 4331) 3900 Series ISR-G2 (3925, 3945) 2900 Series ISR-G2 (2901, 2911, 2921, 2951) 800/1861 ISR CUBE and Voice Gateways ISDN GW 3241 ISDN GW MSE 8321 Video Gateways 46

47 CUBE Deployment Scenarios Enterprise Network Carrier Network Demarcation Line Voice Carrier Network Cisco Unified CM Cisco Unified Border Element Interconnection Zone Session Border Controller Class 4/Class 5 switches IP Voice Network PSTN Enterprise Network Demarcation Line SIP Softswitch Class 5 switch

48 Centralized Voice Connection using CUBE and voice gateways CUBE for centralized IP PSTN Topology hiding when connecting to carrier SBC for IP PSTN access Delayed offer to early offer conversion and vice versa In-band and out-of-band DTMF support, DTMF conversion, fax passthrough and T.38 fax relay, volume and gain control Call admission control (CAC) based on resource consumption such as CPU, memory, call arrival spike detection RTP to srtp interworking and security features Mid-call supplementary services including hold, transfer and conference Conversion of multicast music on hold (MoH) to unicast MoH. Billing statistics and CDR collection

49 Centralized IP PSTN access with local GW as backup Calling Search Space Partition SJCInternational PSTNInternational Device Pool LRG_PSTN1 LRG_PSTN2 SJCPhone CUBE_US_PSTN GW_SJC_PSTN CUBE1 Device Pool set to SJCPhone RCDPhone CUBE_US_PSTN GW_RCD_PSTN Route Pattern \+! Route List RL_PSTN Phone in SJC PSTNInternational LRG_PSTN_1 Calling Search Space LRG_PSTN_2 Partition RCDInternational PSTNInternational Device Pool set to RCDPhone Route Group GW_SJC_PSTN GW_RCD_PSTN Trunk Trunk_To_SJC_GW Trunk_To_RCD_GW SJC_GW RCD_GW Phone in RCD First choice for SJC users Backup for SJC users First choice for RDC users Backup for RCD users

50 Core Applications

51 Headquarters Unity Connection Prime Collaboration Expressway-E Cisco WebEx DMZ Mobile/Teleworker Instant Message and Presence Applications Unified Communications Manager Expressway-C Integrated/Aggregated Services Router Internet Third-Party Solution Call Control Collab Edge MPLS WAN Integrated Services Router TelePresence Server Conductor TelePresence Management Suite PSTN / ISDN Remote Site Conferencing Endpoints

52 Core Applications Overview The Preferred Architecture (PA) for Enterprise Collaboration focuses on a subset of core applications that are common for most collaboration deployments. The core applications covered by the PA for Enterprise Collaboration:» Cisco Unity Connection» Cisco Prime Collaboration Deployment» Cisco Prime Licensing Manager Many other applications and tools are available for collaboration deployments. While these are not covered here, the overall PA architecture is designed in such a way that these additional applications may be added as required for your specific deployment. (See Appendix slides for a list of some of these applications)

53 Core Applications Key Benefits» Cisco Unity Connection enables voic and unified messaging across a wide-range of end-user platforms» Cisco Prime Collaboration Deployment (PCD) eases deployment of new infrastructure components, enabling faster initial setup» Cisco Prime Licensing Manager (PLM) single tool to enable license workflows and manage licensing for collaboration infrastructure components.

54 Cisco Unity Connection

55 Core Applications Cisco Unity Connection: Design Objectives and Prerequisites Design Objectives» Ensure highly available voice messaging services including leaving message, message waiting indication, and message retrieval» Provide access to voice messaging features from hardware and software-based endpoints.» Facilitate mailbox management and message retrieval via telephone, , or visually from a software client. Prerequisites:» Deploy Cisco Unified CM and ensure it is functioning appropriately (refer to Call Control section).» Download appropriate Cisco Unity Connection VMWare OVA template and bootable.iso.» Deploy Microsoft Active Directory and ensure directory services are properly configured.» Deploy Microsoft Exchange and ensure services are functioning normally.

56 Core Applications Cisco Unity Connection: Architecture Voic Unified CM SIP Unity Connection Publisher Subscriber Directory synchronization Directory Microsoft Active Directory Mailbox synchronization Microsoft Exchange Voic access via VoIP to TUI or via REST/HTTPS (Visual Voic ) access to voic (Single Inbox) Messaging (On-Premise or Cloud-Based) Redundant Unity Connection nodes SIP Trunk integration to Unified CM Integrations to directory and mail:» Microsoft Active Directory» Microsoft Exchange Call forwarding to Unity Connection Direct call to voic or visual mailbox navigation (Visual Voic ) access to voic (Single Inbox) SIP VoIP or REST/HTTPS (SMTP/HTTPS)

57 Alternatively use Prime Collaboration Deployment Core Applications Cisco Unity Connection: Deployment Overview (1 of 2) 1. Provision the Unity Connection Cluster Deploy two node cluster for high availability» Determine OVA configuration size (based on number of users) and network and security parameters for each node (hostname, IP address/mask, default gateway, DNS, NTP, username/password, etc.).» Deploy/install publisher, add subscriber details under cluster configuration, then deploy the subscriber. 2. Configure Unified CM for Unity Connection Integration Configure SIP trunks, call routing, and voic settings for integration to Unity Connection cluster.» Configure two SIP trunks (one per Unity Connection node) and call routing constructs (Route Pattern/List/ Group).» Configure voic constructs (Voic Pilot number, MWI on/off, Voic Profile). Refer to the CVD 3. Unity Connection Base Configuration Configure Unity Connection to enable Unified CM integration, user provisioning, and voic capabilities.» Configure phone systems settings, ports (port codec, port groups), and call routing to enable integration with Unified CM.» Enable directory sync with Active Directory and configure templates for user provisioning of mailboxes and self enrollment.

58 Core Applications Cisco Unity Connection: Deployment Overview (2 of 2) Refer to the CVD 4. Enable Single Inbox Unified messaging feature enabling synchronization of voice messages in Unity Connection with user s Microsoft Exchange mailbox.» Configure Unified Messaging Services account and role in Active Directory/Exchange, and configure Unity Connection settings (SMTP, authentication method/protocol, and user enablement).» Install ViewMail for Outlook (available at Cisco.com), configure account and Unity Connection server. 5. Enable Visual Voic Provide visual access to voic boxes for listing and playing messages» Configure appropriate Unity Connection settings: Class of service (CoS) and API options settings» On Unified CM configure voic UC service for each Unity Connection node and add the services to a UC Service Profile. 6. Voic in SRST Mode Configure branch ISRs with SRST to route calls to Unity Connection voic system via PSTN when IP WAN is down.» Configure call forward no answer/busy and POTS dial-peer to route calls via the PSTN to Unity Connection.» Ensure Redirected Dialed Number Information Service (RDNIS) is configured and carrier propagates so that callers are directed to the appropriate voic box rather than the automated attendant prompt. 7. HTTPS Interworking of two or more Unity Connection Clusters Configure HTTPS networking to enable directory information sharing and message exchange between multiple clusters.

59 Core Applications Cisco Unity Connection: Design Considerations Unity Connection Cluster Deployment (publisher + subscriber) Sub X Pub» Nodes: Must be the same OVA size and integrate to the same Unified CM cluster.» Connectivity: Maximum RTT = 150 ms. For every 50 voice messaging ports 7 Mbps of bandwidth is required. Unified CM Integration» Dual SIP trunks, route group with Top Down algorithm for call routing: Unity Connection subscriber 1st (primary), publisher 2nd (backup).» Visual Voic UC Service: Set the Unity Connection publisher as the primary voic service and subscriber as the secondary service within the UC service profile. Capacity Planning» Reserve 20% of total system ports for dial out/non-answering operations (message notification, MWI, etc.)

60 Cisco Prime Collaboration Deployment

61 Core Applications Cisco Prime Collaboration Deployment: Design Objectives and Prerequisites Design Objectives» Simplify collaboration application node deployments by enabling automated unattended installation of collaboration application server nodes» Facilitate configuration of common network and security settings for all collaboration applications. Prerequisites:» Download OVA and bootable.iso file for Cisco Prime Collaboration Deployment (PCD)» Deploy PCD virtual machine as a standalone application instance on VMWare ESXi host.» Determine which collaboration applications will be deployed (Unified CM, IM & Presence, Unity Connection) and the number of nodes required based on overall size of the deployment.

62 Core Applications Cisco Prime Collaboration Deployment: Architecture VMWare EXSi host CM_Pub VM CM_Sub VM CM_Sub VM IM&P_Pub VM IM&P_Sub VM IM&P_Sub VM UCXN_Pub VM UCXN_Sub VM Cisco collaboration application.iso install files located on Prime Collaboration Deployment (PCD). PCD network file system (NFS) mount on ESXi host(s) to facilitate.iso file access. Prime Collaboration Deployment.iso.iso.iso Collaboration application node virtual machines (VMs) manually created on the ESXi host. PCD installs collaboration application clusters on the target VMs.

63 Core Applications Cisco Prime Collaboration Deployment: Deployment Overview 1. Prepare for Collaboration Application Deployment Download the OVA templates and bootable Cisco ISO images for the target collaboration application(s) and release. SFTP.iso images to the /fresh_install directory of Cisco Prime Collaboration Deployment (PCD). 2. Create Virtual Machines (VMs) on the ESXi Host(s) using OVA Templates Create one VM for each application node using appropriate application OVA template based on deployment size. 3. Add ESXi Host (s) to PCD Enter ESXi host(s) information via the administrative interface of PCD. 4. Define New UC Cluster (s) in PCD Add VM nodes and configure network parameters and functions as well as cluster-wide network and security settings (DNS, NTP, usernames/passwords, certificate information). [Two clusters required: 1 for Unified CM/IM & P, 1 for Unity Connection] 5. Add Install Task (s) in PCD Select UC cluster for installation and select installation files (.iso) for cluster node types. [Two installation tasks required: 1 for Unified CM/IM & P, 1 for Unity Connection] 6. PCD Completes Installation Process All collaboration application server nodes are installed with base configuration and now ready for further configuration.

64 Cisco Prime License Manager

65 Core Applications Cisco Prime License Manager: Design Objectives and Prerequisites Design Objectives» Enable simplified, enterprise-wide management and tracking of user-based licensing for collaboration applications.» Provide enterprise-level reporting of usage and entitlement» Facilitate license fulfillment using electronic or license file methods.» Simplify procurement of additional licenses when number of users increases. Prerequisites:» Download Cisco Prime License Manager OVA template and bootable.iso file.» Determine number and types of users to be licensed for collaboration applications (Unified CM and Unity Connection)

66 Core Applications Cisco Prime License Manager: Architecture Unified CM Unity Connection Cisco Prime License Manager (PLM) enables license fulfillment: Publisher Publisher» Electronic [requires Internet connectivity] OR» Manual license file request Licenses received (over the network or via ) Cisco.com Prime License Manager Licenses applied to system and propagated to synchronized application instances.

67 Core Applications Cisco Prime License Manager: Deployment Overview 1. Deploy and Install Cisco Prime Licensing Manager (PLM) Install PLM as a virtual machine on a VMWare ESXi host. 2. Add Product Instances Add Unified CM and Unity Connection product instances to PLM (one per cluster). Use Test Connection to verify communication between the collaboration applications and PLM. 3. Determine Licensing Requirement for Products Based on number of users within deployment determine number and types of licenses required.» Use the License Usage and License Planning menu options to determine number and type of required licenses based on current user count as well as to calculate and prepare for future license requests. 4. Perform New License Fulfillment Acquire and install collaboration user licenses.» Enter PAK (product activation key) and retrieve licenses electronically via the Internet» Alternatively, generate license request and submit along with PAK via Cisco License Registration site ( to receive license file via . Install received license file.

68 Simplified Sizing

69 Traditional Sizing for Cisco Collaboration Collaboration Sizing Tool (CST)

70 Simplified Sizing for the Preferred Architecture (PA) The Preferred Architecture (PA) offers Simplified Sizing rules with corresponding assumptions (e.g. average BHCA per user, number of DN per device, etc )

71 PA Simplified Sizing vs. Collaboration Sizing Tool Deployment within the PA Sizing Assumptions? Use PA Simplified Sizing Use Collaboration Sizing Tool

72 Sizing Cisco Unified CM < 5k devices and users Between 5k and 10k devices and users Publisher TFTP 1 TFTP 2 Publisher TFTP 1 TFTP 2 Call Processing subscriber pair Call Processing subscriber pair Call Processing subscriber pair 7.5k OVA (2 vcpus) is deployed for both deployments 7.5k OVA supported on BE7000M or larger

73 Why using the 7.5k OVA for Cisco Unified CM? Let s consider the deployment with 10,000 users/devices With the 7.5k OVA With the 10k OVA

74 Sizing Unified CM PA Assumptions PA Assumptions: Up to 4 BHCA per user Up to 2 DNs per device Each user can use Extension Mobility No SW Conference Bridge Up to 500 CTI ports and 100 CTI Route Points per Call Processing pair Up to 3,000 partitions, 6,000 CSS, 12,000 Translation Patterns etc Refer to the Preferred Architecture CVD for the complete list of assumptions

75 Sizing IM and Presence In the PA, IM & Presence is deployed with 2 servers The number of users (full UC) dictate which OVA is used Less than 2k users Between 2k and 5k users Between 5k and 15k users 2k-user OVA (1 vcpu) 5k-user OVA (2 vcpus) 15k-user OVA (4 vcpus) Those 3 OVAs are supported on BE7000M or larger

76 Sizing TelePresence Server Add TelePresence Servers as needed Platform Multiparty Media 410v Multiparty Media 820 (blade) Cluster Support HD 1080p port capacity 1 HD 720p port capacity 2 SD 480p port capacity 2 No Yes Includes content sharing 720p@15fps 2 Includes content sharing 720p@5fps TelePresence Servers support a maximum of 200 audio connections on any platform Data sheet:

77 Sizing TelePresence Conductor In the PA, 2 TelePresence Conductor servers are deployed The number of concurrent participants dictates which OVA to use < 50 total concurrent participants < 2,400 total concurrent participants Small OVA (2 vcpus, 4GB RAM) Large OVA (2 vcpus, 6GB RAM) or Dedicated Appliance Both OVAs are supported on BE6000M or larger A TelePresence Conductor cluster supports up to 30 TS servers

78 Sizing TelePresence Management Suite (TMS) < 200 controlled systems < 100 concurrent participants < 50 concurrent ongoing scheduled conference <1000 Collaboration Meeting Rooms < 5,000 controlled systems < 1,800 concurrent participants < 250 concurrent ongoing scheduled conference < 48,000 Collaboration Meeting Rooms TMS/TMSPE TMS/TMSPE TMS/ TMSPE/TMSXE TMS/ TMSPE/TMSXE TMSXE TMSXE Regular Deployment (1 vcpu OVA) All OVAs are supported on BE6000M or larger Large Deployment (4 vcpus OVAs)

79 Sizing Expressway - Deployment Expressway-C Expressway-E Internet Equal number of nodes in Expressway-C vs. Expressway-E clusters Up to 6 nodes per Expressway C/E cluster

80 Sizing Expressway Expressway Deployment with CE500 / Medium OVA (2 vcpus) on BE6000M or larger Expressway C/E Cluster Redundancy Model MRA Proxy Registrations Video Audio-only 2 nodes N+1 2, nodes N+1 5, nodes N+2 10, ,200 Expressway Deployment with CE1000 / Large OVA (8 vcpus) on Specs-based Expressway C/E Cluster Redundancy Model MRA Proxy Registrations Video Audio-only 2 nodes N+1 2, ,000 3 nodes N+1 5,000 1,000 2,000 6 nodes N+2 10,000 2,000 4,000

81 Sizing Unity Connection Cisco Unity Connection is deployed with 2 servers in an active/active mode The number of users dictate which OVA is used Between 1k and 5k users Between 5k and 10k users 5k-user OVA (2 vcpus) 10k-user OVA (4 vcpus) Both OVAs are supported on BE7000M or larger

82 Collaboration Virtual Machine Placement Tool VM placement and Hardware Sizing Virtual Machine Placement Tool (VMPT):

83 Deployment example with 5k users / 5k devices BE7KM BE7KM BE7KM MM410v BE7KM

84 Summary Preferred Architecture Introduction Collaboration Edge Applications Simplified Sizing

85 Closing

86 Additional Information Cisco Collaboration Solutions Design Guidance: Cisco Collaboration Systems 10.x Solution Reference Network Designs (SRND)» COMING SOON: Cisco Collaboration Systems 11.0 Solution Reference Network Designs (SRND) Cisco Enterprise Preferred Architecture: Cisco Preferred Architecture for Enterprise Collaboration, Design Overview» Cisco Preferred Architecture for Enterprise Collaboration, CVD To continuously improve the Preferred Architecture Documentation we need your feedback. For questions, suggestions and clarifications please send to

87 Cisco Customer Connection Program Connect with Cisco & Peers 17,000+ Members Influence Collaboration product direction Access to early adopter & beta trials Contribute to advisory groups Monthly technical & roadmap briefings Exclusive perks at Cisco Live Collaboration Cloud Fusion: Vision & Architecture (speaker: Jonathan Rosenberg, VP/CTO CTG) 5 NDA Roadmap Sessions + Microsoft Interop Q&A Open Forum with Product Management Reserved seats at Work Human Innovation Talk (Wed. 3:30 4:30) Visit the Customer Connection Program - Collaboration zone in the Cisco Campus Join the Customer Connection program Explore the Collaboration community New CCP members get a thank-you gift

88 Continue the Conversation using Cisco Spark Sign up free for Cisco Spark at Download the application from ios App Store, Google Play Store, or from Visit the World of Solutions Cisco Spark area for demos Use Cisco Spark to continue the conversation or ask any additional questions with the speaker for this session. The room name is BRKCOL-2421 How to get added to the Cisco Spark room for this session To opt in, send an to with the message Please add me to the BRKCOL-2421 room

89 Complete Your Online Session Evaluation Give us your feedback to be entered into a Daily Survey Drawing. A daily winner will receive a $750 Amazon gift card. Complete your session surveys though the Cisco Live mobile app or your computer on Cisco Live Connect. Don t forget: Cisco Live sessions will be available for viewing on-demand after the event at CiscoLive.com/Online

90 Continue Your Education Demos in the Cisco campus Walk-in Self-Paced Labs Table Topics Meet the Engineer 1:1 meetings Related sessions

91 Thank you

92

93 Appendix

94 Core Applications Additional Applications to Enhance Preferred Architecture* (1 of 2) Application Name Functions Integration Method Contact Center Enterprise (CCE) Contact Center Express (CCX) TelePresence Content Server (TCS) Show and Share Prime Collaboration Provisioning Prime Collaboration Assurance Provides internal and external customer collaboration technologies, including agent login, Interactive Voice Response (IVR) for call vectoring, outbound connection methods, and omnichannel agent interactions. Provides dial-by-name and a subset of Contact Center ideal for small contact centers or internal use. Provides video, audio, and content recording functionality that can be included in scheduled calls through a check-box in TMS or dialed, allowing any endpoint to easily be a recording station. Provides an internal stored video content portal. Provides an administrative portal for "Day 2" operations. Provides quality and fault detection services for collaboration deployment administrator. Enterprise contact centers operate on a dedicated Unified CM cluster that is trunked to the enterprise Unified CM cluster. Communicates to Unified CM using JTAPI. Registers with Cisco TelePresence VCS-Control and communicates with Unified CM devices via SIP trunk between Unified CM and VCS Control. TCS automatically uploads content to Show and Share. No other integration to call control is required. Standalone software that communicates through SSH and HTTPS interfaces of infrastructure devices and endpoints. Stand alone software that communicates through SSH and HTTPS interfaces of infrastructure devices and endpoints. * This is not an exhaustive list of applications that can be integrated with the Enterprise Preferred Architecture

95 Core Applications Additional Applications to Enhance Preferred Architecture* (2 of 2) Application Name Functions Integration Method Prime Collaboration Analytics Attendant Console Media Sense Jabber Guest Provides up to one year of usage data for usage and fault trend analysis by the collaboration deployment administrator. Gives corporate operators or receptionists a desktop application to handle incoming calls. Provides recording for both full-time and selective recording scenarios in Unified CM. Provides click-to-connect functionality for business-to-consumer (B2C) collaboration. Deployed with Prime Collaboration Assurance and utilizes data collected by that application. Standard version installs on the end user s Windows computer and connects to Unified CM. Advanced version runs on a dedicated server, and the end users log into the application.. Recording Profiles are configured in Unified CM, and MediaSense is connected to Unified CM and Cisco Unified Border Element through SIP trunks. Requires a dedicated Expressway-C and Expressway-E pair, using a distinct domain from the enterprise Expressway-C and Expressway-E implementation used for Mobile and Remote Access and business-to-business video calls. Unified CM has SIP trunks to this dedicated Expressway pair. * This is not an exhaustive list of applications that can be integrated with the Enterprise Preferred Architecture