Technical Overview of Cisco Preferred Architecture for Enterprise Collaboration

Technical Overview of Cisco Preferred Architecture for Enterprise Collaboration Luca Pellegrini Technical Marketing Engineer

Abstract Cisco Preferred Architectures (CPAs) provide a concise set of recommendations and best practices to simplify the deployment of Collaboration and provide a foundational set of products and feature through a recommended deployment model that covers most market segments based on common use cases. This session will discuss the latest CPA Cisco Validated Design targeted for Enterprise Collaboration and highlight some of the recommendations and best practices contained in it. The Collaboration portfolio will be broken down into 4 discrete sub-systems, call control, edge, conferencing and applications and will offer concise, prescriptive recommendations for each. Our documentation is split up into architecture and deployment process. In this technical overview we will only look at the architecture which comprises of the various components, their role and and design considerations and best practices. The deployment process is a more procedural aspect of the Cisco Validate Design and will only be covered in the presentation in form of reference for a complete understanding of the CPA Validated Design for Enterprise Collaboration.

Agenda What is Preferred Architecture? Call Control Conferencing Collaboration Edge Core Applications TMS Unity Connection Conclusion 4

What is Preferred Architecture?

What s the problem? Overlapping products CUCM or VCS MCU or TS VCS or Expressway Endless Part Numbers Typical BoM requires hundreds or thousands of unique part numbers Documentation Overload SRND, CVDs, SBAs, Install Guides, Deployment Guides, Solution Guides, White Papers, Configuration Guides, Design Guides, etc Fuzzy Vision What products should I invest in today, knowing they ll be developed and supported in the future? 6

Collaboration Preferred Architecture (CPA) What products to use to enable users for Unified Communications for simple deployments. Prescriptive recommendations Concise Documents Tested best practices Preferred Architecture provides prescriptive design guidance that simplifies and drives design consistency for Cisco Collaboration deployments Preferred Architecture can be used as a design base for any customer using modular and scalable approach 7

Collaboration Preferred Architecture (CPA) What products to use to enable users for Unified Communications for simple deployments. Prescriptive recommendations Concise Documents Preferred Architecture provides prescriptive design guidance that simplifies and drives design consistency for Cisco Collaboration deployments Preferred Architecture can be used as a design base for any customer using modular and scalable approach Preferred Architecture team provides feedback on solution level gaps to product teams Preferred Architecture will help you scale! Tested best practices 7

Preferred Architecture Strategy Collaboration Preferred Architecture is broken into four sub-systems which Makes the overall architecture easier to understand Allows products to be categorized based on function Within each sub-system create prescriptive architecture of recommended products and design best practices Sub-Systems: Call Control IM&P Conferencing Edge Applications Endpoints 8

Enterprise Document Deliverable PA Design Overview Cisco Validated Design PA Leverages CVDs Design Overview Document ~ 30 pages with an example BoM Detailed Design Guide http://www.cisco.com/c/en/us/solutions/enterprise/design-zone-collaboration/index.html 9

Call Control

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

Call Control Design Objectives Call control is centralized at a single location that serves multiple remote sites Multiple call control systems as iterations of the centralized call control model Management and administration are centralized Common telephony features are available across voice, video endpoints and Jabber clients Single call control and a unified dial plan are provided for voice, video endpoints and Jabber clients Critical business applications are highly available and redundant

Cisco Unified Communications Manager with IM & Presence DB Sync SIP Subscribers Publisher CTI/QBE SOAP API XML Publisher Subscriber Subscriber TFTP Subscriber Subscriber Subscriber MoH Up to 20 nodes total Up to 6 nodes total CUCM Voice/Video Nodes CUCM IM & Presence Nodes Unified CM with IM and Presence Service Cisco Unified Communications Manager and IM & Presence Cluster Not a real single cluster; still two separate databases Almost all IM&P configuration is done on the CM interface 13

Cisco Unified CM Trunking Recommendations Best Effort Early Offer (BE EO) trunk Use FQDN in SIP Requests for video endpoints in SIP Profile on both endpoints and trunks Redundancy achieved with multiple application servers per trunk (Unity Connection, Conductor, Expressway-C). OPTIONS Ping for trunk real-time status monitoring 14

Route Pattern/SIP Route Pattern Load balancing and alternate path for alias-based routing Device is assigned a Calling Search Space: SJCInternational Partitions: DN PSTNInternational onnetremote User dials a number or URI 1 st Choice 2 nd Choice Route Group 1 Cisco Unified CM selects the best pattern match through all partitions (SIP) Route Pattern Route List Route Group 2 Personal CMR Expressway-C CUBE Gateways Third-Parties start with the 1 st RG an continue to hunt through the Route List Top down or circular Top down or circular Trunks within the Route Group are selected based on a top down or circular rotation SIP Trunk SIP Trunk SIP Trunk SIP Trunk 15

Media Resource Selection Media Resource Group/Media Resource Group List Assigned to Device or Device Pool Media Resource Group List 1 st Choice 2 nd Choice Media Resource Group 1 Media Resource Group 2 Choose the highest priority MRG with an available device of the type required. Load Balance Load Balance Round Robin load-balance between devices of the same type within an MRG Media Resource Media Resource Media Resource Media Resource 16

Cisco Unified CM Call Routing Logic Basic Principles Cisco Unified CM matches the most specific pattern (longest-match logic) For call routing, an IP phone directory number acts as a route pattern that matches a single number There s much more on UCM routing logic. For more information see the Collaboration SRND: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab10/collab10/dialplan.html Cisco Unified CM Call Routing Logic User Dials 1200 Route Patterns 1XXX 12XX User Dials Directory Numbers 1234 1234 1234 17

Partitions and Calling Search Spaces Alphanumeric SIP URIs Calling Search Space Partition A *.com company.com *.* * 2 1 3 4 Similar closest pattern match logic applies Numbers show closest pattern match in priority order User dials abc@company.com 18

Deployment Considerations: Numeric Dial Plan Use +E.164 as DN addressing Benefit: ensure uniform phone number formatting across all enterprise contacts Use XXXX abbreviated intra-site dialing Benefit: allow abbreviated dialing for intra-site calls Use sitecode based abbreviated inter-site dialing e.g.: 8+<site code>+<extension> Benefit: use a normalized approach for inter-site calls Non-DID addresses in line with sitecode based abbreviated inter-site dialing Unique addresses Addtl. sitecodes per site or non-overlapping extensions 19

Import and Assign SIP URI How do I add SIP URIs to my existing dial plan? Easiest approach is with LDAP Directory Integration Recommendation is to map the mail attribute to Directory URI Set end user primary line if not already set, to associate Directory URI with primary extension Other URI import options include Bulk Admin Tool AXL API Manual update to DN page 20

URIs and Directory Integration Up to 5 URIs can be configured per DN End user s directory URIs are assigned to directory numbers based on enduser s primary extension; partition Directory URI (cannot be changed/deleted) other URIs can be in any partition; no need to have them in the same partition as the DN 21

URIs and DNs Primary URI One URI associated with DN is marked the primary URI Auto-generated URI based on user s primary extension will always be the primary URI If no auto-generated URI exists one of the other URIs can be marked primary Primary URI will be used as URI identity for calls from/to this line 22

Multi-cluster scenario IM&P UCM IM&P UCM IM&P UCM Branch1 Branch2 Branch1 Branch2 Branch1 Branch2 Recommendation: Centralized Call Processing Model (Single Call Processing Cluster) Full-Mesh Distributed Call Processing Deployment Model when required. This model is based on multiple iterations of the Centralized Call Processing Deployment Model. SME out of the PA scope. 23 SIP XMPP

Multi Cluster scenario Cisco Unified CM Dial Plan Intercluster Lookup Service (ILS) was introduced in Cisco Unified Communications Manager Release 9 Provides an overlay network between UCM clusters to facilitate information exchange SIP URI replication was the first application for ILS Addresses issue of same domain multicluster URI routing UC Release 10 adds support for exchange of numeric call routing information Simplifies configuration in large deployments based on dynamic exchange of numeric call routing information 24

ILS and GDPR Learning and routing Learned from ILS bob@cisco.com nyc.route frank@cisco.com fra.route UCM1 sfo.route nyc.route UCM2 Learned from ILS alice@cisco.com sfo.route frank@cisco.com fra.route alice@cisco.com Call controls establish ILS Exchange routestring: sfo.route ILS Exchange bob@cisco.com routestring: nyc.route URI information flooded Each call control creates table with URIs and associated SIP route string SIP route strings routed by SIP route patterns UCM3 Learned from ILS alice@cisco.com sfo.route bob@cisco.com nyc.route routestring: fra.route Numbers are also learned and routed (CM 10+) frank@cisco.com 25

Sizing Simplified sizing rule to avoid the usage of collaboration sizing tool The tool is still needed if the requirements go outside perimeter defined in the PA doc The tool is available at: http://tools.cisco.com/cucst 26

Sizing Cisco Unified CM Cluster Up to 5,000 users Based on 7.5K OVA. We are considering 5,000 devices and a heavy load I.e. each user configured with a Remote Destination Profile for Single Number Reach, can use Extension Mobility, each endpoint can be CTI controlled, some shared lines are configured, mobile and remote access is enabled and more For the full list of assumptions see the PA CVD sizing chapter at: http://www.cisco.com/c/en/us/td/docs/solutions/cvd/c ollaboration/enterprise/collbcvd/sizing.html#pgfid- 1066475 TFTP 1 TFTP 2 5,000 devices Publisher Primary Call Processing Subscriber Backup Call Processing Subscriber These assumptions can be used under normal conditions (i.e. not a contact center scenario) Unified CM nodes 27

Sizing Cisco Unified CM Cluster Up to 10,000 devices The sizing templates are valid up to 10,000 devices. 5,000 users with Jabber and a hardware phone=10,000 devices TFTP 1 10,000 devices Publisher Primary Call Processing Subscriber Primary Call Processing Subscriber TFTP 2 Backup Call Processing Subscriber Backup Call Processing Subscriber Unified CM nodes 28

Sizing IM and Presence Server Deployment Size (Users) Less than 2,000 Between 2,000 and 5,000 Between 5,000 and 15,000 IM & Presence Nodes to be deployed One IM & Presence pair using the 2k-user OVA One IM & Presence pair using the 5k-user OVA One IM & Presence pair using the 15k-user OVA 29

Conferencing Sub-System

Conferencing Design Objectives Flexible, extendable architecture that supports deployment of one or more rendezvous, scheduled, and ad hoc conference resources Dynamic optimization of conference resources on the TelePresence Server for inbound calls Resilience in the video network Simplified, optimal user experience for conference participants

Conferencing Architecture Unified CM Expressway-C Expressway-E Internet TelePresence Conductor Cisco TMS Personal Multiparty TelePresence Server General TelePresence Server Scheduled TelePresence Server SIP Media+Content HTTP(s) 33

Multipoint Products Products discussed in the PA Conductor as the orchestrator for multipoint devices TelePresence Server platforms chosen as multipoint devices MCUs still a valid approach but not included in the PA Architectural considerations don t change 34

TelePresence Server Platforms TelePresence Server on VMWare (specs based) TelePresence Server on VMWare Appliances Blade 8-core 310 1 to 12 ports at 720p 1 to 10 ports at 720p 400v 320 8710 30vCPU 1 to 36 ports at 720p 1 to 24 ports at 720p 1 to 24 ports at 720p 7010 1 to 24 ports at 720p 1 to 24 ports at 720p Note: For simplicity, only capacity for 720p is shown. TS is capable of many other resolutions and frame rates with differing limits on capacity. All numbers represent remotely managed mode (Conductor required) capability. See release notes for further detail. 35

What does TelePresence Conductor do? What does this mean? Conference Virtualization What does this mean? Resource Management/ Conference Bridge Selection What does this mean? Centralized Conference Provisioning and Administration Consistent User Experience Whether using Ad hoc or Rendezvous or Scheduled Conferences Knows all the available and used ports and optimizes resources. Intelligent Bridge selection Automatic cascading of MCUs Single configuration applied to any conferencing resource Ad hoc Rendezvous and scheduled Conference support 36

Conductor and Unified CM How does the model change? Conference Bridge in UCM configuration SIP trunk in UCM configuration Individual bridges Unified CM 10 37

Conductor and Unified CM How does the model change? Conference Bridge in UCM configuration Emulates MCU API, looks like MCU to UCM Utilizes B2BUA Accepts SIP Signaling Uses Multiple IP addresses (65 Max.) Management IP Location specific IPs IP address for Instant Meetings IP address for Personal CMR Added Conductor SIP trunk in UCM configuration Individual bridges Unified CM 10 37

Ad-Hoc Conference Endpoint creates an ad hoc conference requesting to join three participants Unified CM initiates an ad hoc conference on Conductor TelePresence Conductor creates the conference on a TelePresence Server Unified CM routes the call(s) to TelePresence Conductor TelePresence Conductor routes the call(s) to the TelePresence Server hosting the relevant conference Endpoint Unified CM (UCM) Conductor TelePresence Server (TS) Other Participants Ad hoc conference request Ad hoc conference initiation by UCM Conductor creates conference on TS UCM routes call(s) to Conductor 38 Conductor routes call(s) to TS

Rendezvous Conference Endpoint dials a rendezvous conference number Unified CM matches the dialed number to a (SIP) route pattern or route string Unified CM routes the call to the TelePresence Conductor via SIP trunk TelePresence Conductor matches the called number to an alias and creates a conference on TS TelePresence Conductor routes the call to the TelePresence Server 39

Scheduled Conference User schedules conference by using the Self-Care Portal or email integration. User is notified of the meeting details TMS uses APIs to create a conference on Conductor at the time requested Conductor uses APIs to create a conference on the chosen TS User dials the alias or is dialed from TS Unified CM routes the call to the TS (dial-in, OBTP) or to the user (dial-out) 46

Rendez-Vous SIP Route Pattern Unified CM Alias Conductor Route Pattern Route List Template Route Group Service Preference Endpoint SIP Trunk Location Pool 41 47 Telepresence Telepresence Server Servers

Ad-Hoc Unified CM Conductor Template MRGL Service Preference Pool MRG Endpoint Media Bridge Location Telepresence Telepresence Server Servers 48

Conductor Clustering For Your Reference Unified CM Media Resource Group Media Bridge1 Ad-Hoc 10.1.1.1 10.1.1.1 Conductor 1 Conductor Media Bridge2 10.1.2.1 10.1.1.2 Rendez-Vous Trunk IP1 Trunk 10.1.1.2 10.1.2.1 Conductor 2 Trunk IP2 10.1.2.2 10.1.2.2 43

Conductor Clustering For Your Reference Unified CM Media Resource Group Media Bridge1 Ad-Hoc 10.1.1.1 10.1.1.1 Conductor 1 Conductor Media Bridge2 10.1.2.1 Rendez-Vous Trunk IP1 Trunk 10.1.1.2 10.1.2.1 10.1.1.2 Conductor 2 65 IP addresses per Conductor server Up to 3 nodes in a cluster Up to 30 bridges per cluster Trunk IP2 10.1.2.2 10.1.2.2 43

Conductor Location Setup Unified CM Media Resource Group Video Conductor Ad hoc Media Bridge1 192.168.2.10 Media Resource Group Voice Location Voice Location Video Media Bridge2 192.168.1.10 192.168.1.10 192.168.2.10 Rendezvous Trunk for Voice Trunk IP 192.168.1.11 192.168.1.10 192.168.2.11 Trunk for Video Trunk IP 192.168.2.11 44

Scheduled Conferences Optimized Conferencing Release 4 WebEx Unified Communications Manager Expressway-C Expressway-E Internet B2B, B2C, Cloud Services Conductor Ad Hoc and Rendezvous TMS Scheduled Remotely Managed Mode Dedicated pools for assured scheduling vs shared pool (pros and cons) Alias matching the TMS alias range A dedicated template with scheduled conference set to yes to enforce security

Multi Cluster Scenario Multiple Unified CM clusters might share a single Conductor cluster with separate pools for the Telepresence Servers However, if the Unified CM clusters are dispersed worldwide, it is best to dedicate a Conductor cluster per Unified CM cluster to avoid relying on international connection for local calls Use ILS between different clusters if alphanumeric SIP aliases and a single SIP domain are used 46

Sizing Considerations: Telepresence Server For Your Reference http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/ts/admin_guide/ Cisco-TelePresence-Server-Printable-Help-4-1-1-79-Virtual-Machine.pdf 47

Sizing Considerations: Conductor Total number of TelePresence Servers Total number of concurrent participants across all TelePresence Servers Small OVA 30 50 Large OVA/Appliance 30 2,400 48

49 Collaboration Edge

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.

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 52

53 Business-to-Business Communications

Business-to-Business call scenarios Format SRV records for SIP and H.323 (RFC 2782) _sip. _tcp.example.com 86400 IN 10 60 5060 expe.example.com SRV 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. If connection fails, client fallback to the higher priority record Weight: for records with same Priority, it is used for load-balancing Port: TCP or UDP port for the service 54 Targed: hostname or IP Address for the host Providing the service

Service Discovery Smallbox _sips._tcp.example.com. 86400 IN SRV 10 60 5060 bigbox.example.com. _sips._tcp.example.com. 86400 IN SRV 10 40 5060 smallbox.example.com. _sips._tcp.example.com. 86400 IN SRV 20 0 5060 backupbox.example.com. Backupbox 40% Bigbox 60% Dial: luca@example.com 55

Business-to-Business call scenarios Format SRV records for SIP and H.323 (RFC 2782) SIP _sips._tcp.<fully.qualified.domain> 5061 _sip._tcp.<fully.qualified.domain> 5060 _sip._udp.<fully.qualified.domain> 5060 H.323 _h323ls._udp.<fully.qualified.domain> 1719 - RAS _h323cs._tcp.<fully.qualified.domain> 1720 - Call Signaling Example _service._protocol.<f.q.dn>. TTL Priority Weight Port Target Host _sips._tcp.company.com. 86400 20 5 5061 vcs.company.com _h323ls._udp.company.com. 86400 20 5 1719 vcs.company.com 64

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 to reach the called user or endpoint 6. The call is established and media traverses the firewall securely over an existing traversal connection 58

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

B2B Call Flow Single Edge with SIP only in the internal network Interworking set to off Expressway-C Interworking set to on Interworking off on Expressway-C Interworking on on Expressway-E B2B call first attempted using SIP (native protocol) If doesn t find the alias, same call attempted with H.323 Interworking takes place on Expressway-E Cisco Unified CM Expressway-E Internet 60

Outbound Calls Multiple Edges HQ SJC Branch Office RCD Use the nearest Edge for outbound calls Use the remote Edge if the nearest is not available Works with 2+ Edges Expressway-E_RCD Company B CUCM IM&P Internet Expressway-E_SJC 61

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 62 Phone in RCD 69

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 63

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) Routing based on the minimal distance between the edge and the called device (minimizes costs) 64

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

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 Geo DNS services are easy to configure and cost-effective 66

Geo DNS: latency routing and round-robin configuration settings for B2B calls SRV Record CNAME Record A-Records Expressway-E _sips._tcp.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 67

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

IP Address Dialing for Internet devices: Inbound Calls Fallback alias Fallback alias A.B.C.D Expressway-C Expressway-E H.323 device dials A.B.C.D and call reaches the Expressway-E. The destination IP A.B.C.D is statically mapped to the fallback alias and sent to Expressway-C accordingly to search rules. Call can be sent to a TelePresence Server for a multipoint meeting or to Unity Connection for IVR-based directory services SIP clients using direct DNS dialing can reach the fallback alias. Same considerations apply for SIP clients not registered to a SIP Proxy 69

IP Address Dialing for H.323 Internet devices: Inbound Calls Fallback alias for point-to-point and multipoint calls: Unity Connection call flow (1) luca@cisco.com +391000 812000 luca@cisco.com +391000 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 70 Unity Connection

IP Address Dialing for H.323 Internet devices: Inbound Calls Fallback alias for point-to-point and multipoint calls: Telepresence Server call flow (2) luca@cisco.com +391000 812000 3. Internet user enters the conference Expressway-C Expressway-E Cisco Unified CM A.B.C.D 2. Fallback alias set to 812000@domain Cisco Unified Presence Server 1. Dial A.B.C.D 71 Unity Connection

IP Address Dialing: Outbound Calls Cisco Unified CM IP dialing IP address dialing is a capability of H.323 endpoints Cisco Unified CM doesn t support native IP address dialing since it uses SIP Route Patterns for B2B calls and a domain is needed Conclusions: instruct the users to append a suffix such as: 10.10.10.10@ip UCM matches a ip SIP Route Pattern and routes the call to Expressway-C Expressway-C strips the @ip and sends out the call to Expressway-E as IP dialing 72

73 Mobile and Remote Access

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 voicemail, directory) SIP (audio, video) XMPP (IM&P) IM and Presence Expressway C Firewall Expressway E 74

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 10 10 8443 expwy1.example.com. _collab-edge._tls.example.com. SRV 10 10 8443 expwy2.example.com. _cisco-uds record needs be available only in internal DNS _cisco-uds._tcp.example.com. SRV 10 10 8443 ucm1.example.com. _cisco-uds._tcp.example.com. SRV 10 10 8443 ucm2.example.com. 75

Multiple Clusters Support Cluster2 IM and Presence Cisco Unified CM HTTPs (provisioning, visual voicemail, directory) SIP (audio, video) XMPP (IM&P) Cluster1 Cisco Unified CM IM and Presence Expressway C Firewall Expressway E 76

77 PSTN Access with CUBE and Gateways

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 78

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 79 Backup for RCD users

80 Core Applications

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

Core Applications Unity Connection and TMS Design Objectives Creation and provisioning for individual end-user Collaboration Meeting Rooms (CMRs) User has access to TMS interface embedded in Self Care Portal Eases deployment of new infrastructure components Unified messaging available on multiple end-user platforms

Cisco TelePresence Management Suite Unified Service Orchestration and Control 83

TMS Architecture TMSXE Active Nodes TMS Scheduling request TMSPE Exchange Servers SQL Active Directory Network Load Balancer Single virtual IP address address for management TMSXE must be deployed separately TMSPE is co-resident with TMS TMSPE TMSXE TMS Passive Nodes 84

Personal CMR Provisioning CMR Template configuration on TMS This template will be created on Conductor by TMS Service Preference on Conductor for this template Alias generated from AD username Number generated from AD telephone number 85

CMR created at User s provisioning 86

Unified Communications Self Care Portal TelePresence Conference Meeting Room and Scheduling This tab provided by TelePresence Management Suite (TMS) Provisioning Extension (TMSPE) Your scheduled TelePresence meetings, including WebExenabled TelePresence, One Button to Push, etc. Your Collaboration Meeting Room (CMR) Your favorites and account settings 87

TMS Simplified Sizing Deployment Cisco TMS Cisco TMSXE Cisco TMSPE Regular Deployment (2 vcpu OVA) 2 nodes total: 2x TMS/TMSPE/TMSXE Additional servers for Microsoft SQL < 200 controlled systems (endpoints added to TMS for scheduling) < 100 concurrent participants < 50 endpoints bookable in Microsoft Exchange < 1,000 Collaboration Meeting Rooms Large Deployment (4 vcpu OVA) 4 nodes total: 2x TMS/TMSPE and 2xTMSXE Additional servers for Microsoft SQL < 50 concurrent ongoing scheduled conferences < 5,000 controlled systems < 1,800 concurrent participants < 250 concurrent ongoing scheduled conferences < 1,800 endpoints bookable in Microsoft Exchange < 48,000 Collaboration Meeting Rooms There are other possible TMS deployments but they are not covered in the PA documentation. For instance, the single server deployment that has all TMS, TMSPE, TMSXE, and Microsoft SQL components co-resident in the same virtual machine is not considered because it doesn t provide redundancy. 88

Unity Connection Architecture Unified CM Unity Connection Publisher Subscriber Mailbox synchronization Directory synchronization On-Premises or Cloud-Based Exchange Directory Active Directory Mailbox accounts Single Inbox Directed calls v. forwarded calls Auto-attendant and IVR functionalities TUI/Web access to voicemails Voicemail 89

Unity Connection sizing Deployment size Unity Connection nodes to be deployed for Active/Active 1,000 users One Unity Connection pair using 1k-user OVA 1,000-5,000 users One Unity Connection pair using 5k-user OVA 5000-10,000 users One Unity Connection pair using 10K-user OVA 90

Conclusions Preferred Architecture is available at this link: http://www.cisco.com/c/en/us/solutions/enterprise/validated-designscollaboration/index.html This is an ongoing process. Feedback is very important to address future releases What is not included in the PA might still be a supported scenario. Check the latest release of Collaboration SRND which includes everything is possible with Cisco Collaboration architecture http://www.cisco.com/c/en/us/solutions/enterprise/unified-communicationsystem/index.html 91

Call to Action Visit the World of Solutions for Cisco Campus Walk in Labs Technical Solution Clinics Meet the Engineer Lunch time Table Topics DevNet zone related labs and sessions Recommended Reading: for reading material and further resources for this session, please visit www.pearson-books.com/clmilan2015 92

Complete Your Online Session Evaluation 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 93