Cisco Meeting Server, on-premises and hybrid large scale conferencing design

Transcription

1

2 Cisco Meeting Server, on-premises and hybrid large scale conferencing design Aniello (Nello) Zanfardino, Solution Architect Cisco Advanced Services

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

4 Agenda Cisco Meeting Server, on-premises and hybrid large scale conferencing design Introduction Core Edge MS Interoperability Hybrid Conferencing Conclusions Backup slides

5 Introduction

6 CMS - Key Capabilities What CMS does Video Conference Audio Conference Spaces Browser Access (WebRTC) Cisco Meeting Application (Native CMA) MS Interoperability Interoperability Scaling Clustering Multitenancy Virtual Meeting Rooms Built in NAT traversal Security Scalable Reduced costs Multiple ways to join DTMF, IVR Enriched meeting Virtual meeting rooms Multiple VMR per user content sharing WebRTC browsers Users & Guests access Session Controls (mute, drop, etc) Session handover browser/video room PC/MAC/iOS Same functionalities and look & feel as WebRTC client Better video quality Native Any Lync/S4B version On-prem and cloud Bidirectional content Seamless user experience Cisco Meeting Server 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 6

7 Hardware Components How CMS looks like excluding legacy servers CMS 2000 Flagship, Highest Capacity CMS1000 Swiss Knife High Capacity Spec Based Flexibility Medium capacity BRKCOL-2803 Abhijit Dey Designing and deploying multiparty conferencing for telepresence video 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 7

8 Core CMS sizing Platform Capacity [HD sessions per server(*)] CMS (up to CMS 2.2) CMS 1000 (****) 96 MM410v (legacy) 64 MM400v (legacy) 32 Dedicated server VM (**) 2.5 per physical core Session Type Full-HD 1080p30 HD (*) 720p30 Capacity Multipliers p30 2 Audio (***) 40 Co-resident VM (hyper-threading disabled) 1.25 per physical core (*) HD 720p30 video calls with 720p5 content and up to 2.5 Mbps bandwidth (**) CPU 2.5 GHz+, 1 GB vram per vcpu, hyper-threading enabled, more details at: (***) With G.711 codec. Max 450 participant per conference per CallBridge, max 3000 audio calls (****) Cms1000 VM : hyper-threading enabled,2 Virtual Sockets, 35 Core per sockets, 58 GB vram,100 GB HD Max 100 WebRTC sessions per server and max 500 sessions per XMPP cluster (see edge section) 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 8

9 Management / Admin methods How to interact with CMS API CLI / Console SFTP WebAdmin (Web GUI) 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 9

10 CMS - Services CMS Key Software Components Call Bridge (core) XMPP (core) WebBridge (core, edge) Turn Server (edge) Load Balancer (edge) H323 GW and SIP Edge (legacy) Video Bridging core Call Control Media processing Clustering Client and Inter-component signalling IM&P WebRTC with compatible browsers (Chrome, Firefox, Opera) Brand-able VP8 & H.264 Firewall traversal for media traffic XMPP signalling firewall traversal (proxy) H323 GW (not GK) SIP firewall transversal Equivalents services exist in Expressway Webadmin (core) Web Administration Recorder & Streamer (core) Recording meetings to external storage Streaming meetings to external server Database cluster (core) Database Clustering Redundancy and Resiliency Services are split between Core Service Edge Services depending on their placement in the network 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 10

11 Architecture Core only Single server CMA Clients WebRTC Clients XMPP WEBBRIDGE SIP XMPP CORE SERVER CALLBRIDGE HTTPS / WEBRTC Media AD LDAP Although the term CMA client in documentation may refer to both native and WebRTC clients, for simplicity, we will use the CMA name only for native clients 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 11

12 Architecture core and edge (pre-expressway WebProxy) External CMA Clients WebRTC Clients DMZ EDGE SERVER LOADBALANCER TURN WEBBRIDGE SIP Internal XMPP WEBBRIDGE XMPP CORE SERVER CALLBRIDGE HTTPS / WEBRTC Media AD WebRTC Clients LDAP CMA Clients 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 12

13 CMS Clustering Benefits Scalability Resiliency Geographic optimization: Reduce latency using closest call bridge Minimize WAN traffic Components Database Clustering Spaces Dial Plan Cluster-wide configuration Call Bridge Clustering Distributed calls 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 13

14 Database Clustering Highlights Odd number of DB servers required for reliable master election if network split DB nodes needs to see more than half of the cluster members to be eligible as master Max 5 DB server, recommended 3 All DB operations are directed to the master Separate DB server improves CallBridge robustness and simplifies upgrades (suggested with server with distribute processing (cms2000, X3) and large DBbs (>10k spaces)) Max of 8 Call Bridges per cluster. Designs more than 8 Call Bridges in a cluster need to be validated by Cisco BU 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 14

15 Clustering Architecture - Call Bridge with dedicated DB Call Bridge Cluster Keepalives Call Status Distributed Calls Max 300 ms RTT (max 100 ms RTT within CallBridgeGroup) Cluster sync Max 200 ms RTT Database Connect DB Master Spaces Users Dial-plan Cluster-wide configuration Max 300 ms RTT Call Bridge Cluster HTTPS + SIP Database Connect TLS/Postgres Postgres TCP/TLS Port : 5432 DB Slave Database Cluster DB Slave Database Cluster TLS / Postgres 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 15

16 Clustering Architecture - Call Bridge with co-located DB DB Slave Database Cluster Call Bridge Cluster DB Slave Keepalives Call Status Distributed Calls Call Bridge Cluster HTTPS + SIP Database Connect TLS/Postgres Cluster sync DB Master Spaces Users Dial-plan Cluster-wide configuration Database Cluster TLS / Postgres Other combinations of CallBridges and DataBase are also possible, best choice may vary with customer deployment 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 16

17 Distributed calls Resiliency, scale, geo-distribution Conference 1 Conference 2 distribution links with multiple streams for remote participants (*) Preview in CMS 2.3 : more than 4 streams in the distribution links (Cluster.peerlinkbitrate >= 2Mpbs) Americas EMEA (*) up to 4 streams using max peerlinkbitrate bandwidth (before CMS 2.3) APAC 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 17

18 Distributed call Setup For reference Enpoint1 CUCM1 Call Bridge CB1 Call Bridge Cluster Call Bridge CB2 CUCM2 Enpoint2 DB: MySpace1 SIP: INVITE MySpace1 SIP: INVITE MySpace1 Dual protocol HTTP/SIP inter- CallBridges trunk First call established SIP: INVITE MySpace1 Intra-cluster dialogue finds that the space is already active in in CB1 CB1: generating peer URI for cospace <spaceid> SIP HTTPS / SIP Media Distributed Video Call established CB2: call <Call ID> now peered with conference on server CB1 (peer URI Conf_ID@CB1) SIP: INVITE Conf_ID@CB Cisco and/or its affiliates. All rights reserved. Cisco Public 18

19 XMPP Clustering Highlights XMPP High Availability mechanism with keepalives 3 or 5 XMPP Servers Master election similar to the database cluster Call Bridges gets XMPP server list from DNS _xmpp-component._tcp SRV record (use GEO DNS to optimize geographically the XMPP server selection) Call Bridge must be configured on all XMPP servers with same credentials (use the xmpp callbridge add once and then xmpp callbridge add-secret) All XMPP traffic is forwarded to XMPP master (CallBridge/loadbalacers can send message to any XMPP server) Full mesh connectivity from LoadBalancers to XMPP servers is not required Max 500 sessions per XMPP cluster Max 200 msec RTT between XMPP servers 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 19

20 Deployment Prerequisites - DNS Several DNS records are required for the solution to work properly DNS The main DNS records are: 1. 1) DNS A records for all the servers involved (e.g. cms1-us.mycompany.com) 2. 2) DNS A records for user access to services (e.g. meet.mycompany.com) 3. 3) DNS SRV records to locate XMPP server: 4. -For clients and internal services _xmpp-client._tcp.mycompany.com port For CallBridges to locate XMPP cluster members _xmpp-components._tcp.mycompany.com port A more comprehensive list is in installation docs Large conference design involves (discussed in the Edge section) GEO DNS for optimal allocation of service entry point from Internet Split DNS allocation of external, internal service 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 21

21 Deployment Prerequisites - Certificates Components that need a certificate: WebAdmin XMPP WebBridge Callbridge Loadbalancer Trunk Turn (if using TLS) Database Cluster Recording server Streaming server Certificate types: self-signed Private CA Signed Public CA Signed 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 22

22 Reduce Certificate Complexity Plan/design certificate structure before deployment Combined Certificates Certificates shared among multiple components and servers Use multiple FQDN entries in certificates Subject Alternative Name (SAN) CA-Signed Combined certificates have some limitations: database clustering (client) needs separate certificate Lync/S4B integration have specific requirements Wildcard certificates Supported but limitations applies too Cisco Meeting Server 2.x, Certificate Guidelines for Scalable and Resilient Server Deployments 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 23

23 Use case 1 CMS Core Design Call Control : traffic optimization Bridge and DB Cluster distribution LDAP integration : user and space names Domains structure and Dial Plan Call Admission Control TMS Scheduling

24 Use Case 1 Large enterprise with established worldwide collaboration infrastructure with the need of pervasive video services with global coverage Structural requirements (*): Three worldwide regions (**) Redundancy with 2 Data Centres (DC) in each region (**) Traffic Optimization (localize the traffic to regions whenever possible) Conferencing requirements: Virtual Meeting Rooms (VMR) Scheduled meetings with OBTP (One Button To Push) Expected load around 2000 HD ports evenly split between the regions (*) Structural requirements will be the same in most of the use cases presented (**) More regions or more DCs can be added to the same design 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 25

25 Use Case 1 - Architecture Summary (**) AD (**) Calendar TMS+TMSXE Sizing for use case 1 : 6 x CMS-2000 : 3000 HD ports 3 x spec based VMs for DB servers (**) Global Routing & Management... Regional Call Control Core Core Core Conferencing (CMS cluster) Americas Database EMEA Database APAC Database (**) The design discussed do not depend on the use of SME, as long as the global routing call control entity (CUCM or SME) is aware of global and regional topology 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 26

26 Call Control Trunks... Global Routing & Management... Regional Call Control Conferencing (CMS cluster) Americas EMEA APAC Trunk the CMS cluster to global routing call control to simplify configuration and to reflect the global reach of the CMS cluster One CUCM trunk per CMS to leverage CUCM route advance on call error codes (see load limit slide) BRKCOL-2614 Glen Lavers Technical Overview of Preferred Architecture for Enterprise Collaboration 11.6 release SIP HTTPS / SIP 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 27

27 Traffic Optimization 1 Localization Localization == keep traffic in region whenever possible. Traffic from endpoints (CMS numeric pattern and CMS SIP domains) to CallBridges is localized by leveraging CUCM CSS/partition/RL/RG or Local Route Groups.. Global Routing & Management... Regional Call Control Americas EMEA APAC Conferencing (CMS cluster) Traffic back from CallBridges is localized by configuring CallBridge (scope) specific outbound dial-plan rule (with CMS API) 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 28

28 Traffic optimization 2 - HA and loop avoidance Avoid call loop when using CMS in other region as backup/overflow Trunk_to_other_SME. IncomingCSS (RP,RL,RG) 1) EMEA_CB1 2) EMEA_CB2 Core Americas. Incoming CSS of trunk to other SME can only see local CMS. EMEA_CB1 EMEA. EMEA_CB2 Incoming CSS of trunk to leaf CUCM has access to regional CMS and other SME s. Trunk_to_regional_CUCM Incoming CSS (RP,RL,RG) 1) EMEA_CB1 2) EMEA_CB2 3) other SMEs Core APAC. Global Routing & Management Regional Call Control Conferencing (CMS cluster) CMS 2.x White Paper : Load Balancing Calls Across Cisco Meeting Servers 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 29

29 Intra-region or Intra-DC distributed conferences should be limited Conference 1 Conference 2 Conference 3 Conference 4 Focus on one Region EMEA For these four conferences load balancing distribute calls may create up to 17 call legs (9+4x2) With more CallBridges number can increase fast!!. EMEA If call legs belonging to the same conference are bound to a single CallBridge in the region, then the number of call legs is reduced to 9 (even with more CallBridges ) 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 30

30 Call Bridge Group - Feature I: Grouping CMS 2.1 introduces the concept of CallBridge Group When CallBridges in the same region or DC are placed in the same CallBridge Group, conference will not be distributed between them It leverages the SIP replace mechanism (supported by CUCM) When CUCM makes a call to a conference (space) in a CallBridge, if the conference exists on another CallBridge in the same group, then the call is replaced to the correct call Bridge Network Requirement : Max latency between members of a Call Bridge Group 100 ms RTT replace query for conference YYY using server CB2 (priority: 0, load level: 0, conference is running: 1) 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 31

31 Call Replacement (simplified flow) For reference CUCM Call Bridge CB1 Call Bridge group EMEA Call Bridge CB2 SIP: INVITE MySpace1 Space MySpace1 SIP: INVITE MySpace1 with Call_ID Supported:.. Replace Video EP with existing call to MySpace1 on CB2 Do not forget CUCM Rerouting CSS on CUCM CMS trunk and Accept replace on SIP trunk security profiles replace query for conference YYY using server CB2 (priority: 0, load level: 0, conference is running: 1) replacing call Call_ID to conference YYY on server CB2 replacing call Call_ID from server CB1 into conference YYY SIP: INVITE EndpointURI From spaceuri Replaces: Call_ID SIP HTTPS / SIP SIP: INVITE EndpointURI SIP: CANCEL Call_ID Video Call established on CB2 only Media 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 32

32 Call Bridge Group Feature II: Load Balance A mechanism is necessary to ensure load balancing of conferences in the same CallBridge Group EMEA_CUCM This is implemented by distributing conferences based on conference_id and bridge_id hashing that generate a priority in the CallBridge choice 3) Invite w/replace to Space02 1) Call to Space 02 It is totally transparent to the user and it leverages the same replace mechanism for call reallocation Load balancing is applied from the first call to a space replace query for conference YYY using server CB2 (priority: 0, load level: 0, conference is running: 1) EMEA_CB1 2) check EMEA_CBGroup EMEA_CB2 Space02 (priority EMEA_CB1, then EMEA_CB2) 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 33

33 Call Bridge Group - Feature III: LoadLimit Before version 2.1 the CMS carried on accepting calls even when it was full by simply reducing other call resolution to accommodate load With 2.1 a max load Limit can be configured on each CallBridge so that when a call is received and the CMS is above a limit CMS rejects the call; Limit is variable according to the conference state CUCM receives SIP 488,Not acceptable here, and Dial Plan (RG, RL) can be configured to route advance to next call bridge Max load Limit 100% Existing Conference Threshold 80 % New Conference Threshold 50% Because of this, one SIP trunk per CMS is required, so that error handling surface to CUCM RG/RL level CallBridge1 log: call XX: ending; local teardown, system participant limit reached CallBridge2 log: replace query for conference YYY using server CB2 (priority: 0, load level: 2, conference is running: 1) 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 34

34 LDAP integration : user and space names CMS can be synchronized with LDAP to generate users and spaces A good mapping of AD fields into CMS objects creates a solid and flexible naming structure Active Directory CallBridge Use case 1 Database AD + Space Key parameters for mapping Username: $samaccountname$@meet.ucdomain.com Space URI user part: $samaccountname$.space Space secondary URI user part: 888$telephoneNumber$ User (XMPP ID & URI) Alice@meet.ucdomain.com Space URI Alice.space@meet.ucdomain.com 2 nd Space URI @meet.ucdomain.com 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 35

35 CMS Dial plan : Inbound call processing Stage 1 Incoming Is the call for this CMS? For spaces, users, IVR? Does the call require a Lync meeting resolution? Stage 2 Forwarding Shall the call be forwarded? With domain rewrite? Stage 3 Outgoing Where to send the call? And how? In use case 1: CUCM SIP domain ucdomain.com CMS cluster SIP domain meet.ucdomain.com CMS space will have dual alphanumeric and numeric URI 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 36

36 CMS dial plan configuration details Focus on configuration of one region: EMEA EMEA Inbound dial rules for CUCM Domain name Priority Targets spaces Targets users Targets IVRs meet.ucdomain.com (1) 100 Yes Yes Yes No EMEA_CB1_fqdn (2) 50 Yes Yes Yes No Targets Lync EMEA_CUCM ucdomain.com EMEA_CBGroup EMEA_CB1 EMEA_CB2 meet.ucdomain.com EMEA_CB2_fqdn (2) 50 Yes Yes Yes No EMEA Outbound dial rules for CUCM Domain SIP proxy to use Local contact domain EMEA Forward dial rules : none Local from domain Trunk type Call Bridge specific outbound dial rule (API) with same priority (keep traffic in EMEA) Behavior Priority(5) Encryption CallBridge Scope ucdomain.com EMEA_CUCM_fqdn (3) meet.ucdomain.com Standard Continue 10 <match CUCM> EMEA_CB1 ucdomain.com EMEA_CUCM_fqdn (3) meet.ucdomain.com Standard Continue 10 <match CUCM> EMEA_CB2 EMEA_CB1_IP EMEA_CB1_IP (4) Standard Continue 5 Auto All EMEA_CB2_IP EMEA_CB2_IP (4) Standard Continue 5 Auto All Dial transform for CMA/WebRTC numeric dial-out type Match exp. Transform Prior. Action strip ($1/(.*)/) $1@ucdomain.com 10 accept (1) Highest priority domain will be used in meeting request invite (2) Assuming CUCM trunk has CMS FQDN as destination address (3) alternative : multiple rules for each Subscriber (4) required by distributed calls when default SIP route is used (5) Same domain entries need equal priority 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 37

37 TMS Scheduling From version 15.3 TMS supports CMS as scheduled bridge CMS can be added as scheduled Bridge in TMS CMS clusters support Set CMS as preferred MCU 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 38

38 TMS Scheduling CMS interaction Administrator configures a CMS meeting number range in TMS (with a domain) TMS programs a set of static meeting into CMS TMS reconfigures the static meeting at the conference start time by activating it and updating the meeting name 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 39

39 Use Case 1 TMS Scheduling and OBTP - Flow 1) Meeting TMS+TMSXE. 4) OBTP to Join conference Calendar 3) Program meeting on CMS. 2) Send OBPT to Endpoints 4) OBTP to Join conference. Global Routing & Management Regional Call Control... 5) Distributed call Conferencing (CMS cluster) Americas EMEA APAC SIP CMS API EP API HTTPS / SIP EWS Media 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 40

40 Use case 2: Scheduled conferences with white glove services

41 Use Case 2 A large traditional worldwide enterprise where employers meeting are mediated by white gloves service from an internal video service team Structural requirements (*): Three worldwide regions Redundancy with 2 DC in each region (**) Traffic Optimization Conferencing requirements: The great majority of the video conferences are Scheduled and managed by the video team Connected automatically (auto-connect) (*) Structural requirements will be the same in most of the use cases presented (**) More regions or more DCs can be added to the same design 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 42

42 Key challenges with scheduling with white glove services Challenge 1: Optimal call routing with auto-connect Solution: If video endpoints belong to different regional SIP domains, then a single worldwide CMS cluster can still be used and call routing optimized - TMS and CMS 2.2+ to enable loadbalanceoutgoingcalls in CallBridgeGroup - configure per region CallBridgeGroup specific outbound dial rules If video endpoints belong to same SIP domain, then a separate regional CMS clusters can be deployed Challenge 2 : TMS Conference Control Center (CCC ) does not support CMS Solution : Cisco Meeting Manager (CMM) 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 43

43 TMS Scheduling with auto-connect with separate endpoint SIP domain TMS... Global Routing & Management. us.example.com 1) Create meeting on CMS 2) Conference Start. ap.example.com. Regional Call Control CBGroup US CBGroup EU 3) Distributed Conference on global CMS cluster eu.example.com CBGroup AP Conferencing (Global cluster) Americas EMEA APAC SIP API HTTPS / SIP Media EWS 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 44

44 TMS Scheduling with auto-connect with single endpoint SIP domain TMS... Global Routing & Management. example.com 1) Create meeting on CMS 2) Conference Start. example.com. Regional Call Control CMS Cluster Americas CMS Cluster EMEA 3) Conference on regional CMS cluster example.com CMS cluster APAC Conferencing (Regional clusters) IPZONE Americas IPZONE EMEA IPZONE APAC Americas EMEA APAC SIP API HTTPS / SIP Media EWS 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 45

45 Conference Management : CMM 1.x 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 46

46 Update CMS 2.3, CMM 1.0, TMS 15.6, From TMS 15.6 Meeting owner is passed to CMM Note also that Scheduled meeting appear as soon as it is activated, even if no participant has joined yet (handy in white glove environments) CMS 2.3 adds call type (Lync, Space, Forwarded, Ad-hoc) to API GET to /calls for CMM 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 47

47 User case 3 - Ad-hoc conferencing

48 Use Case 2 A large and dynamic worldwide enterprise where employers communicate on the fly and need ad-hoc conference capability Structural requirements (*): Three worldwide regions Redundancy with 2 DC in each region (**) Traffic Optimization Conferencing requirements: Mainly Ad-hoc conference with participant belonging to any region Some rendezvous conferences (*) Structural requirements will be the same in most of the use cases presented (**) More regions or more DCs can be added to the same design 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 49

49 CUCM ad-hoc CMS 2.0+ supports CUCM ad-hoc calls and it can be configured as CUCM Conference Bridge (type is conductor in CUCM 11.x and CMS in CUCM 12.x) Configuration is two steps A SIP trunk (secure or not secure) between CUCM and CMS Conference Bridge - API connection (always secure/https) from CUCM to CMS (*) CA-Signed certificates strongly recommended Recommended to use prefixes (URI uniqueness, troubleshooting, routing) (*) same port as Webadmin 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 50

50 CUCM ad-hoc Conferencing - Architecture Direct trunk from regional CUCM clusters for ad-hoc conference... Global Routing & Management Regional Call Control... Core Core Core Conferencing (CMS cluster) Americas EMEA APAC SIP API HTTPS / SIP Media 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 51

51 CUCM ad-hoc Conferencing Simplified call flow... Global Routing & Management... Regional Call Control Merge conference Core Core Core Conferencing (CMS cluster) Americas EMEA APAC SIP API HTTPS / SIP Media 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 52

52 Use cases with large number of ports but smaller regional footage

53 Single region, large port number use cases 1000 SIP HD ports, no WebRTC or CMA clients 1000 HD ports 500 WebRTC or CMA sessions CMS 2000: - Call-Bridge - Webbridge CMS 2000: - Call-Bridge - Webbridge CMS 2000: - Call-Bridge - Database CMS 2000: - Call-Bridge - Database Spec based VM: - Database (master) XMPP Call Bridge Cluster HTTPS + SIP Database Connect TLS/Postgres Database Cluster TLS / Postgres CMS 1000 (*): - Webbridge - XMPP (**) - Database CMS 1000 (*): - Webbridge - XMPP (**) - Database CMS 1000 (*): - Webbridge - XMPP (**) - Database (*) or spec based VM (**) require server license 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 54

54 Single region, large port number use cases 480 (96x5) WebRTC or CMA HD sessions (*) Optimization via CallBridgeGroup is a must to minimize of distributed calls CMS 1000: - Call-Bridge - Webbridge CMS 1000: - Call-Bridge - Webbridge (*) Note that this is below the 500 XMPP sessions limit CMS 1000: - Call-Bridge - Webbridge - XMPP - Database CMS 1000: - Call-Bridge - Webbridge - XMPP - Database CMS 1000: - Call-Bridge - Webbridge - XMPP - Database Alternatively the same topology can host 480 SIP HD ports, but then it is worthy considering CMS2000 that doesn t waste capacity for distributed legs XMPP Call Bridge Cluster HTTPS + SIP Database Connect TLS/ Postgres Database Cluster TLS / Postgres 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 55

55 Edge WebRTC proxy with Expressway Edge design

56 CMS WebProxy feature in Expressway First step toward the single edge CMS WebProxy feature in Expressway leverages expressway existing capabilities (TURN and MRA Web-Proxy) to facilitate firewall transversal of WebRTC CMS clients On expressway it can coexist with MRA, B2B, Registrar, IMP federation but not with Jabber-Guest or Expressway-MS Interop LIMITATIONS CMA native clients still needs classical CMS edge TURN on TCP port 443 Planned for Expressway X8.11 Load balancing is supported, but no redundancy Expressway TURN for native/cma clients is not yet supported BRKCOL-2986 Kristof Van Coillie ICE / TURN / STUN Tutorial 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 57

57 From legacy CMS Edge to Expressway Web-Proxy CMS EDGE SERVER Expressway-E TURN LOADBALANCER WEBBRIDGE TURN Expressway WebProxy Web-Proxy UC transversal XMPP XMPP CALLBRIDGE WEBBRIDGE CALLBRIDGE WEBBRIDGE UC transversal client CMS CORE SERVER CMS CORE SERVER Expressway-C XMPP HTTPS / WEBRTC Media ; TURN 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 58

58 Expressway proxy for WebRTC Architecture with updated DNS requirements DMZ Internet Expressway-C Expressway-E WebRTC Client Core CMS With WebBridge DNS Internal DNS (split) resolves: 1) (A) meet.mycompany.com to Webbridge IPs 2) (SRV) _cms-web._tls. meet.mydomain to Webbridge FQDNs 3) (SRV) _xmpp-client._tcp.mydomain to XMPP FQDN(s) DNS External DNS (split) resolves (A) meet.mydomain to Expressway-E IP Add WebBridge and Expressway FQDNs in certificate SANs DNS HTTPS / WEBRTC Media/TURN 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 59

59 Web-Proxy Some configuration screenshots Match to Guest Client Account URI in CMS GUI 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 60

60 CMS Edge Design Sizing (*) Maximum number of concurrent XMPP clients per XMPP cluster: 500 (include CMA and WebRTC client, users and guests) Maximum number of concurrent WebRTC sessions per CMS server: 100 WebRTC proxy: Medium Expressway : max 100 media traversal calls per node (B2B or MRA or WebRTC, any combination) Large Expressway Max 500 (**) WebRTC or 500 B2B calls per node (*) Figures referred to expressway dedicated to the service mentioned (**) Figure may be updated in upcoming expressway version X Cisco and/or its affiliates. All rights reserved. Cisco Public 61

61 CMS Edge Design - Sizing TURN server allocation limits: CMS TURN server: max 1000 allocations Medium Expressway: max 1800 TURN allocations Large Expressway: max 6000 TURN allocations (*) Notes : Each CallBridge will use only one TURN server of a certain type (standard or Lync) TURN allocation are requested for every CMA, WebRTC and distributed calls (not on standard SIP calls), TURN allocations are kept for the call duration (as safeguard for network connectivity problems) With audio, video and content streams, each with media and control, 6 allocation are needed per TURN client, so we can size 6 TURN allocations for internal calls, 12 TURN allocation for calls over internet (CMA or WebRTC) (*) 6000 TURN allocation using one port are planned for new expressway release 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 62

62 CMS Edge Design Service Selection A combination of factors influence edge service selection and hence high availability and traffic localization: DNS resolutions RTT calculation Configuration Notes RTT has an important role so administrators have not full control on traffic localization CallBridge Groups feature at edge is not a complete solution but it helps in cleaning up the selection process by reducing the number of choices (e.g. excluding choice like CallBridge in EMEA via TURN in APAC) When more granular control is required, explicit selection of CallBridge can be used in alternative to CBGroup (e.g. TURN in DC1 in US is bound to CB in the same DC) Next slides detail the mechanism and how they can be used for High Availability and Traffic localization 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 63

63 Multiregional architecture with CMS edges For CMA and WebRTC clients (this is the full picture for next slide diagram) Americas EMEA APAC CBGroup Americas CBGroup EMEA CBGroup APAC LB WB LB WB LB WB LB WB LB WB LB WB TU TU TU TU TU TU CB WB CB WB CB WB CB WB CB WB CB WB XM DB XM DB XM DB DC1 DC2 DC1 DC2 DC1 DC2 LB: LoadBalancer WB: WebBridge TU: TURN server CB: CallBridge XM: XMPP server CallBridge Groups include CallBridges, TURN and WebBridge servers 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 64

64 CMA: Service Selection It affects High Availability and Traffic Localization (for full picture see previous slide) (GEO) DNS SRV _xmpp-client Home selection using RTT among Call Bridge direct and CallBridge via TURN (TURN/CB pairs from CBGroups) LB: LoadBalancer WB: WebBridge TU: TURN server CB: CallBridge XM: XMPP server LB WB TU TU WB LB TU LB WB Trunk configuration edge edge edge Trunk configuration -Turn configuration -CallBridgeGroup -RTT WB CB CB WB XM XM CB WB core core core Region1 CallBridgeGroup1 Region2 CallBridgeGroup2 (partially shown) 1) Client selects LoadBalancer (DNS SRV) 2) LoadBalancer selects XMPP server (trunk config) 3) Client selects home CB, CB+TURN (CBGroups, RTT) 4) CallBridges selects TURN (CBGroups, RTT) Selecting entity and criteria Selected Path Alternative selections 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 65

65 Multiregional Architecture with CMS and Expressway WebRTC only Americas EMEA APAC CBGroup Americas CBGroup EMEA CBGroup APAC Xway-E Xway-E Xway-E Xway-E Xway-E Xway-E Xway-C Xway-C Xway-C Xway-C Xway-C Xway-C CB WB CB WB CB WB CB WB CB WB CB WB Core CMS DC1 XM DB Core CMS XM DB Core CMS XM DB Core CMS Core CMS Core CMS DC2 DC1 DC2 DC1 DC2 LB: LoadBalancer WB: WebBridge TU: TURN server CB: CallBridge XM: XMPP server CallBridge Groups include CallBridges and TURN servers in Expressway 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 66

66 WebRTC proxy via Expressway: Service Selection It affects High Availability and Traffic Localization (GEO) DNS A meet.mydomain + Xway cookie LB: LoadBalancer WB: WebBridge TU: TURN server CB: CallBridge XM: XMPP server Xway Clusters Transversal Configuration Xway-C Xway-E TURN Xway-E TURN Xway-C (GEO) DNS SRV _cms-web._tls -Turn configuration -CallBridgeGroup -RTTs Home selection using RTT among Call Bridge direct and CallBridge via TURN (TURN/CB pairs from CBGroups) WB CB CB WB XM XM XM WB core Region1 CallBridgeGroup1 core Region2 CallBridgeGroup2 (partially shown) 1) WebBridge (and CB) has selected XMPP (DNS SRV) 2) Client selects Expressway-E (DNS A) 3) Expressway Transversal (transversal) 4) Xway-C selects WebBridge (DNS SRV) 5) WebBridge selects CallBridge/TURN (CBGroups, RTT) 6) CallBridges selects TURN (CBGroups, RTT) DNR SRV Selecting entity and criteria Selected Path Alternative Selections 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 67

67 Multiregional Architecture with CMS and Expressway With limitation of cross DC traffic to DMZ Americas EMEA APAC Special use case Xway-E Xway-E Xway-E Xway-E Xway-E Xway-E Xway-C Xway-C Xway-C Xway-C Xway-C Xway-C CB WB CB WB CB WB CB WB CB WB CB WB Core CMS XM DB Core CMS Core CMS Core CMS Core CMS DC1 DC2 DC1 DC2 DC1 DC2 CBGroup Americas CBGroup EMEA CBGroup APAC LB: LoadBalancer WB: WebBridge TU: TURN server CB: CallBridge XM: XMPP server XM TURN servers are directly mapped to callbridge in same DC, Expressways are not clustered between DCs, Expressway-C use the regional WebBridges (GEO DNS) CallBridge Groups include CallBridges only DB Core CMS XM DB 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 68

68 Load-balancing of CMA native and WebRTC calls New in CMS 2.3, this complements the load-balance feature suite The same mechanism to avoid distributed call inside a CallBridgeGroup is available for client calls CMA and WebRTC on CMS 2.3 Inside a CallBridgeGroup, CMA calls to the same meeting will not be distributed and they will happen on one CallBridge (as long as it has capacity left) Configuration steps: 1. Add a CallBridgeGroup and place the CallBridge in the group 2. In the CallBridgeGroup configure (with API) loadbalanceusercalls (in addition to loadbalancingenabled for SIP call load balance) 3. Ensure that each Call Bridge in the Call Bridge Group has a connection to the XMPP cluster or single XMPP server Log messages are similar to a normal load-balanced call 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 69

69 For reference Summary of LoadBalance CallBridgeGroups parameters /callbridgegroup API parameter Usage loadbalancingenabled = true loadbalanceoutgoingcalls = true loadbalanceusercalls = true Use to LoadBalance SIP calls to spaces and to minimize distributed call between CallBridges in the same CallBridge Group Use to optimally allocate outgoing calls to CallBridges or CallBridgeGroups Use to optimally allocate user calls (webrtc and CMA) to CallBridges or CallBridgeGroups loadbalancelynccalls = false About loadbalancing lync/s4b calls to Spaces Keep it as false, as it is not supported 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 70

70 WebRTC and Meeting Apps new look and features New in CMS 2.3 and CMA 1.10 Lock meetings, make participant important, mute audio or video, drop "Activity" "People" and "Spaces" are replaced with "Recent activity" and "Meet" Multiple way of join management and presentation : manage the meeting, see only audio and presentation use this computer nearby endpoint: use video endpoint via proximity use my video endpoint: use video endpoint via SIP use my phone BRKCOL-2803 Abhijit Dey Designing and deploying multiparty conferencing for telepresence video 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 71

71 On-Premises MS Interoperability

72 MS-Interoperability with CMS Key features Native capability of CallBridge Interoperability with most of Lync/S4B versions and video protocols (SVC, H.264UC, RTVideo ) On-premises or cloud Large scale Bidirectional content sharing Drag &Drop video participant Lync buddy list integration Presence information and in meeting IM Native user experience with Dual Home BRKCOL-2610 Tobias Neumann Cisco Interoperability with Microsoft - Part 1, Collaboration BRKCOL-2611 Fabio Chiesa Cisco Interoperability with Microsoft - Part 2, Video Interoperability 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 73

73 Skype for Business Integration call types Gateway : call goes across CMS for adaptation and transcoding Rendezvous : Video and Lync Endpoints meet in a CMS space Dual Homed conferencing Video endpoint joins a Lync/S4B meeting via CMS as a native participants Video EP Dial IVR+ConferenceID CMS Join Lync Conference Click-To-Join 5 media streams LYNC SERVER AVMCU 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 74

74 Call types: Call start and user experience comparison Call method CMS call type End user experience video side End user experience MS side Direct point to point call Gateway Good Good Endpoints and Video Clients meet into a CMS space -Dial Lync meeting via IVR -Drag and drop Video EPs into a Lync conference Rendezvous Good Better layouts; missing participant roster and controls Dual homed Good Lync layouts, roster and limited controls 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 75

75 Video endpoint user experience When joining a Lync/S4B (dual homed) scheduled meeting Option1: Meeting invitation with additional info about how to join Lync/S4B meeting from Video Endpoint [Modification of Lync invitation form] Option 2: One Button to Push on endpoints [TMS/TMSXE integration with MS-Exchange] 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 76

76 For reference Comparison of TMS scheduling with CMS and OBTP without Lync participants With Lync participant on-prem User add Lync Meeting in invitation No Yes In outlook invitation, TMSXE service user will look at Rooms only Rooms and Lync conference ID CMS Query for Lync Conference_ID No SIP SERVICE message to resolve lync conference Book CMS scheduled spaces Yes No OBTP content MS_Domain> <Lync_Domain> CMS meeting type Rendez-vous Dual homed 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 77

77 Dual homed call setup via IVR (*) Lync client Client creates a Lync Meeting MS Front End & AVMCU Call Bridge Video EP For reference invite with Lync Meeting ID: Lync clients join meeting SIP: INVITE IVR Type meeting ID " " from invitation Lync resolution for " " SIP: SERVICE sip:fep-fqdn.<resolveconference> <pstn-meeting-id> SIP: OK <msci:conference-id>3bg9g902 INVITE sip:lyncuser@lyncdomain...:conf:focus:id:3bg9g902 Lync conference join Lync conference subscription SIP: SUBSCRIBE sip:lyncuser@lyncdomain.. 3BG9G902 SIP: OK with Conference information. (*) simplified All participant in a dual homed meeting Media SIP 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 78

78 Use Case 4 Customer is a Large Enterprise with Cisco UC + Video and on-premises Lync/S4B requiring full featured integration between the two worlds Structural requirements (*): Conferencing requirements: Three worldwide regions (**) Redundancy with 2 Data Centres (DC) in each region (**) Traffic Optimization (localize the traffic to regions whenever possible) Point to point call between Video EP and Lync/S4B clients Lync/S4B clients able to join Spaces on CMS (rendezvous) Video Endpoints able to join Lync meetings via OBTP and via IVR with full features (dual homed) This is an extension of use case 1; configuration is additive to the one in use case 1 (*) Structural requirements will be the same in most of the use cases presented (**) More regions or more DCs can be added to the same design 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 79

79 Use case 4 : Architecture. Calendar. TMS & TMSXE. Global Routing & Management... Regional Call Control Conferencing CMS cluster MS Lync/S4B Front End Pool +Infra Front End Pool +Infra Front End Pool +Infra Americas SIP HTTPS / SIP EMEA (MS) SIP APAC (*) DB server not shown for simplicity 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 80

80 LDAP integration : User and Space names The simple solution is to use a different domain for CUCM, CMS and Lync/S4B SIP domains URIs CUCM ucdomain.com user@ucdomain.com Lync/S4B lyncdomain.com user@lyncdomain.com CMS Spaces meet.ucdomain.com user.space@meet.ucdomain.com CMS users: user@meet.ucdomain.com This ensure that user and space URIs do not overlap with Lync/S4B URI 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 81

81 Use case 4 : Traffic optimization (localization) Traffic. from call Bridge to Lync is kept local by using CallBridge specific outbound dial rules.. Traffic from local EPs to Lync domain is kept local by CUCM DialPlan(*) Global Routing & Management. Traffic from call Bridge to CUCM is kept local by using CallBridge Regional specific outbound dial rules Call Control. Conferencing CMS cluster Traffic from Lync to CallBridge is kept local by FEP specific static routes MS Lync/S4B Americas SIP HTTPS / SIP (MS) SIP EMEA APAC (*) interregional secondary path is possible but pay attention to call loop 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 82

82 CMS configuration details Focus on Lync related configuration of one region: (*) SIP Domains CUCM ucdomain.com CMS Lync meet.ucdomain.com lyncdomain.com CMS Dial Plan: EMEA Outbound dial rules for Lync (CUCM rules omitted) Domain SIP proxy to use Local contact domain ucdomain.com meet.ucdomain.com Call Bridge specific outbound dial rule (API), same priority Local from domain Trunk type lyncdomain.com EMEA_CBGroup EMEA_CB1 EMEA_CB2 EMEA_FEP Behavior Priority Encryption For reference CallBridge Scope lyncdomain.com EMEA_FEP_fqdn EMEA_CB1_fqdn ucdomain.com Lync Continue 10 Encrypted EMEA_CB1 lyncdomain.com EMEA_FEP_fqdn EMEA_CB2_fqdn ucdomain.com Lync Continue 10 Encrypted EMEA_CB2 CMS Dial Plan: (additional) Inbound dial rules for Lync Domain name Priority Targets spaces Targets users Targets IVRs lyncdomain.com 20 No No No Yes CMS FQDN(s) 10 Yes Yes Yes Yes Targets Lync CMS Dial Plan: Forward dial rules Forward both ucdomain.com and lyncdomain.com with no changes Direct numeric call from CUCM to Lync Meeting (optional (*) to be added 2018 Cisco to and/or configuration its affiliates. All rights for reserved. use Cisco case Public1 83

83 Lync configuration details Focus on one region: EMEA SIP Domains CUCM ucdomain.com CMS Lync meet.ucdomain.com lyncdomain.com EMEA shared CMS Certificate CN: EMEA_CBGroup_fqdn SAN: EMEA_CB1_fqdn, EMEA_CB2_fqdn For reference ucdomain.com EMEA_CBGroup EMEA_CB1 EMEA_CB2 meet.ucdomain.com lyncdomain.com EMEA_FEP New-CsTrustedApplicationPool -Identity EMEA_CBGroup_fqdn -ComputerFqdn EMEA_CB1_fqdn -Registrar EMEA_FEP_fqdn -site 1 - RequiresReplication $false -ThrottleAsServer $true -TreatAsAuthenticated $true FEP specific application pool New-CsTrustedApplicationComputer Identity EMEA_CB2_fqdn Pool EMEA_CBGroup_fqdn New-CsTrustedApplication -ApplicationId EMEA-CMS-Group -TrustedApplicationPoolFqdn EMEA_CBGroup_fqdn -Port 5061 $Route1 = New-CsStaticRoute -TLSRoute -Destination EMEA_CBGroup_fqdn -MatchUri ucdomain.com -Port UseDefaultCertificate $true Set-CsStaticRoutingConfiguration -Identity Service:Registrar:EMEA_FEP_ID $Route2 = New-CsStaticRoute -TLSRoute -Destination EMEA_CBGroup_fqdn -MatchUri meet.ucdomain.com -Port UseDefaultCertificate $true Set-CsStaticRoutingConfiguration -Identity Service:Registrar:EMEA_FEP_ID 1. EMEA_FEP_ID from Get-CsStaticRoutingConfiguration 2. Moving from routing global to FEP specific requires full re-config!! FEP specific static routes 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 84

84 CMS 2.3 S4B meeting optimization: dualhomecluster mode default and pre-2.3 behaviour (MS) SIP SIP Audio/Video XMPP HTTPS / SIP Media Lync proxy leg Lync proxy leg Distributed call leg dualhomecluster (*): Behaviour as in previous versions. Conferences on callbridges have distribution and Lync proxy calls between them. All calls to S4B meeting from one callbridge. CMS participants video mixed by CMS. Use this mode when a single cascading point per S4B dual homed conference is preferable (*) lyncconferencemode in /callprofiles/ SIP HTTPS / SIP 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 85

85 CMS 2.3 S4B meeting optimization: dualhomecallbridge mode No distribution between callbridges (MS) SIP SIP Audio/Video XMPP HTTPS / SIP Media Lync proxy leg Conference & Participants info Audio/Video dualhomecallbridge: No distribution between callbridges. Separate conference on every callbridge, each with calls out to S4B meeting. A/V mixed by S4B AVMCU. Use this mode when a independent cascading points to S4B conference on each CMS are preferred A typical use is when conference participants are mostly belonging to the same region and you want to avoid that when the conference is opened by a participant in the region with few participants, traffic is anchored on this region CMS and then clearly suboptimal SIP HTTPS / SIP 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 86

86 CMS 2.3 S4B meeting optimization: gateway mode CMS creates legs for each endpoint (MS) SIP SIP Audio/Video XMPP HTTPS / SIP Media Lync proxy leg Conference & Participants info Audio/Video gateway: No distribution between callbridges. Each SIP participant in its own conference with associated calls out to S4B meeting. A/V mixed by S4B AVMCU. Use this mode when separate and independent gateway call legs for each endpoint are needed with the purpose of giving the full control of the meeting to the S4B AVMCU (note that this is still a dual homed call because S4B meeting need to be resolved) SIP HTTPS / SIP 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 87

87 MS interoperability off-premises

88 MS interop off-premises - Use Case 5 Customer is a Large Enterprise with Cisco UC and without on-prem MS infrastructure requiring integration and federation with external organizations using MS and standard SIP Structural requirements : Conferencing requirements: Three worldwide regions Redundancy with 2 Data Centres (DC) in each region Traffic Optimization Video calls with external organizations using standard SIP Video calls with external organizations with own MS infrastructure or using O365 Join meetings (spaces) hosted on this organization CMS cluster with any client TECCOL-2225 Davide Preti, Fabio Chiesa Cisco Collaboration and Microsoft Skype for Business - Best Practices for a successful coexistence and migration BRKCOL-2986 Kristof Van Coillie ICE / TURN / STUN Tutorial 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 89

89 CMS with Expressway Edge: Basic Architecture Expressway advanced search rule filtering options : any part of URI,SIP variant, SIP content (AV/Share or IM&P) All traffic that needs smart SIP analysis will be sent to expressway When required, Expressway hairpins the call leg to CMS for the adaptation and transcoding for MS-interop 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 90

90 Points of attention and limitations Points of attention and limitations Expressway do not support yet load balance with CMS (callbridgegroup) Hair-pinning traffic to CMS from Expressway require a relatively complex dial plan Because of that for large deployments, it is simpler to have one separate adaptation CMS per region separate from the interregional MS cluster 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 91

91 Use case 5 : Architecture Regional Call control Global Routing Global Conferencing with core CMS cluster Edge with adaptation CMS External Users Other SIP domains Americas Organization with MS infrastructure O365 Clients EMEA B2B standard SIP APAC SIP HTTPS / WebRTC (MS) SIP 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 92

92 O365 OBTP Dual Homed experience Office 365 users join skype meeting (o365 cloud same organization) from Video Endpoints with OBTP and with Dual Homed Experience Prerequisites: CMS 2.2, TMS 15.5, TMSXE 5.5, X Operation (see next slide) : TMSXE monitors the room mailboxes When it sees a meeting it gets the skype alphanumeric URL value fetched from MAPI property TMSXE appends the cisco meeting server domain name (a sort of dummy/routing domain) TMS saves the appointment in TMS as Externally Hosted conference (no resource local reserved) When meeting start and OBTP is pressed, CMS resolves the Lync Simple Meet URL (requires both connectivity to internet and permission to resolve) Then CMS sends an INVITE to join the resolved meeting BRKCOL-2986 Kristof Van Coillie ICE / TURN / STUN Tutorial 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 93

93 O365 OBTP Dual Homed experience O365 client TMS/TMSXE Video EP CMS Expressway-C Expressway-E O365 client books a meeting adding room participants Fetch meeting info, including join Lync URL Program OBTP with INVITE https Resolve Simple URI Meeting URI and id INVITE user@lyncdomain;gruu;...:id:<lync MeetingID> ICE Negotiation MS SIP SIP EP API HTTPS / EWS ICE Media 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 94

94 O365 OBTP Dual Homed: Configuration screenshots (*) TMSXE: Define CMS domain + Skype support for Multiple Domains CMS: Define CMS domain + Target Lync SimpleJoin ExpresswayC: call hairpinning to and from CMS for SIP MS variant adaptation + reach O365 via transversal (*) SIP domains used in the example sthlab.onmicrosoft.com : 0365 Meet.lync.com : CMS domain for 0365 OBTP sthlab.net : CUCM 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 95

95 O365 OBTP Dual Homed: Some operational screenshots Lync/Touch: See combined participant list.but controls affect only one side TMS: Meeting confirmation EP: OBTP with Simple URI B2B SIP Microsoft AV calls to O365 on Expressway C and E 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 96

96 For reference Comparison of TMS scheduling with CMS and OBTP without Lync participants Lync on-prem O365 Dual homed experience User add Lync Meeting in invitation In outlook invitation, TMSXE service user will look at No Yes Yes Rooms only Rooms and Lync Conference ID Rooms and Conference URL CMS Query for Lync Conference_ID No SIP SERVICE message to resolve lync conference https conference resolution Book CMS scheduled spaces Yes No No OBTP content <CMS_Domain> <Lync_Domain> <CMS_Domain_for_interop> CMS meeting type Rendez-vous Dual homed Dual homed experience 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 97

97 Hybrid Conferencing How apply large scale design principles to cloud/hybrid conferencing

98 Hybrid Media Node Highlights HMN is an on-prem extension of the Webex/Spark cloud Runs on CMS-1000 (or MM410v or spec based VM) Improve media quality by reducing latency and bandwidth consumption Automatic overflow. Controllable automatic upgrade In Phase II, HMN supports spark clients, spark rooms and SIP video endpoints Management via the spark admin with resource monitoring and usage metrics HMN can be installed in core or in DMZ It requires minimal number of Firewall ports to be opened BRKCOL-2607 Louis Pratt BRKCOL-1120 Richard Murphy BRKCOL-2202 Luca Pellegrini BRKCOL-2030 Anthony Mulchrone Understanding Cloud and Hybrid Cloud Collaboration Deployment Cisco Spark Hybrid Media Node Cisco Spark Hybrid Call Services Architecture and Design Cisco Spark - Cloud and On Premise Security explained 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 99

99 Conferencing Architecture with Hybrid Media Node in core PSTN CUCM Expway-C Expway-E Overflow Traffic Webex client WebEx/Spark SIP Video Endpoints Spark Clients HMN Spark Video Endpoints Webex clients B2B partner Media Signaling SIP HTTPS REST/API Webex session Other Signaling/media Audio Video HMN Video 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 100

100 Conferencing Architecture with Hybrid Media Node in DMZ PSTN CUCM Expway-C Expway-E Overflow Traffic Webex client WebEx/Spark SIP Video Endpoints Spark Clients HMN Spark Video Endpoints Webex clients Media Signaling SIP B2B partner 900 WX media HTTPS WX session 9000 udp REST/API Signaling 443 tcp Audio Video HMN Video 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 101

101 Use case 5 : Hybrid Conferencing with large hub site Large Enterprise with Cisco UC and video looking for cloud web conferencing Structural requirements : Large hub site with two DC Redundancy Maximize Local (on-premises) Media Termination Traffic Optimization Conferencing requirements: Webex Meetings Personal Meeting Rooms Scheduled Meetings 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 102

102 Design Notes HMN placed in core Local media stays in core Minimal number of port opened on internal firewall Avoid traffic between DMZs in different DCs (caused by HMN inter-cluster signalling and media) HMN placed in DMZ Security policies may prefer this: the extension of the cloud devices is confined to DMZ 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 103

103 Use case 5 Architecture with Hybrid Media Node in core Minimization of ports to be opened on internal FW and of traffic between DMZs in different DCs DC 1 SIP Video Endpoints CUCM Expway-C Expway-E (*) Spark Clients HMN Cluster HMNs WebEx/Spark Spark Video Endpoints DC 2 WX clients HMNs CUCM Expway-C Expway-E (*) (*) Expressways are clustered inside a DCs, not between DCs Media Signaling SIP HTTPS REST/API Webex session Other Signaling/media Audio Video HMN Video 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 104

104 Use case 5 Architecture with Hybrid Media Node in DMZs The extension of the cloud device (HMN) is confined to DMZ but more inter-dmz traffics and more opened ports on internal FW DC 1 Expway-C (*) Expway-E (*) SIP Video Endpoints CUCM Spark Clients WebEx/Spark Spark Video Endpoints DC 2 WX clients HMN Cluster CUCM Expway-C (*) Expway-E (*) (*) also Expressways are clustered between DCs Media Signaling SIP HTTPS REST/API Webex session Expway Other Signaling/media Cluster Video HMN Video 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 105

105 Design Notes CUCM SIP trunk(s) to HMN Cloud allocates HMN within cluster (CUCM is informed by SDP) => HMNs in same cluster can be assigned to same CUCM SIP trunk (One trunk with multiple HMN IPs for each HMN cluster) CUCM Route Groups/Lists are needed for 1. Traffic overflow via Expressway (route advance on SIP error 488) 2. Routing to multiple HMN clusters 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 106

106 Cloud Allocation of HMN within HMN cluster How CUCM is informed about the HMN to use Video Endpoint CUCM HMN 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 107

107 Cloud Allocation of HMN within HMN cluster There is not much benefit in leveraging CUCM route advance within an HMN cluster Video Endpoint CUCM HMN1 HMN Cisco and/or its affiliates. All rights reserved. Cisco Public 108

108 Design Notes Bandwidth utilization Device Behavior Typical bandwidth with 720p resolution HMN (on-prem and cloud) Spark devices (rooms and clients) SIP Video Endpoints Switch media whenever possible Transcode media when required Receive multiple streams with participants to compose in local layout Receive pre-composed stream with layout (traditionally coming from a transcoding video bridge) Send up to 6 streams between HMNs including roster participants using original participant stream resolution 1 Mbps to 2.5 Mbps 1 Mbps to 2.5 Mbps Webex Client Receive multiple streams with participants to compose in local layout ; only main participant is at full resolution Up to 2Mbps BRKCOL-1120 Richard Murphy Cisco Spark Hybrid Media Node 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 109

109 Design Notes Bandwidth utilization - Examples SIP + Webex clients (average bandwidths) Webex client (on cloud) 2 Mbps 2 Mbps (max) SIP Video Endpoints WebEx/Spark SIP Video Endpoints HMN SIP Video Endpoints SIP Video Endpoints Webex clients (on prem) Webex session media Audio Video HMN Video (*) Two participant streams but only one sent with 720p 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 110

110 Design Notes Bandwidth utilization - Examples SIP + Webex + Spark clients Webex client (on cloud) 2 Mbps 2 Mbps SIP Video Endpoints WebEx/Spark SIP Video Endpoints HMN SIP Video Endpoints Spark Video Endpoints Webex clients (on prem) B2B partner Spark Video Endpoints Webex session media Audio Video HMN Video (*) 4 participant streams but only 3 with 720p 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 111

111 Design Notes Bandwidth utilization - Examples Attention to unbalanced conferences 6 streams vs. 1 stream Remote Video Endpoint 1 stream Remote Video Endpoint 1 stream Webex session media Audio Video HMN Video 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 114

112 Use case 6 : Hybrid Conferencing with multiple regions Large Enterprise with Cisco UC and video looking to migrate from a legacy conferencing infrastructure to cloud web conferencing Structural requirements : Three worldwide regions Redundancy with 2 DC in each region Maximize Local (on-premises) Media Termination Traffic Optimization Conferencing requirements: Webex Meetings Personal Meeting Rooms Scheduled Meetings Only SIP Endpoints and Webex clients 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 115

113 Additional Design Notes CUCM SIP trunk(s) to HMN CUCM trunks to different HMN regional clusters need be separate HMN traffic HMN intra-cluster traffic stays within enterprise network HMN inter-cluster traffic use cloud HMN selection (SIP devices) HMN cluster used for the call is chosen by CUCM HMN server inside a cluster is chosen by the cloud based on HMN inputs (latency, load) HMN selection (Spark clients/rooms) HMN is chosen by cloud based on reachability info provided by client (STUN RTT) with preference for onpremises HMN 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 116

114 Additional Design Notes Want to keep media on-premises Do not close port 5004, this will cause split meetings!! Traffic via cloud can be reduced but not avoided, the following traffic types go anyway via cloud Spark/HMN signaling Webex signalling and media HMN Inter-cluster signalling and media Approach to limit HMN inter-cluster traffic for SIP devices: CUCM Time Of Day Routing 1. Prefer a regional HMN cluster at a certain time of the day, 2. with alternate route to the other HMN regional clusters for High Availability and Overflow 3. and to cloud via Expressway for overflow TOD time switch should avoid meeting start time :00, :30 (:45 may be a good choice) Limitations Spark clients and rooms (not covered by this use case) do not follow CUCM allocation. Strategy applies only to dial in to Webex/HMN Future HMN dial out feature may not fit this approach 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 117

115 Use case 6 : Architecture Endpoint SIP Call control On premises Hybrid conferencing layer Regional Edges Webex/Spark cloud During US business hours 1) HMN cluster Americas 2) HMN cluster EMEA, APAC 3) Overflow to cloud via US Expressway HMN cluster Americas Americas During EMEA business hours 1) HMN cluster EMEA 2) HMN cluster Americas, APAC 3) Overflow to cloud via EMEA Expressway HMN cluster EMEA EMEA WebEx/Spark During APAC business hours 1) HMN cluster APAC 2) HMN cluster Americas, EMEA 3) Overflow to cloud via APAC Expressway HMN cluster APAC APAC 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 118

116 Conclusions When planning a large conferencing infrastructure, you cannot count on magic. Good planning and design enables a seamless and robust deployment.

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

118 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 Cisco and/or its affiliates. All rights reserved. Cisco Public

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

120 Thank you

121

122 BACKUP SLIDES

123 Cisco Advanced Services

124 Cisco Advanced Services Portfolio Advise Services Develop a strategy to align your people, process, and technology Assess your network, infrastructure, security, and readiness for change Design sustainable architectures and tech-enabled business processes ADVISE IMPLEMENT Implement Services Integrate new solutions with existing technology Migrate from your current state to future-state solution Validate that the solution meets your business and technical needs Optimize Services OPTIMIZE Recommend best practices for maintaining your solutions Remediate solution-related issues Analyze solution value and recommend adjustments or improvements 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 127

125 Cisco Meeting Server Services Advise and Implement Highly scalable video and audio conferencing design Interoperability with Microsoft Lync/Skype for Business and WebRTC Extensible to new user video experiences and business interactions Migration from legacy MCUs and/or TelePresence Servers Flexible, global on premise deployment model Cisco MCU Migrate Cisco TelePresence Server Optimize Ongoing capability, functionality, and capacity evolution Escalation support for critical or service impacting incidents/ problems Security alerts and risk mitigation Enterprise wide change management and architectural integrity Knowledge transfer - architecture and design changes, migration testing Interoperate Cisco Meeting Server Other relevant AS value added services are available: NPA, MNRA, Adoption. Please contact AS Global BDM team for Advanced Services scoping & quotes Cisco and/or its affiliates. All rights reserved. Cisco Public 128

126 Value Added Services Customer Issues When installing Cisco Meeting Servers in new data centers When installing Cisco Meeting Servers that have more capacity than the existing MCUs / TelePresence Servers New video customers deploying video bridges for the first time Migration from third party video bridges / services (on-premises or cloud) Customer environment has known video quality issues Proposed AS Value Added Services Network Path Assessment (NPA) -- or Media Network Readiness Assessment (MNRA) Customer's needing assistance with an end-user communication plan Customer's needing assistance with educating end-users on any experience changes after the deployment Adoption Services * Contact AS Global BDM team to determine which service is appropriate 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 129

127 CMS configuration quick start

128 Configuration quick start - basic For reference Configure IP ipv4 a add <CMS_IP>/<mask> <def_gw> Hostname <CMS_name> 2 nd admin and an API user user add admin2 admin user add apiuser api Ntp server Ntp server add <NTP_IP> Timezone <timezone> DNS add and verify Dns add forwardzone <DNS_IP> Dns lookup a <address to lookup> Dns lookup SRV _xmpp-client._tcp.xxx Certificate command (transfer with sftp) Pki list Pki match <key> <cert> Pki inspect <cert> License (transfer with sftp file cms.lic) License Webadmin Webadmin listen a 8443 Webadmin certs <key> <cert> <rootbundle> Webadmin enable CallBridge callbridge listen a callbridge certs <key> <cert> <rootbundle> callbridge restart 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 131

129 Configuration quick start - Spaces Add IVR GUI->configuration->General For reference Add static Rendezvous meeting GUI->configuration->Spaces Active Directory (example) Base DN :OU=Training,DC=EXAMPLE,DC=com FILTER: (&(objectcategory=person)(objectclass=user)(!(cn=administrator))(!(cn=guest))(!(cn=krbtgt))) Display name: $cn$ Username: $samaccountname$@meet.example.com Space Name $samaccountname$.space Space URI $samaccountname$.space Secondary Space URI 15$telephoneNumber$ 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 132

130 Configuration quick start XMPP & WebBridge XMPP xmpp listen a xmpp certs <key> <cert> <rootbundle> xmpp domain meet.example.com xmpp enable Add callbridges (CLI on xmpp server) xmpp callbridge add core1 xmpp callbridge add core2 Xmpp callbridge list Connect CallBridge to XMPP (GUI or API) Webbridge Webbridge listen a Webbridge certs <key> <cert> <rootbundle> Webbridge trust <callbridge_cert> Webbridge enable Webbridge Web GUI config (or API) For reference CMS Dial Plan see core section 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 133

131 Core

132 For reference CMS cluster operation during outages If connection to DB is lost, operation stop or it is severely degraded Operation Status Condition Features available READ/WRITE READ-ONLY NO OPERATION POSSIBLE All read and write queries are always directed to current DB Master, wherever it is. It is not possible to perform any WRITE operation to a database which is not elected as current Master. If CallBridge server has local, collocated database, it can only read from local database when Master DB is not accessible. If CallBridge is a standalone - no local database on the same server, it can't do read access to any node except the Master DB. CallBridge is fully featured inbound/forwarding/outgoing calls possible, TMS scheduled conferences will not work, dual home conferencing may not work CallBridge death, only outgoing calls may work 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 135

133 Distributed call Setup For reference Enpoint1 CUCM1 Call Bridge CB1 Call Bridge Cluster Call Bridge CB2 CUCM2 Enpoint2 DB: MySpace1 SIP: INVITE MySpace1 SIP: INVITE MySpace1 First call established SIP: INVITE MySpace1 Intra-cluster dialogue finds that the space is already active in in CB1 CB1: generating peer URI for cospace <spaceid> SIP HTTPS / SIP Media Distributed Video Call established CB2: call <Call ID> now peered with conference on server CB1 (peer URI Conf_ID@CB1) SIP: INVITE Conf_ID@CB Cisco and/or its affiliates. All rights reserved. Cisco Public 136

134 Call Replacement (simplified flow) For reference CUCM Call Bridge CB1 Call Bridge group EMEA Call Bridge CB2 SIP: INVITE MySpace1 Space MySpace1 SIP: INVITE MySpace1 with Call_ID Supported:.. Replace Video EP with existing call to MySpace1 on CB2 replace query for conference YYY using server CB2 (priority: 0, load level: 0, conference is running: 1) replacing call Call_ID to conference YYY on server CB2 replacing call Call_ID from server CB1 into conference YYY SIP: INVITE EndpointURI From spaceuri Replaces: Call_ID SIP HTTPS / SIP SIP: INVITE EndpointURI SIP: CANCEL Call_ID Video Call established on CB2 only Media 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 137

135 LDAP integration : things to watch AD mapping creates 3 dial-able URIs in CMS : Primary and Secondary Space URI and User URI => None of them should overlap with other URI in the network Dual mapping with alphanumeric and numeric URI for spaces provides a flexible way to join spaces Sizing : If more than users need to be imported from AD, the design should be validated by Cisco There is a lot of flexibility in configuring LDAP Multiple LDAP sources and mapping can be configured LDAP configuration on CallBridge is per server when configured using GUI All CallBridges in a cluster can update users and space database For a clustered environment, it is best to configure LDAP integration using API But case should be take to to avoid feeding CMS with incongruent information 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 138

136 For reference CMS 2.2 Load balancing of outbound SIP calls Operation: When CMS receive an API request to make an outbound call, it finds the highest priority outbound dial plan rule that matches the SIP domain, if this applies to a local Call Bridge, then balance the call within the local Call Bridge Group. if this only applies to remote Call Bridges, then load balance the call within the Call Bridge Group to which the Call Bridge is a member As a consequence, traffic can be optimized as long as video endpoints belong to different regional SIP domains 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 139

137 Recording and Streaming

138 Recording and streaming basic architecture RECORDING xmpp client CallBridge + XMPP server Recorder NFS/mp4 NFS server Video Management Server Viewing Clients STREAMING xmpp client RTMP/H264 CallBridge + XMPP server Streamer Streaming Server Streaming Clients Third party BRKCOL-2544 Terry French Enterprise Webcasting and Recording Architecture with VBrick Rev XMPP Media Media (NFS) Media (RTMP) 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 141

139 Sizing Virtual Machine Recording and Streaming needs separate VM with minimum 4 vcpus Streaming: 1 vcpu and 1GB of memory per 6 concurrent streams (max 6 VM) Recording: 1 vcpu and 0.5GB of memory per concurrent recording (max 8 VM) Network Stream media is H264 at 720p30 (2Mbps) Disk The size of 720p30 recordings ranges from 300MB to 800MB for 1 hour Presentation is captured in the main recording stream, not separately 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 142

140 Scaling Streaming and Recording Call Bridge Groups allow optimal allocation of resources 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 143

141 Edge WebRTC proxy with Expressway Edge design

142 CMA Sign-in and Join a space (simplified) For reference CMA client LoadBalancer XMPP Server TURN CallBridge(s) DNS DNS SRV lookup _xmpp-client._tcp.mydomain Sign-in + userid, password CMA Client: Evaluate RTT among CB and CB via TURN, Choose CB list of CB and CB via TURN Validate credential AD Welcome CMA Screen Join Space Call Request Answer Port Allocation Request[UDP 3478] Answer with TURN address and port to use Port Allocation Request[UDP 3478 or TCP 443] UDP or TCP UDP DNS XMPP HTTPS / WEBRTC Media/TURN 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 145

143 WebRTC Sign-in and Join a space (simplified) For reference Web client DNS WebBridge XMPP via LoadBalancer TURN CallBridge DNS A lookup meet.mydomain Sign-in + userid, password DNS SRV lookup _xmpp-client._tcp.mydomain Authenticate list of CB and CB via TURN Validate credential AD WB:Evaluate RTT among CB and CB via TURN, Choose CB Welcome CMA Screen Join Space Answer Call Request Port Allocation Request[UDP 3478] Answer with TURN address and port to use Port Allocation Request[UDP 3478 or TCP 443] UDP or TCP UDP DNS XMPP HTTPS / WEBRTC Media/TURN 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 146

144 WebRTC Guest joins a Space (simplified) For reference Web client DNS WebBridge XMPP via LoadBalancer TURN CallBridge DNS A lookup meet.mydomain Join a meeting + Meeting_ID & passwd DNS SRV lookup _xmpp-client._tcp.domain Validate Meeting_ID & passwd Enter Name + Join Request guest credentials Authenticate Validate credentials TBV list of CB and CB via TURN TBV WB Evaluate RTT among CB and CB via TURN, Choose CB, Call Request Answer Port Allocation Request[UDP 3478] Answer with TURN address and port to use Port Allocation Request[UDP 3478 or TCP 443] UDP or TCP UDP DNS XMPP HTTPS / WEBRTC Media/TURN 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 147

145 CMA: Traffic Localization and High Availability Tools For reference Selecting entity Service / Server Section method Localization High Availability Client LoadBalancer DNS SRV GEO DNS Multiple LB SRV records and/or smart DNS Load Balancer XMPPserver Trunks configuration Local Trunk Multiple trunks from LoadBalancer to XMPP servers CMA client (via XMPPserver) CallBridge (CB) CMA Client estimation RTT among CB and CB via TURN ( sticky result, selected CB will be homecb ) CallBridge (CB) TURN Server CB RTT estimation + CallBridgeGroup CMA Client TURN server at CMA client side TURN protocol and port at CMA client side Received by CB after CB turn allocation Try fist UDP.3478, then TCP TURN according to CBgroups - RTT favours regional servers RTT and CBgroup (same as above) Decided in previous step Decided in previous step Multiple CallBridges Multiple TURN choices per CB Multiple TURN servers Multiple TURN servers 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 148

146 WebRTC: Traffic Localization and High Availability Tools Selecting entity Service / Server Section method Localization High Availability Client WebBridge (WB) DNS A (need that client sticks with one WebBridge IP) GEO DNS Multiple WB A records and/or smart DNS WebBridge LoadBalancer DNS SRV GEO DNS Multiple SRV records and/or smart DNS Load Balancer XMPPserver Trunks configuration Local Trunk Multiple trunks from LoadBalancer to XMPP servers WebBridge (via XMPPserver) CallBridge (CB) WebBridge estimation RTT among CB and CB+TURN (TBVerified) ( sticky result -> home CB ) - TURN according to CBgroups - RTT favour regional servers Multiple CallBridges WebBridge XMPP server DNS SRV record GEO DNS XMPP clustering For reference CallBridge (CB) TURN Server CB RTT estimation + CallBridgeGroup WebBridge Client TURN server at client side TURN protocol & port at client side Received by CB after CallBridge TURN allocation Try fist UDP.3478, then TCP.443 RTT and CBgroup (same as above) Decided in previous step Decided in previous step Multiple TURN choices per CB Multiple TURN servers Multiple TURN servers 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 149

147 WebRTC Expressway Proxy : Localization and HA Tools Selecting entity Service / Server Section method Localization High Availability Client Expressway-E DNS A (Xway sticks the session with a cookie) GEO DNS Expressway-E Expressway-C Transversal Zone Config. Regional Xway Cluster, Configuration Multiple Xway-E A records and/or smart DNS Clustering, transversal zone configuration Expressway-C WebBridge DNS SRV record GEO DNS Multiple SRV records and/or smart DNS WebBridge (via XMPPserver) (WebBridge located in core) CallBridge (CB) WebBridge estimation RTT among CB and CB+TURN (TBVerified) ( sticky result ) - TURN according to CBgroups - RTT favour regional TURN servers Multiple CallBridges WebBridge XMPP server DNS SRV record GEO DNS XMPP clustering For reference CallBridge (CB) TURN Server CB RTT estimation + CallBridgeGroup WebBridge Client TURN server at client side TURN protocol and port at client side Received by CB after CallBridge TURN allocation Try fist UDP.3478, then TCP.443 RTT and CBgroup (same as above) Decided in previous step Decided in previous step Multiple TURN choices per CB Multiple TURN servers Multiple TURN servers 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 150

148 On-Premises MS Interoperability

149 Dual homed call setup via drag and drop (*) For reference Lync client Lync client MS Front End & AVMCU Call Bridge Video EP Lync clients in meeting SIP: INVITE VideoEP SIP: (re)invite VideoEP with conf:focus:id:r6khvk2y escalating Lync conversation. To Lync Conference drag and drop Video EP to the meeting SIP: INVITE conf:focus:id:r6khvk2y Lync conference subscription SIP: SUBSCRIBE conf:focus:id:r6khvk2y SIP: OK with Conference information. All participant in a dual homed meeting (*) simplified Media SIP 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 152