Professional Documents
Culture Documents
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
cs.co/ciscolivebot#BRKCOL-3990
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Agenda
Cisco Meeting Server, on-premises and hybrid
large scale conferencing design
• Introduction
• Core
• Edge
• MS Interoperability
• Hybrid Conferencing
• Conclusions
• Backup slides
Introduction
CMS - Key Capabilities
What CMS does
Cisco Meeting
Audio Browser Access
Video Conference Spaces Application MS Interoperability
Conference (WebRTC)
(Native CMA)
BRKCOL-2803 Abhijit Dey Designing and deploying multiparty conferencing for telepresence video
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
Core CMS sizing
Platform Capacity [HD sessions per server(*)] Session Capacity
Type Multipliers
CMS 2000 500 (up to CMS 2.2)
Full-HD 0.5
CMS 1000 (****) 96 1080p30
HD (*) 1
MM410v (legacy) 64
720p30
MM400v (legacy) 32 480p30 2
Dedicated server VM (**) 2.5 per physical core Audio (***) 40
(*) 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:
https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-meeting-server.html
(***) 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)
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 8
Management / Admin methods
How to interact with CMS
CLI /
API
Console
WebAdmin
SFTP
(Web GUI)
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 9
CMS - Services
CMS Key Software Components
H323 GW and
Call Bridge XMPP WebBridge Turn Server Load Balancer
SIP Edge
(core) (core) (core, edge) (edge) (edge)
(legacy)
Video Bridging core Client and WebRTC with compatible Firewall traversal for XMPP signalling H323 GW (not GK)
Call Control Inter-component browsers (Chrome, media traffic firewall traversal
Media processing signalling Firefox, Opera) (proxy) SIP firewall
Clustering transversal
IM&P Brand-able
VP8 & H.264 Equivalents services
exist in Expressway
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 10
Architecture – Core only – Single server
CMA WebRTC
Clients Clients
XMPP WEBBRIDGE
SIP
XMPP
Media
LDAP
AD
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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 11
Architecture – core and edge (pre-Expressway WebProxy)
CMA WebRTC
Clients Clients
External
TURN
DMZ
LOADBALANCER WEBBRIDGE
EDGE SERVER
SIP
Internal XMPP
XMPP WEBBRIDGE
HTTPS / WEBRTC
CALLBRIDGE
CORE SERVER Media
AD LDAP
WebRTC
Clients
CMA
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 12
Clients
CMS Clustering
Benefits Components
• Scalability Database Clustering
• Resiliency • Spaces
• Geographic optimization: • Dial Plan
• Reduce latency using closest call • Cluster-wide configuration
bridge Call Bridge Clustering
• Minimize WAN traffic • Distributed calls
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 13
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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 14
Clustering Architecture - Call Bridge with dedicated DB
• Keepalives
Call Bridge Cluster • Call Status
• Distributed Calls
• Max 300 ms RTT
(max 100 ms RTT within CallBridgeGroup)
• Spaces
• Users Call Bridge Cluster
Database Connect • Dial-plan HTTPS + SIP
• Cluster-wide
configuration
• Max 300 ms RTT Database Connect
TLS/Postgres
• Cluster sync DB Master
• Max 200 ms RTT
Postgres Database Cluster
TCP/TLS Port : 5432 Database Cluster TLS / Postgres
DB Slave DB Slave
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 15
Clustering Architecture - Call Bridge with co-located DB
Database Cluster
• Keepalives Call Bridge Cluster
• Call Status HTTPS + SIP
Call Bridge Cluster • Distributed Calls
DB Slave
DB Slave Database Connect
TLS/Postgres
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 16
Distributed calls
Resiliency, scale, geo-distribution
Conference 1
Conference 2
EMEA
Americas APAC
(*) up to 4 streams using
max “peerlinkbitrate” bandwidth
(before CMS 2.3) BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 17
For reference
DB: MySpace1
SIP: INVITE MySpace1
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 18
XMPP Clustering
Highlights
XMPP High Availability mechanism with keepalives
3 or 5 XMPP Servers
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
• Several DNS records are required for the solution to work properly
• 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 5222
-For CallBridges to locate XMPP cluster members _xmpp-components._tcp.mycompany.com port 5223
5. A more comprehensive list is in installation docs
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 21
Deployment Prerequisites - Certificates
•WebAdmin
Certificate
•XMPP
•WebBridge types:
•Callbridge
• self-signed
Components •Loadbalancer
that need a
certificate: •Trunk
•Turn (if using TLS)
•Database Cluster • Private CA
•Recording server
•Streaming server
Signed
• Public CA Signed
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 23
• Use case 1
• TMS Scheduling
Use Case 1
Large enterprise with established worldwide collaboration infrastructure
with the need of pervasive video services with global coverage
Structural requirements (*): Conferencing requirements:
• Three worldwide regions (**) • Virtual Meeting Rooms (VMR)
• Redundancy with 2 Data Centres (DC) in • Scheduled meetings with OBTP (One
each region (**) Button To Push)
• Traffic Optimization (localize the traffic to • Expected load around 2000 HD ports
regions whenever possible) 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 25
Use Case 1 - Architecture Summary
Sizing for use case 1 :
AD 6 x CMS-2000 : 3000 HD ports
3 x spec based VMs for DB servers
Calendar
TMS+TMSXE
Global
(**) (**) (**)
Routing &
Management
Regional
.
Call Control
. .
Conferencing
Core Core Core (CMS cluster)
Database Database Database
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
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
. . .
Conferencing
(CMS cluster)
Americas EMEA APAC
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 28
Traffic optimization 2 - HA and loop avoidance
Avoid call loop when using CMS in other region as backup/overflow
Incoming CSS of trunk to other SME Incoming CSS of trunk to leaf CUCM has
can only see local CMS access to regional CMS and other SME’s
Global
Trunk_to_other_SME Trunk_to_regional_CUCM Routing &
.
IncomingCSS
. . Incoming CSS Management
(RP,RL,RG) (RP,RL,RG)
1) EMEA_CB1 1) EMEA_CB1
2) EMEA_CB2 2) EMEA_CB2 Regional
3) other SMEs Call Control
. . .
EMEA_CB2
Conferencing
Core EMEA_CB1 Core (CMS cluster)
Americas EMEA APAC
CMS 2.x White Paper : Load Balancing Calls Across Cisco Meeting Servers
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 29
Intra-region or Intra-DC distributed conferences should be
limited
Conference 1
Conference 2
Conference 3
Conference 4
For these four conferences load balancing distribute If call legs belonging to the same conference
calls may create up to 17 call legs (9+4x2) are bound to a single CallBridge in the region,
With more CallBridges number can increase fast!! then the number of call legs is reduced to 9
(even with more CallBridges )
.
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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)
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 31
For reference
Media
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 32
Call Bridge Group – Feature II: Load Balance
• A mechanism is necessary to ensure load
balancing of conferences in the same EMEA_CUCM
CallBridge Group
• This is implemented by distributing conferences
3) Invite 1) Call to
based on conference_ID and bridge_ID hashing w/Replace Space 02
that generate a “priority” in the CallBridge choice to Space02
replace query for conference YYY using server CB2 (priority: 0, load level: 0, conference is running: 1) EMEA_CBGroup
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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 Max load Limit
100%
• 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 Existing Conference
Threshold 80 %
the call;
• Limit is variable according to the conference state
New Conference
Threshold 50%
• CUCM receives “SIP 488 ,Not acceptable
here”, and Dial Plan (RG, RL) can be
configured to route advance to next call bridge
• 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)
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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
Use case 1
Active
CallBridge Database
Directory
AD
+ Space
Key parameters for mapping
User (XMPP ID & URI) Alice@meet.ucdomain.com
Username: $sAMAccountName$@meet.ucdomain.com
Space URI Alice.space@meet.ucdomain.com
Space URI user part: $sAMAccountName$.space
2nd Space URI 8884085267209@meet.ucdomain.com
Space secondary URI user part: 888$telephoneNumber$
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 35
CMS Dial plan : Inbound call processing
Stage 1 Incoming
Stage 2 Forwarding
• Is the call for this CMS ?
• For spaces, users, IVR ? Stage 3 Outgoing
• Shall the call be
• Does the call require a Lync forwarded ?
meeting resolution ? • Where to send the call ?
• With domain rewrite ?
• 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 36
CMS dial plan configuration details EMEA_CUCM
ucdomain.com
Focus on configuration of one region: EMEA
EMEA Inbound dial rules for CUCM EMEA_CBGroup
EMEA_CB1 EMEA_CB2
Targets Targets Targets
Domain name Priority Targets Lync
spaces users IVRs
meet.ucdomain.com (1) 100 Yes Yes Yes No
Dial transform for CMA/WebRTC numeric dial-out (1) Highest priority domain will be used in meeting request invite
(2) Assuming CUCM trunk has CMS FQDN as “destination address”
type Match exp. Transform Prior. Action (3) alternative : multiple rules for each Subscriber
(4) required by distributed calls when “default SIP route” is used
strip ($1/(.*)/) $1@ucdomain.com 10 accept (5) Same domain entries need equal priority
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 37
TMS Scheduling
From version 15.3 TMS supports CMS as scheduled bridge
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 39
Use Case 1 TMS Scheduling and OBTP - Flow
TMS+TMSXE
1) Meeting
2) Send OBPT
Calendar to Endpoints Global
Routing &
. . Management
.
3) Program
meeting
on CMS
4) OBTP to 4) OBTP to
Join Join Regional
conference conference Call Control
. . .
Conferencing
(CMS cluster)
5) Distributed call
(*) 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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 15.5+ 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)
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 43
TMS Scheduling with auto-connect with separate endpoint SIP domain
TMS
Global
Routing &
Management
. . .
1) Create
meeting
on CMS ap.example.com
Regional
. Call Control
. us.example.com 2) Conference .
Start
CBGroup EU
Conferencing
eu.example.com
(Global
CBGroup AP
cluster)
CBGroup US 3) Distributed Conference
on global CMS cluster
EMEA
Americas APAC
HTTPS / SIP Media EWS
SIP API
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 44
TMS Scheduling with auto-connect with single endpoint SIP domain
TMS
Global
Routing &
. . Management
.
1) Create
meeting
on CMS example.com
Regional
.
2) Conference Call Control
. example.com
Start .
Conferencing
CMS
CMS 3) Conference (Regional
Cluster on regional CMS CMS
Cluster EMEA cluster example.com
cluster clusters)
Americas APAC
EMEA
Americas APAC
HTTPS / SIP Media EWS
SIP API
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 45
Conference Management : CMM 1.x
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 46
Update CMS 2.3, CMM 1.0, TMS 15.6,
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 47
User case 3 -
Ad-hoc conferencing
Use Case 2
A large and dynamic worldwide enterprise where employers communicate on the fly
and need ad-hoc conference capability
Structural requirements (*): Conferencing requirements:
• Three worldwide regions Mainly Ad-hoc conference with participant
• Redundancy with 2 DC in each region (**) belonging to any region
• Traffic Optimization 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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)
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 50
CUCM ad-hoc Conferencing - Architecture
Direct trunk from regional CUCM clusters for ad-hoc conference
Global
. . . Routing &
Management
Regional
Call Control
. . .
Core Conferencing
Core Core (CMS cluster)
. . Global
.
Routing &
Management
.
.
Regional
Call Control
.
Merge
conference
Conferencing
Core Core Core
(CMS cluster)
(*) Note that this is below the 500 XMPP sessions limit
CMS 1000: CMS 1000: Alternatively the same topology can host 480 SIP HD ports,
- Call-Bridge - Call-Bridge but then it is worthy considering CMS2000 that doesn’t
- Webbridge - Webbridge “waste” capacity for distributed legs
- XMPP - XMPP
- Database CMS 1000: - Database
- Call-Bridge
- Webbridge XMPP Call Bridge Cluster Database Connect Database Cluster
- XMPP HTTPS + SIP TLS/ Postgres TLS / Postgres
- Database
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 55
• WebRTC proxy with Expressway
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 57
From legacy CMS Edge to Expressway Web-Proxy
XMPP
Core CMS
With WebBridge
DNS
DNS
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 60
CMS Edge Design – Sizing (*)
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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 63
Multiregional architecture with CMS edges
For CMA and WebRTC clients (this is the full picture for next slide diagram)
Americas EMEA 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
LB: LoadBalancer
WB: WebBridge CallBridge Groups include CallBridges, TURN and WebBridge servers
TU: TURN server
CB: CallBridge
XM: XMPP server BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 64
CMA: Service Selection
It affects High Availability and Traffic Localization (for full picture see previous slide)
(GEO) DNS SRV “Home” selection using RTT among LB: LoadBalancer
_xmpp-client Call Bridge direct and CallBridge via TURN WB: WebBridge
(TURN/CB pairs from CBGroups) TU: TURN server
CB: CallBridge
XM: XMPP server
LB WB TU TU WB LB TU LB WB
-Turn configuration
-CallBridgeGroup
-RTT
WB CB CB WB XM XM CB WB
CB WB CB WB CB WB CB WB
CB WB CB WB
Core CMS XM DB XM XM
Core CMS DB Core CMS DB
LB: LoadBalancer
WB: WebBridge
CallBridge Groups include CallBridges and TURN servers in Expressway
TU: TURN server
CB: CallBridge
XM: XMPP server BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 66
WebRTC proxy via Expressway: Service Selection
It affects High Availability and Traffic Localization LB: LoadBalancer
(GEO) DNS A WB: WebBridge
meet.MyDomain + TU: TURN server
Xway cookie CB: CallBridge
XM: XMPP server
Xway-E
Xway-E TURN
TURN
Xway Clusters
Transversal
Configuration
Xway-C
(GEO) DNS SRV
Xway-C _cms-web._tls
WB CB CB WB XM XM XM WB
core core
Region1 CallBridgeGroup1 Region2 CallBridgeGroup2 (partially shown)
DNR SRV
1) WebBridge (and CB) has selected XMPP (DNS SRV) Selecting entity and criteria
2) Client selects Expressway-E (DNS A) Selected Path
3) Expressway Transversal (transversal) Alternative Selections
4) Xway-C selects WebBridge (DNS SRV)
5) WebBridge selects CallBridge/TURN (CBGroups, RTT)
6) CallBridges selects TURN (CBGroups, RTT) BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 67
Multiregional Architecture with CMS and Expressway Special use case
With limitation of cross DC traffic to DMZ
Americas EMEA APAC
CB WB CB WB CB WB CB WB
CB WB CB WB
Core CMS XM DB XM XM
Core CMS DB Core CMS DB
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 69
For reference
loadBalancingEnabled = true Use to LoadBalance SIP calls to spaces and to minimize distributed
call between CallBridges in the same CallBridge Group
loadBalanceOutgoingCalls = true Use to optimally allocate outgoing calls to CallBridges or
CallBridgeGroups
loadBalanceUserCalls = true Use to optimally allocate user calls (webRTC and CMA) to
CallBridges or CallBridgeGroups
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 71
On-Premises MS Interoperability
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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 73
Skype for Business Integration call types
Gateway : call goes across CMS for adaptation and transcoding
LYNC SERVER
AVMCU
5 media streams
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 74
Call types: Call start and user experience comparison
Call method CMS call type End user End user
experience experience MS
video side side
-Dial Lync meeting via IVR Dual homed Good Lync layouts,
-Drag and drop Video EPs into a roster and limited
Lync conference controls
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 75
Video endpoint user experience
When joining a Lync/S4B (dual homed) scheduled meeting
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 76
For reference
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 77
For reference
Client creates
a Lync Meeting
(*) simplified Media SIP BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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 (**) • Point to point call between Video EP and
• Redundancy with 2 Data Centres (DC) in each Lync/S4B clients
region (**) • Lync/S4B clients able to join Spaces on CMS
• Traffic Optimization (localize the traffic to (rendezvous)
regions whenever possible) • 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 79
Use case 4 : Architecture
Calendar
Global
. .
TMS & TMSXE
Routing &
.
Management
Regional
Call Control
. . .
Conferencing
CMS cluster
MS Lync/S4B
Front End Pool +Infra Front End Pool +Infra Front End Pool +Infra
• This ensure that user and space URIs do not overlap with Lync/S4B URI
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 81
Use case 4 : Traffic optimization (localization)
Traffic from local EPs to Lync domain is kept local by CUCM DialPlan(*)
Global
Routing &
Traffic. from call Bridge to Lync is . Management
kept local by using CallBridge
specific outbound dial rules
Traffic from call Bridge to CUCM is
kept local by using CallBridge Regional
specific outbound dial rules Call Control
. . .
Conferencing
CMS cluster
CMS Dial Plan: EMEA Outbound dial rules for Lync (CUCM rules omitted)
Domain Local contact Local from Trunk CallBridge
SIP proxy to use Behavior Priority Encryption
domain domain type Scope
lyncdomain.com EMEA_FEP_fqdn EMEA_CB1_fqdn ucdomain.com Lync Continue 10 Encrypted EMEA_CB1
CMS Dial Plan: (additional) Inbound dial rules for Lync CMS Dial Plan: Forward dial rules
Targets Targets Targets Targets
Domain name Priority Forward both ucdomain.com and lyncdomain.com
spaces users IVRs Lync
with no changes
lyncdomain.com 20 No No No Yes
CMS FQDN(s) 10 Yes Yes Yes Yes Direct numeric call from CUCM to Lync Meeting (optional
(*) to be ©added
BRKCOL-3990 toand/or
2018 Cisco configuration
its affiliates. All rightsfor useCisco
reserved. casePublic1 83
For reference
(MS) SIP
SIP Audio/Video
XMPP
Lync
proxy Distributed
HTTPS / SIP leg call leg
Media
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
(MS) SIP
SIP Audio/Video
XMPP
HTTPS / SIP
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
(MS) SIP
SIP Audio/Video
XMPP
HTTPS / SIP
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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 87
MS interoperability off-premises
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 • Video calls with external organizations using
• Redundancy with 2 Data Centres (DC) in each standard SIP
region • Video calls with external organizations with own
• Traffic Optimization 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-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 90
Points of attention and limitations
Points of attention and limitations
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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 91
Use case 5 : Architecture
Regional Global Routing Global Conferencing Edge External
Call control with core CMS cluster with adaptation CMS Users
Organization with
MS infrastructure
Americas
O365 Clients
APAC
SIP HTTPS / WebRTC (MS) SIP
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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, X8.10.2+
• 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-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 93
O365 OBTP Dual Homed experience
TMS/TMSXE Video EP CMS Expressway-C Expressway-E
O365 client
ICE Negotiation
ExpresswayC: call hairpinning to and from CMS for SIP MS variant adaptation + reach O365 via transversal
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 96
For reference
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 97
Hybrid Conferencing
How apply large scale design principles to cloud/hybrid conferencing
Hybrid Media Node Highlights
BRKCOL-2607 Louis Pratt Understanding Cloud and Hybrid Cloud Collaboration Deployment
BRKCOL-1120 Richard Murphy Cisco Spark Hybrid Media Node
BRKCOL-2202 Luca Pellegrini Cisco Spark Hybrid Call Services Architecture and Design
BRKCOL-2030 Anthony Mulchrone Cisco Spark - Cloud and On Premise Security explained
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 99
Conferencing Architecture with Hybrid Media Node in core
PSTN
Webex
Overflow client
CUCM
Expway-C Expway-E Traffic
WebEx/Spark
SIP Video
Endpoints
HMN
Spark
Clients
Spark Video
Endpoints
Webex
clients B2B partner
PSTN
Webex
Overflow client
CUCM
Expway-C Expway-E Traffic
WebEx/Spark
SIP Video
Endpoints
HMN
Spark
Clients
Spark Video
Endpoints
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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
Spark
Clients HMN WebEx/Spark
Cluster HMNs
Spark Video
Endpoints
DC 2
WX
clients HMNs
Spark
Clients WebEx/Spark
Spark Video
Endpoints
DC 2
WX
clients HMN Cluster
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 105
Design Notes
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 106
Cloud Allocation of HMN within HMN cluster
How CUCM is informed about the HMN to use
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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 HMN2
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 108
Design Notes – Bandwidth utilization
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 109
Design Notes – Bandwidth utilization - Examples
SIP + Webex clients (average bandwidths)
Webex
client (on cloud)
SIP Video
Endpoints
WebEx/Spark
SIP Video
Endpoints
HMN
SIP Video
Endpoints
SIP Video
Endpoints
Webex
clients
(on prem)
(*) Two participant streams but only one sent with 720p
Webex session
media Audio Video HMN Video
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 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)
Spark Video
B2B partner
Endpoints
6 streams 1 stream
vs.
1 stream 1 stream
Remote Video Remote Video
Endpoint Endpoint
Webex session
media Audio Video HMN Video
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 114
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 : Conferencing requirements:
• Three worldwide regions Webex Meetings
• Redundancy with 2 DC in each region Personal Meeting Rooms
• Maximize Local (on-premises) Media Scheduled Meetings
Only SIP Endpoints and Webex clients
Termination
• Traffic Optimization
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 115
Additional Design Notes
CUCM SIP trunk(s) to HMN HMN selection (SIP devices)
• CUCM trunks to different HMN • HMN cluster used for the call is
regional clusters need be separate chosen by CUCM
HMN traffic • HMN server inside a cluster is chosen
by the cloud based on HMN inputs
• HMN intra-cluster traffic stays within (latency, load)
enterprise network
HMN selection (Spark clients/rooms)
• HMN inter-cluster traffic use cloud
• HMN is chosen by cloud based on
reachability info provided by client
(STUN RTT) with preference for on-
premises HMN
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 116
Additional Design Notes
Want to keep media on-premises Approach to limit HMN inter-cluster traffic for
SIP devices: CUCM Time Of Day Routing
• Do not close port 5004,
1. Prefer a regional HMN cluster at a certain time of the
this will cause split meetings !! day,
• Traffic via cloud can be reduced but not 2. with alternate route to the other HMN regional
avoided, the following traffic types go clusters for High Availability and Overflow
anyway via cloud 3. and to cloud via Expressway for overflow
• Spark/HMN signaling • TOD time switch should avoid meeting start time
• Webex signalling and media :00, :30 (:45 may be a good choice)
• HMN Inter-cluster signalling and media
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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 117
Use case 6 : Architecture
Endpoint SIP Call control On premises Hybrid conferencing layer Regional Edges Webex/Spark
cloud
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 118
Conclusions
When planning a large conferencing infrastructure, you cannot “count on magic”.
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
cs.co/ciscolivebot#BRKCOL-3990
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
• Please complete your Online Complete Your Online
Session Evaluations after each
session
Session Evaluation
• 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
Don’t forget: Cisco Live sessions will be available
for viewing on-demand after the event at
www.ciscolive.com/global/on-demand-library/.
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Tech Circle
• Meet the Engineer 1:1 meetings
• Related sessions
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 122
Thank you
BACKUP SLIDES
Cisco Advanced Services
Cisco Advanced Services Portfolio
Implement Services
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 127
Cisco Meeting Server Services
Advise and Implement
• Highly scalable video and audio conferencing design Cisco
TelePresence
Cisco MCU
• Interoperability with Microsoft Lync/Skype for Business and WebRTC Server
Cisco
Meeting
Optimize Server
Other relevant AS value added services are available: NPA, MNRA, Adoption.
Please contact AS Global BDM team for Advanced Services scoping & quotes.
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 128
Value Added Services
Proposed AS Value Added Services
Customer Issues
• When installing Cisco Meeting Servers in new data centers Network Path Assessment (NPA)
• When installing Cisco Meeting Servers that have more capacity than the
existing MCUs / TelePresence Servers -- or –
• New video customers deploying video bridges for the first time
• Migration from third party video bridges / services (on-premises or cloud) Media Network Readiness
• Customer environment has known video quality issues Assessment (MNRA)
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 129
CMS configuration quick start
For reference
• FILTER: (&(objectCategory=person)(objectClass=user)(!(cn=Administrator))(!(cn=Guest))(!(cn=krbtgt)))
• Username: $sAMAccountName$@meet.example.com
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 132
For reference
• Add callbridges (CLI on xmpp server) • Webbridge Web GUI config (or API)
• xmpp callbridge add core1
• xmpp callbridge add core2
• Xmpp callbridge list
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 133
Core
For reference
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 135
For reference
DB: MySpace1
SIP: INVITE MySpace1
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 136
For reference
replace query for conference YYY using server CB2 (priority: 0, load level: 0, conference is running: 1)
Media
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 137
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 30000 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
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 138
For reference
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 139
Recording and Streaming
Recording and streaming basic architecture
RECORDING
xmpp client
NFS/mp4
CallBridge + NFS server Video
Recorder Management Viewing
XMPP server Clients
Server
STREAMING
xmpp client
RTMP/H264
CallBridge + Streamer Streaming
XMPP server Server Streaming
Clients
Third party
BRKCOL-2544 Terry French Enterprise Webcasting and Recording Architecture with VBrick Rev
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 142
Scaling Streaming and Recording
Call Bridge Groups allow optimal allocation of resources
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 143
Edge
• Edge design
For reference
CMA Sign-in and Join a space (simplified)
CMA
client LoadBalancer XMPP Server TURN CallBridge(s)
DNS
DNS SRV lookup _xmpp-client._tcp.MyDomain
Join Space
Call Request
DNS XMPP HTTPS / WEBRTC Media/TURN BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 145
For reference
WebRTC Sign-in and Join a space (simplified)
Web
XMPP via CallBridge
client WebBridge TURN
LoadBalancer
DNS
DNS A lookup meet.MyDomain
DNS XMPP HTTPS / WEBRTC Media/TURN BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 146
For reference
WebRTC Guest joins a Space (simplified)
Web
DNS XMPP via CallBridge
client WebBridge TURN
LoadBalancer
TBV WB Evaluate RTT among CB and CB via TURN, Choose CB, Call Request
DNS XMPP HTTPS / WEBRTC Media/TURN BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 147
For reference
Load Balancer XMPPserver Trunks configuration Local Trunk Multiple trunks from
LoadBalancer to XMPP
servers
CMA client (via CallBridge (CB) CMA Client estimation - TURN according to Multiple CallBridges
XMPPserver) RTT among CB and CB CBgroups
via TURN ( sticky result, - RTT favours regional
selected CB will be servers
“homeCB” )
CallBridge (CB) TURN Server CB RTT estimation + RTT and CBgroup Multiple TURN choices
CallBridgeGroup (same as above) per CB
CMA Client TURN server at CMA Received by CB after CB Decided in previous step Multiple TURN servers
client side turn allocation
TURN protocol and Try fist UDP.3478, then Decided in previous step Multiple TURN servers
port at CMA client TCP.443
side
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 148
For reference
Client WebBridge (WB) DNS A (need that client sticks GEO DNS Multiple WB A records
with one WebBridge IP) 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 CallBridge (CB) WebBridge estimation - TURN according to Multiple CallBridges
XMPPserver) RTT among CB and CBgroups
CB+TURN (TBVerified) - RTT favour regional
( sticky result -> “home CB”) servers
WebBridge XMPP server DNS SRV record GEO DNS XMPP clustering
CallBridge (CB) TURN Server CB RTT estimation + RTT and CBgroup Multiple TURN choices per
CallBridgeGroup (same as above) CB
WebBridge Client TURN server at Received by CB after Decided in previous step Multiple TURN servers
client side CallBridge TURN allocation
TURN protocol & Try fist UDP.3478, then Decided in previous step Multiple TURN servers
port at client side TCP.443
BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 149
For reference
Client Expressway-E DNS A (Xway sticks the GEO DNS Multiple Xway-E A records
session with a cookie) and/or smart DNS
Expressway-E Expressway-C Transversal Zone Config. Regional Xway Cluster, Clustering, transversal
Configuration zone configuration
Expressway-C WebBridge DNS SRV record GEO DNS Multiple SRV records
and/or smart DNS
WebBridge (via CallBridge (CB) WebBridge estimation - TURN according to Multiple CallBridges
XMPPserver) RTT among CB and CBgroups
(WebBridge CB+TURN (TBVerified) - RTT favour regional
located in core) ( sticky result ) TURN servers
WebBridge XMPP server DNS SRV record GEO DNS XMPP clustering
CallBridge (CB) TURN Server CB RTT estimation + RTT and CBgroup Multiple TURN choices per
CallBridgeGroup (same as above) CB
WebBridge Client TURN server at Received by CB after Decided in previous Multiple TURN servers
client side CallBridge TURN allocation step
TURN protocol Try fist UDP.3478, then Decided in previous Multiple TURN servers
and port at client TCP.443 step
side BRKCOL-3990 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 150
On-Premises MS Interoperability
For reference