HCS Shared Architecture - A simple, scalable and standardized deployment model

BRKCOL-2295 HCS Shared Architecture - A simple, scalable and standardized deployment model Kai Xu Product Manager, UCaaS Partner Enablement kxu@cisco.com

Cisco Spark How Questions? Use Cisco Spark to communicate with the speaker after the session 1. Find this session in the Cisco Live Mobile App 2. Click Join the Discussion 3. Install Spark or go directly to the space 4. Enter messages/questions in the space cs.co/ciscolivebot#brkcol-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public

Agenda Key Challenges What is HCS Shared Architecture (HCS-SA)? HCS-SA Architecture Cisco Mobile and Remote Access (MRA) HCS-SA Access Options (Meraki VPN/SD-WAN) HCS-SA Deployment Options and Customer Onboarding HCS-SA Sizing Guidelines Q & A

Cloud Collaboration Momentum with HCS 67 Countries 139 Partners 5,500+ Customers >5.6M End-Users 75% Market share (>500 users) #1 In Cloud UC* and Contact Center FY17 Q4 = largest ever number of user activations (367K) & contracted users (941K) *enterprise BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 5

Key Challenges

Key Challenges Compute, Storage & Footprint Costs Operational Costs Access Costs Under utilized dedicated VMs are expensive for small and even for mid-market customers Starting cost of HCS DC is also high Initial customer on-boarding cost is significant Customer site deployment is also complicated MACD service and maintenance of customer clusters are expensive MPLS between HCS DC and customer sites is expensive and also has long lead time Typical VPN solution requires additional CPE at customer site, and it is hard to manage and maintain BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 8

Why HCS Shared Architecture (HCS-SA)? HCS HCS-SA Cost Ratio DC HW 60xC240 M4 100 VRF 3xC240 M4 1 VRF 20 to 1 Customer Onboarding Minimum 2 weeks for each customer About 1 day for each customer 10 to 1 Site Deployment MPLS + device setup OTT + self service N to 1 Release mgmt (Upgrades, ) Each App must be done separately All customers get upgraded at the same time N to 1 BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 9

What is HCS Shared Architecture?

What is HCS Shared Architecture (HCS-SA)? HCS-SA is Deployment Model offering lower TCO o Optimized DC Resource Usage (multiple customers sharing same UC cluster) o Minimum Operation Cost (streamlined customer onboarding process and automation) o Low Cost for Site Deployments - OTT Access via MRA (device self-registration) HCS-SA is a Standardized Offer powered by Automation o Service Creation One Size Fits All (standardized offer w/ options) o Target Markets Commercial and Enterprise (>= 10 users in average) o Service Automation Powered by ASAP/Kurmi/VOSS4UC o Centralized Directory Service and Tenant Separation Enabled by Imagicle BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 11

HCS-SA Service Offer Overview IP PBX Offer UC and Mobility Offer Additional Offer Basic Call Services for Audio/Video Call Back, Call Park, Call Pickup Call Transfer, Call Forward, etc. Barge, Speed Dial Multi-party Conference Hunt Group* Music on Hold Multiple Lines and Shared Lines Multi-party Audio Conf (Ad-Hoc) Soft Phone (Jabber) VoiceMail Attendant Console* IVR services* Call Recording* FAX services* Directory Service* Desktop Share Directory Integration File Transfer Group Chat Escalation Instant Messaging Jabber on Smartphones (Android & Apple) SNR Standard and Custom Presence Status Privacy Policy Video Call WebEx and CMR* Spark Business Messaging and Meeting CMS (Shared) HCS-SCC (Shared) LDAP in Cloud (Shared) Integration with Cloud Service, eg. Google Drive, Calendar, etc. By Imagicle AppSuite (S++ Partner) BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 12

HCS Roadmap Q1CY2018 Q2CY2018 Q3CY2018 2HCY2018 Backlog HCS 11.5 Add-on 5 CUCDM 11.5.3 Quality / Maintenance Release HCS 11.5 Add-on 6 HCS-SA Offline Modeling Tool ICE Media Optimization for MRA Hunt Group for MRA PCA support for TLS (12.x validated with 11.5) Quality / Maintenance Release HCS 12.5 CSR 12.5 with CUCDM12.5 /PCA12.x / CUCM12.5 HCS-CC12.0 Smart Licensing & License Dashboard Enhanced License Summary in HCMF GUI License Dashboard Enhancements in HCMF to include User-level data HCS Management IPv6 Aware CLIR for Call Forwarding VoLTE Support with CIM FedRAMP CER Session Timeout Expressway Optimization Jabber Deskphone Control over MRA CUCM API Security Enh (HCS-G) Operation Orchestration Expressway Bootstrap Certificates for HCS Partners / Customers Licensing as a Service Upgrade as a Service Proxy Connector on ECP Secure Onboarding Simplification Backlog Jabber HA Support for MRA Expressway Multiple VLAN/VRF Support Migration as a Service Test as a Service HCS-SA On-line Sizing Tool CER Local Auth without LDAP Sync ATA / Conference phone support for MRA Analytics as a Service Management as a Service Enhanced License Reporting for HCS-SA at customer level Service Inventory Optimization BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 13

HCS Collaboration for Companies of Every Size HCS Model Options Basic IPT to Full Collaboration Common Architecture Collaboration Software Licensing Framework Management tools Seamless Migration Unified Communications Endpoints Conferencing Customer Care Collaboration Edge B2B, B2C, Mobile & Remote Access, Hybrid, Cloud-Connected Collaboration Cisco Collaboration Cloud HCS-SA HCS 0-50 50-250 250+ 40000+ Customer Size BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 14

HCS-SA Architecture

HCS-SA w/ Single Partner-Owned Domain - A True Cloud Collaboration Turnkey Solution Shared CUCM Cluster + Partitioned Unity Connection Customer A Customer B Customer C Partner-Managed Domain: partner-sa.com VPN/MPLS (Optional) HCS C E Expressway Internet (Standard) Partner Cloud Collaboration Service for customers with average of 10 users or more Full suites of collaboration offers from dial tone, video, mobility to team collaboration. IT/Collaboration TURNKEY Solution: Using partner owned service domain e.g. partner-sa.com to provide collaboration for all customers Managing end users/password for each customer via Partner managed LDAP/AD Providing Internet access (OTT/MRA) access by default Service Provider to manage day to day operation and upgrade (as needed) as any cloud services Basic Voice Voice/Video Mobility Team Collaboration

Management Components HCS-SA Architecture Domain Manager HCM-F Assurance (optional) Web Proxy Mobile and Remote Access Cust A UCXN IM & P LDAP Imagicle CUCM Expressway-C Expressway-E DMZ WAN Cust B PSTN SIP Trunk(s) Single Partner Managed Domain (LDAP/AD) Shared LDAP/AD with OU for tenant Shared CUCM, IM&P, Partitioned Unity All Endpoints access via OTT/MRA by default Imagicle for Directory Service BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 17

Contact Segregation in HCS-SA using Imagicle Directory Service CISCO HCS UCM AXL/SOAP Imagicle AppSuite Server Speedy Enterprise CURRI Optional CRM/ERP/LDAP* XML based IP Phone Customer 2 IP Phone searches for local contacts XML Return Customer 2 contacts only Jabber requests a local contact * Imagicle Speedy can synchronize users directly from Cisco UCM or, optionally, from external sources (CRM/ERP/LDAP) XML based IP Phone Cisco Jabber Desktop/Mobile In network or MRA UDS Return Customer 1 contacts only Customer 1 BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 18

HCS-SA Service Automation Simple, Scalable, Standardized HCS for Commercial Markets Service Automation Tool from Italtel/Kurmi/Voss Multi-tenant LDAP server from Imagicle Partner/Customer facing Web portal for online service procurement Email end-users to selfregister phone/jabber VPN Access BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 19

Cisco Mobile and Remote Access

Mobile and Remote Access with Cisco Expressway Internal Network DMZ External Network Jabber @ the café Collab Services UCM 9.x/10.x/11.x Expressway-C Expressway-E Internet Jabber @ Home Jabber @ work Jabber @ SFO, DEN or ORD Fixed Remote Endpoints BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 21

UDS Directory Search All Jabber clients connecting via Expressway will use UDS for directory search (assuming Unified CM IM&P deployment) TelePresence endpoints, DX series, IP Phones also use UDS directory search For the best contact search experience, all Enterprise Users should be imported into every Unified CM cluster s end user table Home cluster check box needs to be selected on only one cluster for each user BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 22

Cisco Expressway Mobile and Remote Access Expressway Firewall Traversal Basics Enterprise Network DMZ Outside Network Unified CM Expressway C Firewall Expressway E Firewall Internet Signaling Media 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 (or other collaboration services/applications) to reach the called user or endpoint 6. The call is established and media traverses the firewall securely over an existing traversal connection BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 23

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 BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 24

High Level MRA Deployment Guidance Start on solid ground Jabber service discovery needs to work directly w MPLS/VPN Start direction connection and then add MRA access Verify end user home cluster discovery in multi Unified CM cluster deployments Don t forget about DNS Understand split DNS SRV requirements, get DNS change requests in the queue A common DNS domain simplifies matters, but is not required Review TCP and UDP port requirements with firewall team, and minimize UDP ports open to Expressway-E from internet if required Verify Expressway CA signed certs Confirm SANs returned in CA signed cert match what was requested in the CSR Verify cert includes both TLS Web Server & Client Authentication Extended Key Usage BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 25

MRA Port Reference Outbound from Expressway-C (private) to Expressway-E (DMZ) Purpose Protocol Expressway-C (source) Expressway-E (listening) XMPP (IM and Presence) TCP Ephemeral port 7400 SSH (HTTP/S tunnels) TCP Ephemeral port 2222 Traversal zone SIP signaling TLS 25000 to 29999 7001 Traversal zone SIP media UDP 36000 to 59999* 2776 (RTP), 2777 (RTCP) if Use configured (for small/medium systems on X8.1 or demultiplexing ports = later) Yes or 36000 (RTP), 36001 (RTCP) if Use configured demultiplexing ports = No Traversal zone SIP media UDP 36000 to 59999* 36000 to 36011 (6 pairs of RTP and RTCP ports for (for large systems) multiplexed media traversal) BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 26

MRA Port Reference Outbound from Expressway-E (DMZ) to public internet Purpose Protocol Expressway-E (source) Internet endpoint SIP media UDP 36002 to 59999 or >= 1024 (listening) 36012 to 59999 SIP signaling TLS 25000 to 29999 >= 1024 Inbound from public internet to Expressway-E (DMZ) Purpose Protocol Internet endpoint (source) Expressway-E (listening) XMPP (IM and Presence) TCP >= 1024 5222 HTTP proxy (UDS) TCP >= 1024 8443 Media UDP >= 1024 36002 to 59999 or 36012 to 59999* SIP signaling TLS >= 1024 5061 HTTPS (only required for external TCP >= 1024 443 administrative access, which is strongly discouraged) BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 27

MRA Port Reference From Expressway-C to Internal Infrastructure and Endpoints Purpose Protocol Expressway-C (source) Internal Device Port/Range XMPP (IM and Presence) TCP Ephemeral port 7400 (IM and Presence) HTTP proxy (UDS) TCP Ephemeral port 8443 (Unified CM) HTTP proxy (SOAP) TCP Ephemeral port 8443 (IM and Presence Service) HTTP/HTTPS (configuration file TCP Ephemeral port (Unified CM) HTTP 6970 retrieval) Or HTTPS 6972 if you have Cisco Jabber 11.x or later with Unified CM 11.x or CUC (voicemail) TCP Ephemeral port 443 (Unity Connection) Message Waiting Indicator (MWI) from TCP Ephemeral port 7080 (Unity Connection) Unity Connection Media UDP 36000 to 59999* >= 1024 (Media recipient later eg. endpoint) SIP signaling TCP 25000 to 29999 5060 (Unified CM) Secure SIP signaling TLS 25000 to 29999 5061 (Unified CM) BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 28

HCS-SA Access Options

HCS-SA Access Options Management Components SA Customers Domain Manager HCM-F Assurance (optional) DMZ Web Proxy SA Customers UCXN IM & P LDAP Imagicle CUCM Expressway-C Expressway-E MPLS Core PSTN SIP Trunk(s) IPSEC DMVPN Tunnels LBO CUST E CUST F PSTN Meraki VPN CUST Z BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 30

HCS-SA Delivered by Meraki Managed Network(VPN) Meraki Cloud VPN Concentrator Internet SP/Partner DC Partner/ISP Customer 1 Customer 2 BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 31

HCS-SA Delivered by Meraki Managed Network(VPN) SP Managed Meraki Device on the premise. SP has API based control of the Meraki Device thru Meraki Cloud. Customer places order for the HCS-SA Service thru SP portal or thru Meraki Portal or thru SP sales team. SP gets notified of the order and using API s provisions the Meraki Device with necessary config ( DHCP/TFTP, VLAN etc) for specific phone ports on the Meraki Device). The IP address will be configured for readonly and will not be editable by the Customers. SP automates the creation of the HCS-SA VPN tunnel from the Customer Premise to the VPN Concentrator in HCS DC. SP provisions the HCS SA for the Customer in the HCS DC. Customer plugs in phone and registers to the HCS-SA cluster thru the Dedicated HCS VPN Tunnel and starts making and receiving calls. BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 32

HCS-SA + Meraki VPN One Platform with Multiple Services o Managed Network including Mobility o Managed Security o Managed UCaaS E Better SLA o Partner ISP + Meraki VPN = SD-WAN (Managed Network from end to end for UCaaS) o Better Voice/Video Quality and Reliability (in network service) More Features/Functions w/ Less Cost o Support all devices (not just ones supported OTT/MRA) o Support more features/functions o Less Cost compared with MPLS o Operation efficiency with Automation (HCS-SA and Meraki-VPN) BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 34

HCS-SA Deployment Options

HCS-SA Deployment Option SMB and Mid-Market HCS Partner Data Center Shared CUCM Cluster + Partitioned Unity Connection DMZ Partner-Managed Domain/AD: ciscolabs.com Customer A Customer B Customer C All Endpoints access via OTT or VPN Single Partner Managed Domain (AD) Different OU s for customer separation Shared CUCM, Partitioned Unity Internet OTT OTT VPN Customer A Customer B Customer C BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 37

HCS-SA Deployment Option Branch Office/Teleworker/Mobile User for Large Enterprise HCS Partner Data Center HCS Partner Data Center Headquarter CUCM Cluster(s) + Unity Connection PSTN Shared CUCM Cluster + Partitioned Unity Connection LDAP MPLS OR 3 rd party Call Control Imagicle SRST PSTN local breakout PSTN DMZ DMZ VPN/MPLS Internet Regional Office Teleworker Mobile Worker Satellites Sales Office Remote Support Office BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 38

HCS-SA Deployment Option Global Branch Offices HCS Partner Data Center (North America) HCS Partner Data Center (Europe) Satellites NA Sales Office LDAP Imagicle PSTN LDAP Imagicle Satellites Sales Office HCS Partner Data Center (APAC) Remote Support Office LDAP Imagicle Satellites Sales Office Remote Support Office BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 39

HCS-SA Deployment & Customer Onboarding

High level configuration steps System Cluster Infrastructure Setup e.g. VRF LDAP Install & Configuration UC Cluster Install & Initial Setup Expressway Install and configuration Setup once per deployment Setup once per cluster deployment Customer CUCDM Customer Configuration LDAP Integration and Onboarding BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 41

System level configuration Infrastructure Setup e.g. VRF System LDAP Install and Configuration Setup once per deployment Networking(VRF) Create ONE Shared Customer Space VRF for all HCS Shared Architecture customers Configure the Network components accordingly - ASA, Nexus switches, etc. LDAP Install and Configuration Install LDAP in Shared Customer Space Configure LDAP to manage Partner-owned Service Domain: ciscolabs.com Setup DNS w Co-located LDAP CUCDM Configuration Setup an HCS SA Service Provider (entitlement, etc.) Detailed configurations steps are athttp://www.cisco.com/c/en/us/td/docs/voice_ip_comm/hcs/11_5/hcs_solution/install_guide/chcs_b_11-5_installation.html BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 42

Cluster level configuration steps UC Cluster Install & Initial Setup Cluster Setup self-provisioning configuration needed in CUCM Install Expressway UC Cluster Install & Initial Setup Expressway Install and configuration Setup once per cluster deployment Install Expressway C and E Expressway E Configure Traversal Server Configure the domain in TLS verify Subject name Expressway C Configure Traversal Client Add SIP domains(ciscolabs.com) and enable it for MRA CUCDM Configuration Add UC Cluster under HCS SA Service Provider Setup Shared Trunk, if needed Detailed installation steps are in the installation guide athttp://www.cisco.com/c/en/us/td/docs/voice_ip_comm/hcs/11_5/hcs_solution/install_guide/chcs_b_11-5_installation.html BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 43

Customer level configuration steps Provision Customer elements CUCDM Customer Configuration Customer LDAP Integration and Onboarding CUCDM Configuration Configure customer Configure Network Device List for customer Configure Dial plan for customer/site Add DN/E164 inventory & associations (trunk) ASA Setup Integrate LDAP (Customer OU) for customer Move the users to site(s) and pushed to CUCM Pre-Provision phones/soft clients for customers. Configuration details of CUCDM is listed here- http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/hcs/11_5/hcs_solution/dial_plan/chcs_bk_h209ea04_00_hcs-1151- dpm-cucdm-115x.html BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 44

Customer/Users Info Collection Customer/User Management in LDAP LDAP is hosted in Partner DC Configure LDAP with a different Organization Unit for each customer Configure LDAP Organization Units (OU) for customers Each OU represents a customer in Shared Architecture UserId format: user1@c1.com@ciscolabs.com Actual user email: user1@c1.com Minimum User Info: Name Email UserId (managed by Partner) DN/Telephone Number ASA Setup BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 45

HCS-SA End-User Device Onboarding

Phone Registration Process over Expressway Process 1. One time self-provisioning configuration needed in CUCM and CUCDM for line/device templates and dial plans Configure selfprovisioning and Expressway 2. Configure Expressway (one-time) 3. Add end users with associated line into CUCDM and then sync to CUCM 4. End user gets a phone and plugs it into network 5. End user enters server domain for Expressway-E and user ID and password provided by partner 6. Phone auto-registers 7. End user calls IVR number provided by partner and enters extension and PIN 8. Phone reboots and registers with end user s extension Enter server and credentials on phone Phone auto registers User runs self provisioning IVR Phone registers with actual user extension * Partner Steps * End User Steps BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 47

Jabber Registration Process over Expressway Process 1. One time configuration needed in CUCM/CUCIM&P and CUCDM to setup IM&P 2. Add end users with associated Jabber accounts into CUCDM and then make sure they are sync to CUCM/CUCIM&P 3. Configure Expressway C and E 4. End user installs Jabber on their desired machine (Apple, Android, Mac, Windows, etc.) 5. End user enters user ID with Expressway as domain for OTT (ex. user1@c1.com@ciscolabs.com) Configure CUCM/CUCMI M&P, CUCDM and Expressway Enter user ID on Jabber Enter password on Jabber 6. End user enters password and clicks Sign In 7. Jabber registers! * Partner Steps * End User Steps Jabber registers HCS SA Whitepaperhttps://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/hcs/11_5/White_Papers/SAWhitepaper-17042017-002-2_V4.pdf BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 48

HCS-SA Sizing Guidelines

HCS Shared Architecture: Optimized for Lower Average Customer Size Shared Architecture per Cluster Capacity Users per Customer 20 50 100 250 Number of Customers per CUCM Cluster 1,000 OVA (C-Series) 2500 OVA (B-Series) 50 20 10 4 125 50 25 10 Maximum number of customers per CUCM cluster: 590 Cluster can be of any size (Ex: 10K user cluster will support 340 customers w/ average size of 30 user/customer) BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 50

Expressway Compute Platforms and Scalability Deployment vcpu Reserved RAM Disk Space NIC(s) Small 2 x 1.8 GHz 4GB 132GB 1Gb Medium 2 x 2.4 GHz 6GB 132GB 1Gb Virtual Machine(s) Large 8 x 3.3 GHz 8GB 132GB 10Gb Server Cluster Platform Proxied Registrations Video Calls Audio Only Calls Proxied Registrations Video Calls Audio Only Calls Large OVA 2,500 500 1,000 10,000 2,000 4,000 Medium OVA 2,500 100 200 10,000 400 800 Small OVA (BE6K) 2,500 100 200 N/A N/A N/A Notes: HCS UC applications cannot be mixed with non-uc applications. Expressway No over subscription for any compute resources BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 51

Component HW/SW Versions Component CUCM Expressway-E/C CUCDM 10 HCM-F Software 10.5(2) SU3 or later X8.7.1 or later 10.6.3 SU1 or later 10.6.3 or later End-Points 7800 Series IP phones 8800 Series IP phones DX Series endpoints Jabber BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 52

Expressway and CUCM Sizing Average customer size shall determine the UC OVA size for Shared Architecture Cluster (limit of 590 customer/cluster) 20 user/customer -> 20 * 200 = 4000 total users We recommend to reserve 25% capacity for possible customer growth 4000 * 1.25 = 5000 -> 7.5k OVA shall be used for cluster We recommend to use medium OVA for Expressway Cluster, which supports 10k devices registration and 800 active sessions (call) Assume average of 2 devices per user 2 devices/user -> 10000 registration BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 53

Server and VM Configuration Sample UC manager Unified Presence Unity Connection 4000 users 1 Pub/TFTP,2 Sub 2 Nodes 1Pub,1 Sub Active- Active Expressway Imagicle UC App suite on Cluster(C&E) Windows server 6 Exp C,6 Exp E 2 Nodes Server Sizing 7.5K OVA Customer Limit- 340 5K Ova 5K Ova Customer Limit-40 Medium OVA 10,000 registrations,800 active calls 3xB200 M4 6 Cores 4 Cores 4 Cores 24 Cores 4 Cores 8000 users 1 Pub/TFTP,3 Sub 4 nodes 1 Pub,2 Sub 2 Clusters of 6 each Exp C & Exp E 2 Nodes Server Sizing 10K OVA 2x5K OVA 10K OVA 2 Medium OVA clusters,10,000,1600 active calls 7xB200M4 16 cores 8 cores 12 cores 48 Cores 4 Cores BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 54

Q & A

Please complete your Online Session Evaluations after each session Complete 4 Session Evaluations & the Overall Conference Evaluation (available from Thursday) to receive your Cisco Live T-shirt All surveys can be completed via the Cisco Live Mobile App or the Communication Stations Complete Your Online Session Evaluation Don t forget: Cisco Live sessions will be available for viewing on-demand after the event at www.ciscolive.com/global/on-demand-library/. 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public

Continue Your Education Demos in the Cisco campus Walk-in Self-Paced Labs Tech Circle Meet the Engineer 1:1 meetings Related sessions BRKCOL-2295 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 58

Thank you