Brkcol 2607

BRKCOL-2607
Understanding Cloud and

Hybrid Cloud
Collaboration Deployment
Louis Pratt, Principal TME
Agenda
• Cisco Webex Platform
• What is Hybrid Cloud Collaboration
• Hybrid Directory Service
• Hybrid Calendar Service
• Hybrid Call Service
• Hybrid Message Service
• Conclusion
BRKCOL-2607 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Cisco Webex Teams
Questions?
Use Cisco Webex Teams (formerly Cisco Spark)
to chat with the speaker after the session
How
1 Find this session in the Cisco Events Mobile App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
cs.co/ciscolivebot#BRKCOL-2607
Session Objectives
At the end of the session, the participants will understand:

• Cisco Webex Teams must exist for anything Hybrid Services related
to exist
• Flexibility of Cloud and Premises, Together
• Existing on-premises deployments can integrate with Cisco Webex
• Existing cloud deployments can integrate with Cisco Webex
Cloud Collaboration
Cisco Webex – The Platform
Common Management
Messaging Meeting Calling
Open Platform
Application Integration Partner Services Cisco Webex Hybrid

APIs Services
Cloud + On-Premises
Cisco Webex – Meetings
Anywhere, Anytime, Any Device
Cisco Webex
3rd Party endpoints

& service
integrations
Webex Teams
Mobile App
Cisco Webex WebEx Cisco Video

Webex Teams Cisco Webex App Endpoints
Room Device
Desktop App Desk Phone
Cisco Webex – Room Devices
DX70 DX80
• Group collaboration from a meeting room
• Enhance the Cisco Webex experience in
a quiet space with a larger display
• Enterprise Class devices
• SX10N, SX20, SX80 Cisco Webex Board 55 / 70 / 85
• MX200 G2, MX300 G2 Room 55 MX 200 / 300
• MX700, MX800, MX800D Cisco Webex
• DX70 and DX80 Share
• Cisco Webex Board 55/70/85
• Room Kit, Room Kit Plus, Room Kit Mini
• Room 55
MX700 MX800 MX800 Dual
• Cisco Webex Share
• Simplified user experience with Cisco
SX80
Webex Teams app integration Room Kit
SX20
Room Kit Mini
SX10N
Room Kit Plus
Cisco Webex Hybrid Services: AND, not OR
Hybrid Directory Service
Cisco Webex platform

Messaging | Meetings | Calling
Hybrid Calendar Service
Hybrid Call Service
• Call Service Aware
• Call Service Connect
Hybrid Message Service
Existing Services
Hybrid Media Service
Creating unique value by connecting

on-premises and cloud services Hybrid Data Security
Cloud Collaboration – Cisco Webex Platform
Cisco Webex Platform Services
Call Control Identity/SSO Rooms
Notification/Alerts Media/Transcoding
Messaging Interop Content Sharing
Management Calendar Future
Cisco Webex Infrastructure
Metrics &
Reporting
File
Storage
Metadata
Storage Billing & Remote Users
Provisioning
Custom
REST
Applications
based
APIs Widgets
Hybrid Cloud
Collaboration
Hybrid Cloud Collaboration
Cisco Webex Platform Services Enterprise
Conductor
TS
Notification/Alerts Media/Transcoding Video Endpoints

Expressway-E Expressway-C
Management Calendar Future Unified CM
Jabber
Metrics &
Reporting
File
Storage
Metadata
Storage Billing & Remote Users
Provisioning
Custom
REST
Applications
based
APIs Widgets
Integrating On-Premises and Cloud
Webex
Messenger
Expressway
Windows
Platform
Data
Microsoft AD Exchange Cisco UCM* IM&P Media Node
Security
*Includes Business Edition or HCS
Hybrid Directory Service
On-Premises Directory Synchronization
WebEx
Messenger
Windows
Microsoft AD
Identity integration for Users & Devices
Enterprise Directory:
Directory Connector
is the integration point
for user identity
HTTPS
Identity/SSO
Cisco Webex
Active Directory
Directory Connector
 Directory connector integrates with AD to retrieve user information to sync with the identity
service, and specifies the Active Directory synchronization agreement and attribute mappings
 Customer installs Directory Connector in its network on a Windows Domain server (Windows
Server 2003, 2008 R2, 2012, 2012 R2, 2016) with administrative user privilege
 Directory Connector supports Single Forest, Multi-Domain and Multi-Forest, Multi-Domain
Admin Portal DirSync User Configuration
Cisco Directory (DirSync) Connector
Custom Attribute Mapping Requires Directory
Connector 3.0
Cloud Identity integration for Users & Devices
Currently
in EFT
HTTPS HTTPS
Identity/SSO
System for Cross-Domain Cisco Webex
Identity Management
https://www.simplecloud.info
 Simplified user provisioning and lifecycle management
 Enterprise Authentication via enterprise standard SAML

IDP or industry leading IDaaS vendors
 API Security - OAuth 2.0 provides API security for
integration with third party SaaS providers
Identity SCIM Operations with Webex Control Hub
Create (User with full information)
POST https://api.ciscospark.com/v1/scim/{OrgId}/
Read (Get user full information)
GET https://api.ciscospark.com/v1/scim/{OrgId}/Users/{userid}
Update (Update user partially)
PATCH https://api.ciscospark.com/v1/scim/{OrgId}/Users/{userid}
Replace (Update user completely)
PUT https://api.ciscospark.com/v1/scim/{OrgId}/Users/{userid}
Search (Search user with specific filter)
GET https://api.ciscospark.com/v1/scim/{OrgId}/Users?filter=username
Delete (Delete User)
DELETE https://api.ciscospark.com/v1/scim/{OrgId}/Users/{userid}
The Edge
DMZ
Notification/Alerts Media/Transcoding Video Endpoints

Cisco Webex Infrastructure Jabber
Metrics &
Reporting
Future Service
Serviceability
Management
Metadata
Connector
Connector
File
Connector
Connector
Connector
Connector
Calendar
Message
Storage Storage Billing &
Call
SIP Trunk
Provisioning Expressway
XMPP
C
*Note: This is a net Common Connector Framework

new Expressway-C DC
for hosting connectors Directory
Connector
Hybrid Service Expressway-C Registration Complete
Management Connector
DMZ
Metrics &
Reporting
Future Service
Serviceability
Management
Metadata
Connector
Connector
File
Connector
Connector
Connector
Connector
Calendar
Message
Call
SIP Trunk
XMPP
C
Common Connector Framework

DC
Directory
Connector
Hybrid Services Connector Management
Call Control Identity/SSO Hybrid
User Discovery /
Management
Status Subscription
Service
Management Calendar
Future Service
Serviceability
Management
Connector
Connector
Connector
Connector
Connector
Connector
Calendar
Message
Call
SIP Trunk
Expressway
XMPP
C
User Status Service

• Interfaces with Identity for hybrid entitled users Common Connector Framework
• Stores hybrid service status per user DC
• Notifies downstream services about any Directory
entitlement changes Connector
Webex Control Hub
Administration Portal
Demo
Demo
Calendaring Scheduling Integration with @webex
https://collaborationhelp.cisco.com/article/en-us/nwtulzs
Users can use either @webex or @meet in a

calendar scheduling invite, not both.
@webex will backfill the users personal room

information into the calendar invite (seen here)
@meet or will utilize the Cisco Webex Teams

space information when populating a calendar
invite, or create a new space (next page).
There are also modifiers :space and :myroom
Calendaring Scheduling Integration with @meet
Note: Due to the rebranding, changes

were made in Q3CY18 for keyword
usage from @spark to @meet Desktop Mobile
Calendar Service Exchange Calendaring
WebEx
Messenger
Edge
Exchange /
Office 365
Calendar Service
DMZ
Metrics &
Reporting
Future Service
Serviceability
Management
Connector
File Metadata
Connector
Connector
Connector
Connector
Connector
Message
Calendar
SIP Trunk
Call
XMPP
C
Exchange Web Services (EWS)

RESTful https DC
Directory
Connector
Calendar Service Configuration Specifics
• Minimum Exchange 2010 SP3 required due to updates in throttling policies.
http://msdn.microsoft.com/en-us/library/office/jj945066(v=exchg.150).aspx
• Exchange 2013, Exchange 2016, and O365 are also supported.
• EWS Subscription Group - Each group has one streaming subscription

connection containing up to 200 individual streaming subscriptions.
• Using Exchange Web Services (EWS) and an Exchange Impersonation Account
• @webex functionality requires WBS31 or higher
• Deploying Calendar Service:

https://www.cisco.com/go/hybrid-services-calendar
Expressway-C Exchange Configuration
Expressway-C WebEx CMR Configuration
Calendar Service Deployment
Identity/SSO DMZ DC
Management Calendar
Dedicated
Expressway-C
A dedicated Expressway C for Connectors

• Small OVA template – 5000 users
• Large OVA template – 15000 users cas1.example.com cas2.example.com
* Note: O365 capacity is 5000 users for both

Calendar Service
Features
Set Out-of-Office from Outlook
OOF Presence status reflected in Webex Teams
Collaboration Cloud Services Waterfall Hiker
Out of Office until 10/17/2016
Calendar Presence
Presence status displayed when
(a) @Mentions used to mention a user
User sets Out Of Office from Outlook (b) Go to 1:1 room with user
(c) 'User' searched by name
(d) People roster expanded (web client only)
Future Service
Serviceability
Management
Connector
Connector
Connector
Connector
Connector
Connector
Message
Calendar
SIP Trunk
Call
Expressway
XMPP
C

DC
Exchange and O365 supported Directory
Setting from within the app not supported today Connector
Calendar Service OBTP
Conductor
TS
Notification/Alerts Media/Transcoding TMS Video Endpoints

Jabber
Metrics &
Reporting
Future Service
Serviceability
Management
File Metadata
Connector
Connector
Connector
Connector
Connector
Connector
Message
Calendar
SIP Trunk
Call
XMPP
C
Mobile Endpoint:
Participants click CMR link and get to org’s Cloud CMR
Video Endpoint:
Participant taps Join button in room, goes to CMR.
DC
Directory
@webex and @meet: Connector
MINIMUM REQUIREMENT: CALENDAR SERVICE + TMS15 AND TMSXE5
What about Cloud
Calendaring?
Calendar Service for Cloud Calendaring
DMZ
Messaging Interop
Metrics &
Reporting
Future Service
Serviceability
Management
Connector
Metadata
Connector
Connector
Connector
Connector
Connector
File
Message
Calendar
Billing &
Storage Storage
SIP Trunk
Call
XMPP
C

DC
Directory
Connector
Calendar Connector without any premises equipment
Messaging Interop Cloud Calendar Connector
Metrics &
Reporting
Metadata
Connector
File
Calendar
Billing &
Storage Storage Provisioning
Cloud Calendar Connector
Cloud Calendar Connector uses the
same system architecture; however,
the connector resides in the Cisco
Management Calendar Future Collaboration Cloud (i.e. requires no
Metrics &
premises infrastructure)
Reporting
File Metadata
Billing &
Allows the end user experience for
meeting scheduling and calendar
integration to remain the same
Calendar Service –Google via Cloud Calendar Connector
Metrics &
Reporting
File Metadata
Billing &
Calendar Service – Configuration
Metrics &
Reporting
File Metadata
Billing &
Calendar Service – Google User
Metrics &
Reporting
File Metadata
Billing &
Calendar Service – Google Calendar
Google
Messaging Interop Cloud Calendar Connector REST API
Management Calendar Future Webhook
Metrics &
Reporting
File Metadata
Billing &
User schedules
meeting using
@webex or @meet
Calendar Service – Office 365 Calendar
Microsoft
Messaging Interop Cloud Calendar Connector Graph API
Metrics &
Reporting
File Metadata
Billing &
User schedules
meeting using
@webex or @meet
Calendar Service – Office 365 Calendar Activation
© 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public
Office 365 Exchange Online Setup
1. Click Authorize in Cisco Webex Control Hub
2. Sign-in to Microsoft as Global Admin
3. Accept permission scope
• Read/Write Calendar in all mailboxes – read &
decorate meetings
• Read All User Profiles - Localization
• Read Mailbox Settings - OOF
4. Test configuration with an email address
5. Enable users
6. Add room resource email address to Place in
Webex Control Hub
O365 – Cloud Calendar Connector
https://collaborationhelp.cisco.com/article/en-us/niqovwv
O365 – Cloud Calendar Connector
Google Calendar
Integration
Google G suite Apps https://admin.google.com/
Google G suite Calendar setup
Google G suite Calendar Video Meeting decoration
Note: Consider leaving

the Video Calls option
unselected to simplify
the meeting decoration
that the end user
receives
Hybrid Calendar Service Google Registration
https://admin.webex.com/
Hybrid Calendar Service Google G suite setup
Google G suite Security
https://admin.google.com/
Hybrid Calendar Service Google G suite integration
Hybrid Calendar Service Google G suite Manage API
Hybrid Calendar Service Google G suite finish setup
Hybrid Calendar Service Google G suite test account
Hybrid Calendar Service Google G suite complete
Hybrid Calendar Service Google Settings
OBTP Cloud Registered
Endpoint
OBTP User Meeting Scheduling Experience
Cloud Registered
Room Device
Bookable Resource
OBTP User Meeting Join Experience
Touch 10
Desktop Before Meeting
Cloud Registered Room Device

On-Screen
Desktop During Meeting Display
Google G suite Apps https://admin.google.com/
Google G suite Resources setup
OBTP Calendar Mailbox Room Resource - Google
https://support.google.com/a/answer/1033925?hl=en
Hybrid Calendar Service OBTP for Room Device
Hybrid Calendar Service OBTP for Room Device
OBTP Calendar Mailbox Room Resource: Exchange
https://technet.microsoft.com/en-us/library/jj215781(v=exchg.160).aspx
OBTP Calendar Mailbox Room Resource – Office 365
OBTP Calendar Exchange Room Resource Place
Hybrid Call Service
Call Service Integration (UCM, BE6K, or HCS)
WebEx
Messenger
Edge
Cisco UCM *
*Includes Business Edition or HCS
Call Service Connect
Call Service Connect
Expressway
Media Relay
HTTP Proxy
Traversal
SIP Trunk
DMZ Expressway
XMPP
E
Metrics &
Reporting
Future Service
Serviceability
Management
Connector
Metadata
Connector
Connector
Connector
Connector
Connector
File
Message
Calendar
Billing &
Storage Storage
Call
C
Media Expressway
C
AXL / CTI
RESTful https DC
SIP Directory
Connector
Call Service Connect: Premises Device Dial Use Case
Cisco Webex Platform Services Donald
Example
Notification/Alerts Media/Transcoding 4 3 1
Any Unified CM
Expressway-E Expressway-C Unified CM registered device
2
Metrics & Spark-RD
Reporting
Expressway-C
File Metadata
Billing & for Connectors Daisy
1 Call initiated from a Unified CM registered device
5 2 Call presented to device and associated Spark-RD
3 Spark-RD routes daisy@example.call.ciscospark.com
Daisy 4 Call presented to Cisco Webex cloud Call Control
Media 5 Call presented to Cisco Webex Teams
Call Service Connect: Webex Teams Initiated Use Case
Cisco Webex Platform Services Donald
Example
X
5 Expressway-E Expressway-C 5 Unified CM
Any Unified CM
registered device
4
Metrics & Spark-RD
Reporting
Expressway-C
File Metadata
1 Call initiated from Cisco Webex Teams to Donald

1
2 2 Call forked to Webex Teams & donald@example.com
3 Call routed to Unified CM for donald@example.com
Daisy Donald
4 Call presented to device and associated Spark-RD
5 Spark-RD routes donald@example.call.ciscospark.com
Call Service Connect: Webex Teams URI Dial Use Case
Cisco Webex Platform Services Belle
Example
Any Unified CM
Metrics &
Reporting
Expressway-C
File Metadata
1 1 SIP URI dial from Webex Teams to belle@example.com

2 Call sent belle@example.com (not using Webex Teams)
Daisy 3 Call routed to Unified CM for belle@example.com

4 Call presented to device
Call Service Connect: Webex Teams PSTN Use Case
Cisco Webex Platform Services Belle
Example
Notification/Alerts Media/Transcoding 2 3
Any Unified CM
Management Calendar Future 4
Metrics &
Reporting
File Metadata Expressway-C +19195551212
Billing & for Connectors
1 PSTN dial from Webex Teams to +19195551212
1 2 Call routed via SIP Destination (based on CFQDN)
3 Call routed to Unified CM for +19195551212
Daisy 4 Call presented to PSTN Gateway with CallerID of
Daisy’s enterprise DN
Multi-Cluster Call Service Connect
Daisy
US
Directory URI Destination in Route Header
daisy@example.com us-ucm.example.com
donald@example.com us-ucm.example.com Call
Connector
Any Unified CM
Unified CM registered device
Expressway-C Cluster Fully Qualified Domain
for Connectors Name: us-ucm.example.com
EMEA
Directory URI Destination in Route Header
goofy@example.com emea-ucm.example.com
Goofy
Call
mickey@example.com emea-ucm.example.com Connector
Unified CM
Expressway-C Cluster Fully Qualified Domain

for Connectors Name: emea-ucm.example.com
Call Service Connect: Multi-Cluster Use Case
Belle
2 Cisco Webex Platform Services US Example
Any Unified CM
Cluster Fully Qualified Domain Name: us-ucm.example.com
Metrics &
Reporting
File Metadata
Billing &
1 SIP URI dial from Webex Teams to belle@example.com

1
2 Call Connector decision routing based on CFQDN
3 Call sent belle@example.com (not using Webex Teams)
Daisy
4 Call routed to Unified CM for belle@example.com
5 Call presented to device
Call Service Deployment
Call Control Identity/SSO DMZ DC An existing
Expressway C/E pair
used for B2B, MRA
(Calls are equal weight)
Management
Dedicated
Expressway-C
A dedicated Expressway C for Connectors

• Medium OVA template – 5000 users
• Large OVA template – 10000 users ucm1.example.com ucm2.example.com
Call Service Deployment
Guidelines &
Recommendations
Call Service Deployment Administration
Traversal Zone
Call Control Identity/SSO SIP Trunk
Cisco Webex
SIP Address
SIP Destination Expressway-E Expressway-C
Management
DNS Zone Neighbor Zone
Dedicated
Expressway-C
Very important step when DMZ DC

managing any users as
part of your organization!
Ability to edit Cisco Webex SIP Address
Cisco Webex Teams SIP Address editing caveat
Caveat:
There is no option for
Edit Subdomain when
Hybrid Call Service
Connect is enabled
Domain Verification – Adding a Domain
Call Service Connect Deployment
Call Service Connect hybrid service calls are classified the same as
MRA, B2B calls and traverse existing Expressway C&E pairs
• Note: There is no traversal license cost as *.ciscospark.com calls do not count
Call Service Connect follows existing MRA/B2B preferred

architecture planning recommendations
• Determine the total number of concurrent MRA, B2B, and Call Service Connect calls
• Deploy the appropriate number of Expressway E/C pairs
• There is no net new Expressway C or E required for Call Service Connect
Search rules, search rules, search rules
Expressway Configuration Requirements Stay
Current
• Configure a separate Traversal Zone on Expressway-C and Expressway-E Pair
─ When using a shared with B2B or MRA, a second set of search rules and neighbor zone is
required
• Enable Mutual TLS Authentication between Expressway-E & Collaboration Cloud

─ Port/ACL configuration for incoming connections on MTLS port (5062 is recommended)
• Configure DNS Zone on Expressway-E

─ Allows for routing of SIP Requests between On-Premises and Cloud
• Configure DNS Zone on Expressway-E

─ Expressway-E for Domain URI routing (customer unique)
─ Expressway-C has one inbound search rule per UCM cluster, and a single outbound search rule
• Neighbor Zones on Expressway-C per UCM cluster

─ Jabber MRA zones cannot be reused due to different listening port
─ Accept preloaded SIP Route headers with home cluster FQDN
UC Manager Configuration Requirements 10.5(2) SU5
Minimum
• Configure a SIP Trunk to Expressway-C
• Configure a SIP route pattern to route the appropriate domain via SIP Trunk
(*.ciscospark.com)
• Configure a Spark-RD containing the URI of user (directory URI)

─ A remote destination automatically created (i.e. daffy@cisco.calls.webex.com)
─ Spark-RD feature has the ability to anchor an incoming Trunk call under a line if the
incoming caller ID matches the configured Remote Destination (DN or URI).
• UC Manager FQDN home cluster routing capability is available with the appropriate
preloaded SIP Route header mapping.
• UC Manager AXL and CTI credentials are required when registering Expressway
Understanding CTI-RD versus Spark-RD
• With the following Unified CM releases there is a new device type … Spark-RD
• Unified CM 10.5(2) SU5, 11.0(1) SU3, and 11.5(1) SU3
• Call Service Connect works with CTI-RD today; however, CTI-RD counts against the
device count from a licensing perspective and will be eventually deprecated (timing
dependent)
• Even though the minimum version supported for Call Service is Unified CM 10.5(2) SU5
the device license counts for CTI-RD must be accounted for prior to the Spark-RD device
type being available in Unified CM versions listed above
• Spark-RD, when used without any associated UC device, will consume an enhanced user
license. Scenario is deploying softphones only via Spark-RD and no desk phones
• If using CTI-RD, there is a process to approve temporary licenses by a request to Global

Licensing Operations until full Spark-RD availability in the Unified CM versions listed above
Understanding Branding change impacts
• URLs – All the URLs are in place and enabled as of May 21, 2018
• Administration Portal
• Cisco Webex SIP Address is a name change from Cisco Spark SIP Address – Same functionality
• Call Service Connect – This is the biggest change as it involves changing the URIs used for call
routing, as well as various URLs for setup and configuration of the B2B SIP configuration. There
will be a step by step configuration document to walk through the steps required to adapt to the
rebranding changes. Existing setups will continue to work for a period of time through the
transition over time, and new setups will be able to use the new branding from the start.
Note: Hybrid Call Service Connect for users is moving towards a client calling integration
(timeframe is 1HCY19), while Webex Video Devices will continue to use the integration.
Calendar & Call Service Deployment - Dedicated
Collaboration Cloud Services
DMZ An existing
Call Control Identity/SSO DC
Expressway C/E pair
used for B2B, MRA
Management Calendar Dedicated
Expressway-C
cas1.example.com
A dedicated Expressway-C for the
combined Calendar & Call Connectors
• Large OVA template – 10000 users ucm1.example.com ucm2.example.com cas2.example.com
Calendar & Call Service Deployment - Existing
DMZ An existing
Call Control Identity/SSO DC
Expressway C/E pair
for B2B only
Management Calendar
cas1.example.com
An existing Expressway-C for the
combined Calendar & Call Connectors
• Small OVA template – 500 users
• Medium OVA template – 2000 users ucm1.example.com ucm2.example.com cas2.example.com
MRA support and larger scale being tested

Calendar & Call Service Deployment – Multi-Tenant
Call Control Identity/SSO DMZ DC
cas1.example.com
Management Calendar
ucm1.example.com ucm2.example.com cas2.example.com
An existing Expressway-C for the

combined Calendar & Call Connectors cas1.example2.com
• Small OVA template – 500 users Expressway-C

MRA support and larger scale being tested
ucm1.example2.com ucm2.example2.com cas2.example2.com
Hybrid Message Service Integration
Expressway
IM&P
Hybrid Message Service Control Hub
DMZ
Metrics &
Reporting
Future Service
Serviceability
Management
Connector
File Metadata
Connector
Connector
Connector
Connector
Connector
Message
Calendar
SIP Trunk
Call
XMPP
C
AXL / XMPP
RESTful https DC
Directory
Connector
Cisco Webex Teams / Jabber Interoperability - Presence
• When user is running Jabber, the user’s Presence on

Jabber shall be based on existing Jabber logic
• Available / Busy / Presenting / In meeting, etc.
• When user is not running Jabber, the user’s Presence

on Jabber shall be based on WebEx Teams activity
• “Available On WebEx Teams” when the user has
been active on WebEx Teams within the last 24
hours
• “Offline” when the user has not been active on
WebEx Teams for over 24 hours
Note: Webex Teams Presence is not impacted due to user’s Jabber activity
Cisco Webex Teams / Jabber Interoperability
• Cisco Webex Teams Interop will allow 1:1 message only between Jabber
and Webex Teams users.
• Users must be configured and enabled on both IM&P and Webex Teams
• Message Connector will map Jabber and the Webex Teams ID using a
common email address
• Notifications include isTyping, Message Read, Deletes, or Missed
• File transfer is not supported.
o When a Webex Teams user posts a file, Cisco Jabber will receive a notification to
get access to the file in the Webex Teams web client
What do I need to know?
Integrating On-Premises and Cloud
Google G Suite
Webex
Messenger
Expressway
Windows
Platform
Expressway - latest
Data
Microsoft AD Exchange Cisco UCM* IM&P Media Node
Security
Directory Connector
installed on a trusted
Windows Domain ?
Server 2003, 2008
R2, 2012, 2012 R2,
or 2016 as Exchange 2010 *Includes Business Edition or HCS
administrator SP3, 2013, 2016, Unified CM
and O365 supported 10.5(2)SU5 HCS10.6
Recommended firewall ports settings
Cisco Webex Teams
https://collaborationhelp.cisco.com/article/en-us/WBX000028782
Understanding Security Implications
• The Payment Card Industry (PCI) Security Standards Council has
recommended that organizations stop using Secure Socket Layer (SSL)
and Transport Layer Security (TLS) 1.0, and upgrade to TLS 1.2 as soon
as possible.
• Following this recommendation, Cisco Webex Teams no longer accepts
TLS 1.0 connections for Hybrid Call Service or over-the-top SIP cloud
calling, effective September 10, 2018. All attempts to negotiate
connections with TLS 1.0 will be rejected. Organizations must upgrade to
TLS 1.1 or, preferably, TLS 1.2 to continue using these services.
Connector Upgrades
Serviceability
Connector
Connector
Connector
Connector
Connector
Connector
Calendar
Message
Future
Mgmt
v001
v002
SIP Trunk
Call
XMPP
Expressway
Notification/Alerts Media/Transcoding C
Serviceability
Connector
Connector
Connector
Connector
Connector
Connector
Calendar
Message
Future
Mgmt
v001
v002
SIP Trunk
Call
XMPP
Metrics & Expressway
Reporting C
File Metadata
Storage Storage Billing & Common Connector Framework
Provisioning
Serviceability
Connector
Connector
Connector
Connector
Connector
Connector
Calendar
Message
Future
Mgmt
v002
v001
SIP Trunk
Call
XMPP
Expressway
C
Calendar Connector HA Capacity Guidelines
1 redundant pair
Small OVA 5,000 Users
Medium OVA 10,000 Users
Expressway-C for Connectors
Large OVA 15,000 Users
Calendar
Management 5+1 redundant model
A B
2 sites, 5+1 redundant model
Expressway-C for Connectors Expressway-C for Connectors
Call Connector HA Capacity Guidelines
1 redundant pair
Small/Med OVA 5,000 Users
Call
Management Redundant pair assignment
A B
2 sites, redundant pair assignment
Calendar & Call Connector HA Capacity Guidelines
1 redundant pair
Call
Management Redundant pair assignment
A B
2 sites, redundant pair assignment
Resources
• Getting Started: https://www.webex.com/
• Cisco Collaboration YouTube Playlist:
https://www.youtube.com/playlist?list=PL1D0EC047B2C903A1
• Network Requirements for Cisco Webex Teams:
https://collaborationhelp.cisco.com/article/en-us/WBX000028782
• Cisco Webex Hybrid Services: https://www.cisco.com/go/hybrid-services
• Cisco Webex Community:
https://communities.cisco.com/community/partner/collaboration/spark
• Knowledge Base Articles: https://collaborationhelp.cisco.com/
• Preferred Architectures & SRNDs: http://www.cisco.com/go/ucsrnd
Resources for Jabber Interoperability
• Jabber 12.5 Blog: https://blogs.cisco.com/collaboration/jabber-12-5
• Cisco Jabber: https://www.cisco.com/go/jabber
• Cisco Jabber Team Messaging Mode:
https://collaborationhelp.cisco.com/article/en-us/4217cz
• Webex Hybrid Message Service:
http://www.cisco.com/go/hybrid-services-message
Cisco Webex Teams
Questions?
Use Cisco Webex Teams (formerly Cisco Spark)
to chat with the speaker after the session
How
1 Find this session in the Cisco Events Mobile App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
cs.co/ciscolivebot#BRKCOL-2607
Complete your online
session survey
• Please complete your Online Session
Survey after each session
• Complete 4 Session Surveys & the Overall
Conference Survey (available from
Thursday) to receive your Cisco Live T-
shirt
• All surveys can be completed via the Cisco
Events Mobile App or the Communication
Stations
Don’t forget: Cisco Live sessions will be available for viewing

on demand after the event at ciscolive.cisco.com
Continue Your Education
Demos in Meet the Related

Walk-in
the Cisco engineer sessions
self-paced
Showcase labs 1:1
meetings
Thank you

Brkcol 2607

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Brkcol 2607

Uploaded by

Copyright:

Available Formats

BRKCOL-2607

Understanding Cloud and

At the end of the session, the participants will understand:

Messaging Meeting Calling

Application Integration Partner Services Cisco Webex Hybrid

3rd Party endpoints

Cisco Webex WebEx Cisco Video

Hybrid Directory Service

Cisco Webex platform

Creating unique value by connecting

Messaging Interop Content Sharing

*Includes Business Edition or HCS

 Simplified user provisioning and lifecycle management

 Enterprise Authentication via enterprise standard SAML

Messaging Interop Content Sharing

*Note: This is a net Common Connector Framework

Common Connector Framework

User Status Service

Users can use either @webex or @meet in a

@webex will backfill the users personal room

@meet or will utilize the Cisco Webex Teams

There are also modifiers :space and :myroom

Note: Due to the rebranding, changes

Exchange Web Services (EWS)

• EWS Subscription Group - Each group has one streaming subscription

• @webex functionality requires WBS31 or higher

• Deploying Calendar Service:

A dedicated Expressway C for Connectors

* Note: O365 capacity is 5000 users for both

Common Connector Framework

Messaging Interop Content Sharing

Common Connector Framework

Note: Consider leaving

Cloud Registered Room Device

*Includes Business Edition or HCS

1 Call initiated from Cisco Webex Teams to Donald

1 1 SIP URI dial from Webex Teams to belle@example.com

Daisy 3 Call routed to Unified CM for belle@example.com

Expressway-C Cluster Fully Qualified Domain

1 SIP URI dial from Webex Teams to belle@example.com

A dedicated Expressway C for Connectors

DNS Zone Neighbor Zone

Very important step when DMZ DC

Call Service Connect follows existing MRA/B2B preferred

Search rules, search rules, search rules

• Enable Mutual TLS Authentication between Expressway-E & Collaboration Cloud

• Configure DNS Zone on Expressway-E

• Configure DNS Zone on Expressway-E

• Neighbor Zones on Expressway-C per UCM cluster

• Configure a Spark-RD containing the URI of user (directory URI)

• Unified CM 10.5(2) SU5, 11.0(1) SU3, and 11.5(1) SU3

• If using CTI-RD, there is a process to approve temporary licenses by a request to Global

MRA support and larger scale being tested

ucm1.example.com ucm2.example.com cas2.example.com

An existing Expressway-C for the

• Medium OVA template – 2000 users

• When user is running Jabber, the user’s Presence on

• When user is not running Jabber, the user’s Presence

Expressway-C for Connectors

Expressway-C for Connectors

Don’t forget: Cisco Live sessions will be available for viewing

Demos in Meet the Related

You might also like