Brkcol 2356 Notes

1
Cisco Collaboration
Transitions
On-Premises, Hybrid, and Cloud
Matt Jordy, Technical Marketing Engineer - CTG

mjordy@cisco.com
BRKCOL-2356
2
Agenda
• Collaboration Design and Architecture Documentation
• Collaboration Transitions Program Introduction
» What are Collaboration Transitions?
» Collaboration Transitions Program
• Collaboration Transitions Validated Scenarios
» Meeting Scenarios ✓ Why Transition?
✓ Scenario Introduction + Decision
» Messaging Scenarios ✓ Transition Map
✓ Before Transition
✓ After Transition (What Changes, Workload Flow)
» Calling Scenarios ✓ Deployment Steps Overview
• Summary / Learn More
BRKCOL-2356 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
3
1/28/2020
BRKCOL-2356: Cisco Collaboration Transitions

Session Logistics
• Attendees should have some Please consult the most recent

familiarity with Cisco collaboration Collaboration Transition documents and
solutions. applicable product documentation for
the latest design guidance and specific
• Session time: 120 minutes feature, software version, and hardware
• Please ask questions as we go… version support requirements
• More questions?
Come see me after the session, send me an email, or Webex Teams

message (mjordy@cisco.com) with your question(s) and I will get back to you.
4
Cisco Webex Teams
Questions?
Use Cisco Webex Teams 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
5
Complete your
online session
survey • Please complete your session survey
after each session. Your feedback
is very important.
• Complete a minimum of 4 session
surveys and the Overall Conference
survey (starting on Thursday) to
receive your Cisco Live t-shirt.
• All surveys can be taken in the Cisco Events
Mobile App or by logging in to the Content
Catalog on ciscolive.com/emea.
BRKCOL-2356
Cisco Live sessions will be available for viewing on
demand after the event at ciscolive.com.
6
Collaboration
Design and
Architecture
Documentation
7
Collaboration Transitions
Preferred Architecture (PA) Document Framework
Preferred Supplemental Docs
Overview CVD
Architecture Add-ons,
alternate
Enterprise /
On-Premises + designs,
application
notes, etc.
PA Document
Framework Video Collaboration
includes Midmarket / Collaboration Transitions
On-Premises
Collaboration Voice Transition maps
& deployment
Transitions guides
Collaboration
Hybrid SRND
8
Where to Find Collaboration Design and Deployment Documentation
Preferred www.cisco.com/go/pa
Supplemental Docs
Overview CVD
alternate
Enterprise /
application
notes, etc.
PA Document
On-Premises
Collaboration Voice
www.cisco.com/go/ct
Transitions
Collaboration
Hybrid SRND
www.cisco.com/go/srnd
9
Program Introduction
Note: Collaboration Transitions was formerly known

as Mixed Cloud Premises (MCP)
10
Collaboration Transitions (CT)
Why Collaboration Transitions?
To move collaboration workloads within a deployment it is important to
know: How do you get from where you are to where you want to be?
MAP
Collaboration Transitions maps the transitions for Existing → Latest
existing deployments to move to the latest Cisco B
collaboration applications & services.

A
You ARE
HERE
A A + A
B B B
You WANT
On-Premises Hybrid Cloud to be HERE
11
What is Collaboration Transitions?
12
What is Collaboration Transitions?
New type of prescriptive, validated
deployment model…building on the existing
Collaboration Preferred Architectures (PA).
Deployment model focused on…TRANSITIONING

existing collaboration deployments to the
latest Cisco products and solutions
whether on-premises, hybrid, or cloud.
PROGRAM OBJECTIVE
Remove technical barriers for the existing customer base to ease the
transition of collaboration workloads to the latest Cisco collaboration solutions.
13
Collaboration Transitions Program
14
Lifecycle
Determine Workload
• Iterative validation of collaboration Transitions
workload transition scenarios to the Define transition validation
latest products and solutions scenarios
(on-prem, hybrid, cloud)
• Identification of gaps and barriers

hindering transition of
workload(s) to the latest on- Feedback Build and Validate
premises, hybrid, & cloud Share detailed gap report REPEAT Validate transitions in real
with product teams to Internet-connected test
solutions. improve products environment
• Publication of succinct customer
transition maps & deployment
guides to document the transition. Document Transition Identify Gaps
Paths Determine missing or
• Delivery of internal detailed gaps Create transition map(s) incomplete capabilities
list to product teams with steps required for preventing transition to
transitioning workloads newest offerings
15
Stakeholders
✓
IMPROVED
PRODUCTS
from
Collaboration Technology
→ Group (CTG) Engineering
+
✓
SHORTENED
CYCLES
for
→ Sales (PSS, SE, AM)
→ Support & Services (TAC, AS)
✓
INCREASED
by
→ Customers
→ Partners
ADOPTION
16
Transition Deltas and Challenges
• While differences across on-premises, hybrid, and cloud products and solutions are
to be expected…
• In some scenarios these deltas may present challenges during the transition of
workloads from one product / solution to another.
• These differences and challenges must be categorized in order to effectively report,
Outcomes
analyze, prioritize, and address.
DOCUMENT
Deltas / Challenges Categories
Working as
CTG Engineering designed?
» Administrator & User Experience
(configuration, user interface, etc.)
PRODUCT TEAMS FIX
» Management & Troubleshooting Defect?
(diagnostics, logging, etc.)
✓ Product Management
» Device Control & Monitoring ✓ Engineering /
» QoS & Bandwidth Management Development Enhancement?
ROADMAP
» Other (scheduling, directory, etc.) 17
BRKCOL-2356 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public
17
Outputs (1 of 2)
Three specific documentation outputs:
1. Transition Maps [Format: PDF]
Brief document illustrating the recommended steps for
transitioning from an existing collaboration deployment to
the latest products & solutions and the changes during
& after the transition:
a) Graphical transition maps illustrating the transition from start to finish
b) Summarized lists of benefits and differences between the
existing deployment and the transitioned deployment.
2. Deployment Guides [Format: PDF]

Provides technical background as well as deployment steps and considerations
for the transition from existing products & solutions to newer versions.
Documents published at: https://www.cisco.com/go/ct

• Also reachable via https://www.cisco.com/go/mcp (Mixed Cloud

Premises)
18
Outputs (2 of 2)
Three specific documentation outputs (cont.):
3. Update of existing collateral [Format: HTML, PDF, PPT, etc.]
As required…including: On-Premises and Hybrid PA documents (Overview
and CVD), Cisco Live sessions, etc.
19
Preferred Architecture (PA) Document Framework
Preferred Supplemental Docs
Overview CVD
alternate
Enterprise /
application
notes, etc.
PA Document
On-Premises
Collaboration Voice Transition maps
& deployment
Transitions guides
Hybrid Collaboration
SRND
20
Validated Scenarios
21
Validated Transition Scenarios
Available today at https://www.cisco.com/go/ct
✓ Meetings: Transitioning from TelePresence Server to Cisco Meeting Server
[On-premises ---> On-premises]
✓ Meetings: Transitioning from TelePresence Server / CMR-H Bridging to Cisco Webex

[On-premises / Hybrid –--> Cloud]
✓ Video Endpoints: Transitioning On-Premises Devices to Cisco Webex

[On-premises –--> Cloud]
✓ Messaging: Transitioning from IM&P / Webex Messenger to Jabber Team Messaging Mode
[On-premises / Hybrid ---> Hybrid / Cloud]
✓ Messaging: Transitioning from Distributed to Centralized Unified CM IM&P

[On-premises –--> On-premises]
In progress:
… Calling: Transitioning from Unified CM to Webex Calling
[On-premises ---> Cloud]
22
https://www.cisco.com/go/ct
23
24
25
Meetings Transitions
26
Meeting Transitions
Scenario #1:
TelePresence Server to
Cisco Meeting Server
27
Meetings: TelePresence Server to Cisco Meeting Server
Why Move to Cisco Meeting Server?
• Tightly integrated with the Cisco Collaboration portfolio for best user experience.
• Single on-premises solution for voice, video, and web conferencing
• Robust interoperability with Microsoft Skype for Business
• Consistent conferencing application user experience
» Cisco Meeting Application
» Cisco Jabber
• Simplified scheduling experience with @meet scheduling

• Join meetings from on-premise or cloud based endpoints
• Robust APIs provides the ability to customize the solution as required

• End of Support for TelePresence Server/Conductor is approaching (February 28,
2021)1
1 Cisco TelePresence Server/Conductor are end of life (see: https://www.cisco.com/c/en/us/products/collateral/conferencing/telepresence-server/eos-eol-
notice-c51-739457.html and https://www.cisco.com/c/en/us/products/collateral/conferencing/telepresence-conductor/eos-eol-notice-c51-739456.html
28
Scenario Introduction: Decision Tree
This scenario applies specifically to customers

transitioning to Cisco Meeting Server on-premises
meetings.
On-Premises
Consider carefully before making this transition if
you have requirements for: TelePresence
Server (TS)
» Meetings primarily in the cloud
» High touch white glove
• Zero touch meetings
Cisco
• Full meeting management
Cisco Webex
» Have large numbers of meetings Meeting Server
CLOUD
scheduled for the future
On-Premises *SCOPE
OUT OF
FOR
THIS SCENARIO
• Not supported without VQ Manager: One-time meeting passcodes, DTMF-

based in-call capabilities (access codes, recording PINs, etc. on other
conference systems), analytics including usage trends.
29
Mapping the Transition: Step 0 – TelePresence Server
0 1
TelePresence Server (TS) / Conductor Cisco Meeting Server
Cisco Meeting
TelePresence Server (CMS) /
Server (TS) / Meeting
Conductor Management
(CMM)
On-Premises Expressway MRA1 On-Premises Expressway MRA1

1 Expressway MRA is an optional feature.
30
0 Before – TelePresence Server/Conductor Deployment
On-premises meetings
Meeting1@example.com
TMS/TMSXE Conductor
& TS
Expressway
Call Control:
Unified CM or
Expressway
Video
Endpoints
31
Mapping the Transition: Step 1 – Cisco Meeting Server
0 1
TelePresence Server (TS) / Conductor Cisco Meeting Server
Cisco Meeting
TelePresence Server (CMS) /
Server (TS) / Meeting
Conductor Management
(CMM)
On-Premises Expressway MRA1 On-Premises Expressway MRA1

32
1 After – Cisco Meeting Server Deployment
Management: TMS
enables scheduling of Meeting URIs:
meetings and meeting Meeting1@example.com
resources.
…
Video conference resources:
Cisco Meeting Server (CMS) is the conference
Cisco Meeting TMS/ bridge for on-premises multi-point meetings
Cisco Meeting Management TMSXE
Management (CMM)
provides management Cisco Meeting Server
for meetings hosted Expressway
by CMS
Call Control:
Unified CM or
Expressway
Call control: Unified
CM (or Expressway) Enterprise Cloud Calendaring: Hybrid Connector 1
provide endpoint is the integration point for @meet scheduling.
registration and call
routing. Hybrid 1 Optional component. Deploy Expressway-C Connector
host(s) and Calendar Connector for cloud-based
Video Endpoints Connectors enterprise calendaring integrations (Google, O365)
33
1 After – Cisco Meeting Server Meetings Flow
CMM
TMS/TMSXE
CMS
Expressway
Video
Endpoints
Signaling (SIP)
Meeting URI:
Media (RTP/sRTP) Meeting1@example.com
34
Deployment Steps Overview
Pre-Transition steps: Transition steps (cont.):
1. Decide to maintain conferencing workload/service on-premises. 5. Distribute meeting client to end-users (Cisco
Meeting App or Cisco Jabber).
2. Acquire Cisco Meeting Server hardware, software, and licenses
(SMP, PMP).
3. Acquire/determine network information for LDAP and TMS.
4. Plan and prepare dial plan details for calling into Cisco
Meeting Server meetings and spaces. Post-Transition steps:
5. Acquire Cisco Meeting Management hardware and software. 1. Meeting experience customization (if desired)
2. Implement recording and streaming (if required)
Transition steps:
3. Enable @meet scheduling with O365 or Google
1. Deploy Cisco Meeting Server based on selected architecture
cloud calendar services (if desired)
(Combined Server v. Split Server).
4. Interoperation with Microsoft Skype (if required)
2. Prepare and deploy security certificates for appropriate Cisco
Meeting Server interfaces.
3. Deploy Cisco Meeting Management and integrate to Cisco
Meeting Server.
4. Transition existing scheduled conferences from the
TS/Conductor system to the new Cisco Meeting Server / Cisco
Meeting Management system.
• SMP = Shared Multi-Party

• PMP = Personal Multi-Party
35
Meeting Transitions
Scenario #2:
On-Premises Bridging1
to Cisco Webex
1 TelePresence Server (or CMR-Hybrid)
36
Meetings: Transitioning On-Premises Bridging to Cisco Webex
Why Move to Cisco Webex Meetings?
• Using Cisco Webex cloud-based video conferencing saves companies time and
money. Resources that would otherwise be expended to train IT teams to support
new on-premises systems.
• Constant upgrades happen automatically in the cloud keeping customers up to date
with the latest security fixes and features.
• Add web and audio-only capabilities to your video meetings
• Increased scale for meetings
• Ease of scheduling with keywords (e.g. @webex, using OBTP1)
• No change to user join (Webex clients get upgraded to the new application, but can
continue scheduling via the Outlook calendar)
• No change to endpoint administration and control
1 One Button To Push BRKCOL-2356 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 37
37
Scenario Introduction: Decision Tree
This scenario applies specifically to customers transitioning
to Cisco Webex cloud meetings.
On-Premises
Keep meetings on-premises* if
the requirements include: TelePresence
Server (TS)
» High touch white glove
• Zero touch meetings
• Full meeting management
» On-premises Microsoft interop Cisco Cisco
Meeting
» “No cloud” policy Server Webex
On-Premises CLOUD
* OUT OF
SCOPE FOR
THIS SCENARIO
38
Mapping the Transition: High-Level Transition Map
0 Cisco Video Deployment

1 Cisco Cloud Meetings
2 Cloud Registered Endpoints
OUT OF SCOPE FOR
THIS SCENARIO
TelePresence
Server (TS) Cisco
Cisco
Refer to the Video Webex
Endpoints:
On-Premises Registered to
Webex Webex Registered transition for
+ more information
[see next section]
Webex Edge Video

SCENARIO FOCUS Mesh Node1
1 Optional component.
39
Mapping the Transition: Step 0 – Cisco Video Deployment

OUT OF SCOPE FOR
THIS SCENARIO
TelePresence
Server (TS) Cisco
Cisco
Endpoints:
+ more information
[see next section]
Webex Edge Video

Mesh Node1
40
0 Before – On-Premises Meetings
On-premises meetings
TMS
Conductor
& TS
Expressway
Call Control:
Unified CM or
Expressway
Video
Endpoints
41
Mapping the Transition: Step 1 – Cisco Cloud Meetings

OUT OF SCOPE FOR
THIS SCENARIO
TelePresence
Server (TS) Cisco
Cisco
Endpoints:
+ more information
[see next section]
Webex Edge Video

Mesh Node1
1 Optional component.
42
1 After – Cisco Webex Cloud Meetings
On-premises resources:
Video Mesh Nodes (VMN)1
Enterprise Directory: provide local video
Directory Connector conferencing resources Cisco Webex cloud meetings
is the integration point
for user identity
TMS Video conference resources:
Video Webex is the conference bridge
Directory Mesh for multi-point meetings
Connector
Expressway
Cisco
Call Control:
Unified CM or
Webex
Expressway
Video endpoints: Webex Meeting URIs:

On-premises Meeting1@example.webex.com
registration with
Unified CM (or
Video Hybrid …
User2@example.webex.com
Endpoints Connectors
Expressway)
Enterprise Calendaring: Hybrid Connector 1 is
the integration point for @webex scheduling.
1 Optional components.
• Add Webex Edge for Devices to manage and get analytics for on-premises
registered endpoints (optional)
43
1 Cisco Webex Cloud Meetings Call Flow
Media travels to the Video Mesh nodes (VMNs) with
a cascade to Cisco Webex
OR
TMS/TMSXE Without VMN, media travels directly from endpoints to

Video Cisco Webex via the Expressway-C / Expressway-E
Mesh
Cisco
Webex
Meeting URI:
Signaling (SIP)
Expressway
Media Video
(RTP / sRTP) Endpoints
44
0 ALTERNATE TRANSITION: Before – CMR Hybrid
Video conference resources: TS Meeting URIs:

is the conference bridge for ad- Meeting1@xyz.com Video conference resources:
Cisco Webex is a scheduled
hoc/instant and scheduled on-
…
Meeting2@xyz.com
premises multi-point meetings conference bridge for multi-point
meetings
TMS
TelePresence
Server (TS)
Expressway
Cisco
Call Control:
Unified CM or Webex
Expressway
Webex Meeting URIs:

Meeting1@xyz.webex.com
Video
Endpoints …
Meeting2@xyz.webex.com
45
1 ALTERNATE TRANSITION: After – Cisco Webex Cloud Meetings
On-premises resources:
Video Mesh Nodes (VMN)1
Enterprise Directory: provide local video
Directory Connector conferencing resources Cisco Webex cloud meetings
is the integration point
for user identity
TMS Video conference resources:
Video Webex is the conference bridge
Directory Mesh for multi-point meetings
Connector
Expressway
Cisco
Call Control:
Unified CM or
Webex
Expressway
Video endpoints: Webex Meeting URIs:

On-premises Meeting1@example.webex.com
registration with
Unified CM (or
Video Hybrid …
User2@example.webex.com
Endpoints Connectors
Expressway)
Enterprise Calendaring: Hybrid Connector 1 is
the integration point for @webex scheduling.
1 Optional components.
46
1. Decide whether to move conferencing workload/service to the 7. Update end-user documentation and training material
cloud (Webex) (or keep on-premises (CMS)). for new scheduling architecture (OBTP, @webex,
Webex Meeting Desktop).
2. Acquire Cisco Webex Meeting contract and user licenses (Flex).
8. Phased transition of user groups to the Webex
3. Decide on whether Webex Edge Video Mesh is a requirement.
Meeting site.
4. Create new Cisco Webex site with latest release of software.
5. Decide on meeting scheduling (@meet, @webex, Webex
Meetings Desktop) and email integration (Microsoft, Google).
Post-Transition steps:
Transition steps:
1. Remove TS/Conductor from production (if desired)
1. Setup Cisco Webex site (new – activate / existing – site linking).
2. Disable CMR-H session type in Webex Site Admin at
2. Import users via Directory Connector (optional).
site and user level (if transitioning from CMR-H)
3. Enable single sign-on (SSO) (optional).
3. Monitor Webex Control Hub reports for analytics and
4. Setup scheduling environment. troubleshooting of meetings.
5. Begin scheduling meetings.
6. Install Webex Edge Video Mesh (optional).
47
Meeting Transitions
Scenario #3:
Video Endpoints: On-

Premises Registered to
Webex Registered
48
Video Endpoints: On-Premises to Cisco Webex
Why Move Endpoints to Cloud?
• Cisco Webex cloud-based endpoints reduce installation time and

operational costs. Savings could be used to further train IT staff, or for
future Cisco purchases.
• Automatic software updates simplify the operational process and minimize
time required to perform software upgrades for features and security
enhancements.
• Access to Webex Cloud-only features
» Whiteboarding in a Cisco Webex Meeting
» Webex Assistant – Voice Control
• Automatic Firmware Management

» Latest features and security fixes
49
Scenario Introduction: Decision
This scenario applies specifically to customers transitioning
to Cisco Webex cloud registered endpoints.
If any of the following are critical for your
deployment, carefully review all material,
before making this transition1:
Cisco
» Active Call Troubleshooting
Webex
» Auto Registration / Self-Provisioning
» WAN Bandwidth Optimization (CAC / ICE2)
On-Premises
» Far End Camera Control (FECC)
1 These items are under consideration for future releases, but have not yet been committed.
2 Call Admission Control (CAC), Interactive Connectivity Establishment (ICE).
50
Mapping the Transition: High-Level Transition Map

TelePresence
Server (TS) Cisco
Cisco
Webex
Webex
+
Webex Edge Video

Mesh Node
51
Mapping the Transition: Step 2 - Cloud Registered Endpoints

OUT OF SCOPE FOR
THIS SCENARIO
TelePresence
Server (TS) Cisco
Refer to the Meetings: Transitioning On-Premises

Cisco
Webex
Webex
Bridging to Cisco Webex transition for more
information +
[see previous section]
Webex Edge Video

Mesh Node
52
1 Before - On-Premises Video Endpoint Registration with Cisco Webex Meetings
TMS Video Mesh Node

Directory (optional)
Connector
Expressway
Call Control: Cisco

Unified CM or
VCS/Expressway-C Webex
Hybrid
Connectors
(optional)
Video Endpoints with
CE8.2+ Software1
1 Cisco always recommends running the latest build available on https://www.cisco.com/
53
2 After – Webex Cloud Registered Video Endpoints
Room/video system On-premises resources: Video

scheduling: TMS no Video Mesh Mesh Nodes (VMN) provides local
Directory2 for
longer required Node on-premises media processing.
Connector (optional)
cloud registered video
systems
Cisco
On-premises call control:
No longer required2 for Webex
cloud registered devices
Firewall traversal:
Expressway no longer required2
Video endpoints: Hybrid
for cloud registered devices
Cloud registration Connectors
(optional)
and management Video Endpoints
with Cisco Webex Enterprise Calendaring: Hybrid Connector
RoomOS software1
(@webex scheduling) only required if user
mailboxes remain on-premises.3
1 Cloud registered endpoints will run the latest generally available RoomOS.
2 Maintain on-premises call control, firewall traversal, and scheduling services as required for any devices continuing to consume on-premises services.
3 For cloud mailboxes, a cloud connector would be leveraged instead. BRKCOL-2356 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 54
54
2 Webex Cloud Video Endpoint Registration Call Flow
Video Mesh Node

(optional)
Video Endpoints Cisco

RoomOS Software Webex
Signaling (SIP) Note: Expressway firewall traversal technologies not required for
this workflow. Endpoint signaling and media travel directly to
Media cloud (or to Video Mesh Node if deployed).
OR
(RTP/sRTP)
55
Pre-Transition steps:
1. Create new Cisco Webex site with latest release of software.
2. Decide on whether Webex Edge Video Mesh is a requirement.
3. Verify quantity of available Webex Device licenses and acquire
more if required.
4. Remove devices to be transitioned from on-premises call
control (Unified CM or Expressway).
5. Remove devices from on-premises management (TMS).
1. Managing devices and view analytics on Webex
6. Factory reset devices to be transitioned (recommended). Control Hub.
Transition steps:
1. Setup Cisco Webex site (new – activate / existing – site linking).
2. Import users via Directory Connector (optional).
3. Enable single sign-on (SSO) (optional).
4. Add devices to Webex Control Hub.
5. Install Webex Edge Video Mesh (optional).
Note: Grey steps above covered with previous transition (Meetings: TS to Webex)
56
Messaging Transitions
57
Scenario #4:
Jabber IM&P to Jabber

Team Messaging Mode
58
Messaging: Transitioning to Jabber Team Messaging Mode
Jabber Team Messaging is Flexible & Delivered Seamlessly
• Jabber Team Messaging mode allows an organization to move their messaging
workload from on-premises to the cloud-based Cisco Webex Teams platform.
• Delivers the same recognizable Jabber user experience making the transition
seamless for existing end users.
• Maintains the same Unified CM calling feature set with no loss of calling functionality.
• Fully supported with VDI deployments of Jabber.
• Meeting workload remains the same whether hosted on-premises (for example,
Cisco Meeting Server) or in the cloud (for example, Cisco Webex Meetings).
• Persistent messaging with file sharing: 1:1 and Spaces
• Reduced total cost of ownership (TCO) (No requirement for on-premises Unified CM IM&P
services nodes, no need for external database / file servers for persistent chat.)
• Instant global federation with other Webex Teams organizations

59
This scenario applies specifically to
On-Premises
transitioning Jabber messaging workload
from on-premises Unified CM IM&P Unified
Unified CM
to Webex Teams. CM
IM & Presence
Do not make the transition if you have these requirements:
CALLING
» Very strict compliance requirements MESSAGING /
PRESENCE
• Pre-delivery message blocking
CALLING
• Ethical firewalls
• FIPS1 mode
MESSAGING /
» B2B federation with third-party messaging service PRESENCE
Webex
» Intradomain federation with Microsoft
Cloud Cisco Teams
» Heavy use of Jabber IM only mode desktop share
Webex
1
Federal Information Processing Standards
60
Mapping the Transition: Step 0 – Jabber IM&P Messaging
0 1
Cisco Jabber w/ Unified CM IM&P Cisco Jabber Team Messaging Mode
Unified CM
IM&P
On-Premises
Expressway
MRA
On-Premises Expressway Webex Cisco

MRA1 Teams
Webex

61
0 Before – Cisco Jabber On-Premises Messaging
Unified CM IM&P Expressway-C/E
Directory
LDAP
Direct
MRA1
Unified CM
Jabber
Clients

62
Mapping the Transition: Step 1 – Jabber Team Messaging
0 1
Cisco Jabber w/ Unified CM IM&P Cisco Jabber Team Messaging Mode
Unified CM
IM&P
On-Premises
Expressway
MRA1
On-Premises Expressway Webex Cisco

MRA Teams Webex

63
1 After – Cisco Jabber Team Messaging Deployment
Directory: Corporate users synchronized1 Cloud Messaging & Presence: Webex Teams
between Active Directory and Unified CM. service provides HTTPS/REST-based messaging,
presence and contact list services for Jabber
Unified CM IM&P 3 Expressway-C/E
Webex
Active Teams
Cisco
Directory
LDAP
Webex
Direct
MRA
Unified CM
Jabber
Call Control: Unified CM Clients Firewall Traversal: Expressway-E/C
continues to provide client provides Mobile and Remote
registration and call routing Access (MRA) firewall traversal2
for external Jabber client calling
1 Directory synchronization at Unified CM is optional. Users may also be manually created/imported.
2 Remote connectivity is an optional feature. VPN could also be used for remote connections
3 In case of phased migration, Unified CM IM&P service nodes are removed after all Jabber users have been transitioned to Team Messaging.
64
1 After – Cisco Jabber Team Messaging Flow
Unified CM IM&P Expressway-C/E

Webex
Active Teams
Cisco
Directory
Webex
Direct Direct
MRA2
Unified CM
Jabber
Clients
Call Control – SIP Directory – LDAP
(registration, call (contact search)
routing)
Messaging – HTTPS Directory Sync –
(messaging, presence) LDAP1
1 No direct synchronization between Active Directory and Webex, Directory Connector required (or manual bulk entry at Webex Control Hub).
2 Expressway MRA flow is optional.
65
ALTERNATE TRANSITION: Webex Messenger to Team Messaging
0 1
Cisco
CiscoJabber
Jabberw/
w/Webex
UnifiedMessenger
CM IM&P Cisco Jabber Team Messaging Mode
Unified CM
IM&P
On-Premises On-Premises
Expressway Expressway
MRA1 MRA1
On-Premises
Webex
Cisco Expressway Webex Cisco
Messenger MRA1
Webex Teams Webex

66
ALTERNATE TRANSITION: Webex Messenger to Team Messaging
0 1
Cisco Jabber w/ Webex Messenger Cisco Jabber Team Messaging Mode
On-Premises On-Premises
Expressway Expressway
MRA1 MRA1
Webex
Cisco
Messenger Webex Cisco
Webex Teams Webex

67
0 ALTERNATE TRANSITION: Before - Cisco Jabber Webex Messenger
Cloud Messaging & Presence: Webex Messenger
service provides XMPP-based messaging,
Directory: Corporate users presence and contact list services for Jabber
synchronized1 between LDAP
directory and Unified CM. Expressway-C/E
Webex
Active Messenger
Cisco
Directory
LDAP
Webex
Direct
MRA
Unified CM
Jabber
provides client registration provides Mobile and Remote
and call routing. Access (MRA) firewall traversal2

68
1 ALTERNATE TRANSITION: After – Cisco Jabber Team Messaging Deployment
Cloud Messaging & Presence: Webex Teams
Directory: Corporate users service provides HTTPS/REST-based messaging,
synchronized1 between LDAP presence and contact list services for Jabber
directory and Unified CM. Expressway-C/E
Webex
Active Teams
Cisco
Directory
LDAP
Webex
Direct
MRA
Unified CM
Jabber
provides client registration provides Mobile and Remote
and call routing. Access (MRA) firewall traversal2

69
1. Acquire Flex licensing required for Jabber team messaging mode.
2. Acquire a Cisco Webex Teams organization in order to access
Webex Control Hub for Jabber team messaging configuration.
3. Link Webex Messenger and Webex Teams (if transitioning from
Webex Messenger). Post-Transition steps:
4. Ensure you understand Jabber team messaging authentication 1. Remove unused Unified CM IM&P clusters.
(SSO recommended), service discovery, directory integration 2. Remove unused database and file servers.
and contact lists.
3. Contact the Cisco Webex Ops team to delete the
Transition steps: Webex Messenger site and data (if transitioning
1. Enable Jabber team messaging mode for Webex Teams from Webex Messenger).
organization.
2. Enable Jabber team messaging mode for users.
3. Initial service discovery and first-time connection to Webex
Teams messaging service.
4. Contact migration (if required by administrator configuration).
5. Jabber calling with Unified CM discovery (if enabled by administrator)
• Pre-transition step 3: Linking Webex Messenger and Webex Teams = “CI

enabling the Messenger org”
70
Scenario #5:
Distributed to Centralized
Unified CM IM&P
71
Messaging: Transitioning to Centralized Unified CM IM&P
Centralized IM&P Reduces Cost and Simplifies Management
• Centralized Unified CM IM&P deployments reduce cost because Unified
CM IM&P servers do not need to be installed at every site that requires
messaging and presence services.
• Deployment flexibility for multi-cluster environments
» Version independence between Unified CM IM&P and Unified CM telephony clusters.
» 1:many cluster ratios allowing a single IM&P cluster for multiple telephony clusters.
• Eliminates Unified CM IM&P inter-clustering mitigating issues caused by

inter-site high-latency, low-bandwidth links.
• No change to user messaging and presence experience (Jabber clients
continue to consume the Unified CM IM&P services)
• No change to Jabber client administration and control
72
This scenario applies specifically to transitioning from
distributed to centralized Unified CM IM&P deployments.
Multiple distributed Single centralized
Consider carefully before making Unified CM IM&P clusters Unified CM IM&P cluster
this transition if your deployment

includes:
» Persistent chat
» Compliance with a third-party
compliance solution
» Federation
» Requirement to remain on a version
earlier than 11.5(1)SU5
» Requirement for phone line status
without relying on Jabber clients
73
Mapping the Transition: Step 0 – Distributed IM&P
0 1
Unified CM IM&P Distributed Unified CM IM&P Centralized
Unified CM IM&P / Unified CM Unified CM IM&P
Unified CM
...
...
On-Premises Expressway On-Premises Expressway

MRA1 MRA1

74
0 Before – Unified CM IM&P Distributed Messaging
Call Control: Messaging:

Unified CM Unified CM IM&P Expressway-C/E1
… Cluster n
Cluster 2
… …
Cluster 1
Jabber
Clients
1 Remote connectivity is an optional feature. VPN can also be used for remote connections.
75
Mapping the Transition: Step 1 – Centralized IM&P
0 1
Unified CM IM&P Distributed Unified CM IM&P Centralized
Unified CM IM&P / Unified CM Unified CM IM&P
Unified CM
...
...
On-Premises Expressway On-Premises Expressway

MRA1 MRA1

76
1 After – Unified CM IM&P Centralized Messaging
Multi-site / multi-cluster call control:

Multiple Unified CM clusters for
Firewall traversal: Expressway MRA
required capacity and/or geographic
provides secure remote connectivity
distribution
for remote Jabber users1
Call Control: Expressway-C/E
Unified CM
Cluster n
… Messaging:
Unified CM IM&P
Cluster 2 CENTRALIZED CLUSTER … …
Cluster 1
Jabber clients: Jabber

continues to consume
On-premises messaging / on-premises messaging /
Jabber
presence: Single2 centralized presence (and call control)
Clients
Unified CM IM&P cluster. services.
1 Remote connectivity is an optional feature. VPN can also be used for remote connections.
2 It is possible to have multiple centralized Unified CM IM&P clusters. BRKCOL-2356 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 77
77
1 After – Unified CM IM&P Centralized Messaging Flow
Call Control: Expressway-C/E1

Unified CM
Cluster n
… Messaging:
Unified CM IM&P
Cluster 2 CENTRALIZED CLUSTER … …
Cluster 1
Call Control – SIP

Jabber (registration, call routing)
Clients
Messaging – XMPP
(messaging, presence)
78
1. Verify that all Jabber clients can log in and control both soft and 4. Enable and start required services on the centralized
physical phones and access voicemail. Unified CM Publisher and Unified CM IM&P nodes.
2. Determine centralized Unified CM IM&P equipment location. 5. Configure SSO and OAuth with Refresh Token as
appropriate for your environment (optional).
3. Decide whether you intend to deploy new hardware OR promote
existing hardware as the centralized Unified CM IM&P cluster. 6. Configure an AXL connection between the
centralized IM&P and all remote leaf voice clusters
4. Use the Unified CM IM&P BAT to export users’ contact lists so
(synchronizes private encryption keys)
that you can restore their lists to the centralized Unified CM
IM&P cluster. 7. Define appropriate service profiles, feature group
templates, and UC services on all publishers.
5. Perform DRS backup plan for disaster recovery in case
something goes wrong during the transition. 8. Deactivate IM&P feature services and stop XCP
router on all Unified CM IM&P nodes except for the
Transition steps: centralized cluster.
1. Upgrade all existing Unified CM and IM&P clusters to release 9. Perform a full LDAP sync and then use BAT to update
11.5(1)SU5 or later at all locations user' Service Profile and users' contact lists to
2. Upgrade Jabber clients to version 12.0 or later. centralized Unified CM IM&P (via BAT).
3. Deploy new hardware for the centralized Unified CM IM&P 10. For Expressway MRA deployments, update Unified
cluster OR promote existing cluster for the role of centralized CM and Unified CM IM&P server nodes on
Unified CM IM&P cluster. Expressway-C to account for cluster changes.
79
Deployment Steps Overview (cont.)
1. Remove unused Unified CM IM&P clusters.
2. Configure interclustering with other Unified CM IM&P clusters
from sites that will not leverage centralized Unified CM IM&P (if
required).
80
Calling Transitions
81
** WORK IN PROGRESS **
Content in this section is
SUBJECT TO CHANGE
Calling Transitions
Scenario #6:
Unified CM Calling to
Webex Calling
82
Calling: Transition from Unified CM to Webex
Webex Calling Reduces Cost & Simplifies Management?
• Reduced total cost of ownership (TCO)

» No requirement for on-premises Unified CM service nodes.
» No IT management resources required to maintain & support
on-premises calling system.
• Easy to maintain
» Easier control for IT through simple web portals
» Automatic continuous upgrades in the cloud ensure deployment is up
to date with the latest security fixes and features, further reducing
burden on IT management.
83
Why Move to Webex Calling?
• Built for a mobile workforce enabling anywhere, anytime calling
Cloud calling enables global reach without costly distributed on-premises infrastructure.
Further, Universal availability of Internet bandwidth allows users at any location to make
calls over their local Internet connection reducing enterprise network bandwidth
consumption
• Increased scalability and resilience
Webex calling provides for larger scale deployments with greater reliability and security
than on-site calling deployments.
• Speed of innovation
Cloud features are delivered faster without requirement for maintenance windows or
complex upgrade processes
• Encrypted secure calling delivered on carrier-grade cloud infrastructure
With global regulatory expertise and compliance across all markets served, Webex cloud
platform implements audited, professional security practices.
84
This scenario applies specifically to transitioning from on-
premises Unified CM to Webex Calling deployments.
If any of the following are critical for
your deployment, carefully review all
material before making this transition:
» Phone models other than Cisco 7800 Unified Webex
and 8800 IP phone series CM Calling
» Complex or numerous integrations with Cisco
other on-premises systems / solutions Webex
» Complex dial plan and/or highly granular
classes of service
» Restrictive or limited Internet access
» Stringent data privacy and data
ownership policies
ON-PREMISES CLOUD
85
Mapping the Transition: Step 0 – Unified CM Calling
0 Unified CM Calling
1 Unified CM + Webex Calling 2 Webex Calling1
Cisco Cisco
Webex Webex
1 Video endpoints register to WebexTeams platform, not Webex Calling.

86
0 Before – Unified CM On-Premises Calling
Cisco Meeting TMS / Cisco Meeting

Management TMSXE Server
Expressway1
(MRA & B2B)
Unified
CM
ON-PREMISES REMOTE (MRA)1
1 Expressway MRA/B2B is an optional feature.

87
Mapping the Transition: Step 1 – Unified CM + Webex Calling
1 Unified CM + Webex Calling 2 Webex Calling
Cisco Cisco
Webex Webex
88
1 After – Unified CM and Webex Calling
Users: Directory On-Premises Call Control: Cloud Call Control: Webex Calling
Cisco Meeting
Unified CM TMS /
continues to Meeting
Cisco provides registration and call routing
Connector is the Management TMSXE
provide registration and Server
call for desk phones2 and Webex Teams.
integration point for
cloud user identity routing for some endpoints. Expressway1
(MRA & B2B)
Unified Cisco
CM Webex
Endpoints: Some PSTN: Local Gateway Cloud Endpoints: Some

hardware endpoints and (IOS-XE) for PSTN access for Remote Endpoints: Some hardware endpoints
Jabber continue to use cloud-registered endpoints. hardware endpoints and and Webex Teams use
Unified CM calling. Jabber continue to connect to Webex Calling.
1 Expressway MRA is an optional feature. Unified CM calling over MRA1.
2 7800 and 8800 series only
89
1 After – Unified CM and Webex Calling Flow
Expressway1
(MRA & B2B)
Unified Cisco
CM Webex
Unified CM Calling – SIP Webex Calling – HTTPS

Call Media – RTP/sRTP
(registration, call routing) (registration, call routing)
90
Mapping the Transition: Step 2 – Webex Calling
1 Unified CM + Webex Calling 2 Webex Calling1
Cisco Cisco
Webex Webex
1 Video endpoints register to WebexTeams platform, not Webex Calling.

91
2 After – Webex Calling Cloud Connected PSTN (CCP) (and/or Local Gateway)
for PSTN access for cloud-registered endpoints.
Decommission On- Cisco Meeting TMS / Cisco Meeting
Premises Call Control:
Management TMSXE Server Decommission Firewall Traversal:
Unified CM calling no Expressway is no longer required
Expressway
longer required1 (MRA & B2B) for cloud-registered endpoints1 PSTN
Unified Cisco
CM Webex
Remote Endpoints: Desk

On-Premises Endpoints: Desk Local Gateway (IOS) (and/or CCP) for PSTN endpoints2 and Webex
endpoints2 and Webex Teams3 use access for cloud-registered endpoints. Teams3 use Webex Calling.
Webex Calling. Video endpoints4 Video endpoints4 use
use Webex Teams platform. 1 Maintain on-premises call control & 2 7800 and 8800 series only Webex Teams platform
firewall traversal as required for any 3 Webex Teams replaces Jabber software client.
devices not migrated to cloud
calling.
4 Video endpoints running CE code.
92
2 After – Webex Calling Flow
Expressway
(MRA & B2B) PSTN
Unified Cisco
CM Webex
PSTN
Webex Calling – HTTPS Webex Device – HTTPS

Call Media – RTP/sRTP
(registration, call routing) (registration, call routing)
93
COMING SOON
Transition steps:
COMING SOON
COMING SOON
94
Summary / Learn More
95
Summary
• Program purpose: Remove technical barriers for the existing customer base to ease the
transition of collaboration workloads to the latest Cisco collaboration solutions.
• Delivers a new type of prescriptive, validated deployment model, built upon the existing
Collaboration Preferred Architectures (PA) framework.
• Addresses the transfer of collaboration workloads FROM existing products and solutions
TO the latest versions.
• Provides a map for transitioning customers and partners to the latest services and
solutions.
• Improves solution by closing the feedback loop with product teams and providing iterative
validation of transitions.
• Validation / adoption scenarios covering meeting, video endpoint, messaging, and calling
transitions.
96
Next Steps and Where to Go For More Information
Collateral and publication location:

• Transition map(s)
• Deployment Guides
• Available at https://www.cisco.com/go/ct →
✓ Meetings: Transitioning from TelePresence Server to Cisco Meeting Server
✓ Meetings: Transitioning from TelePresence Server / CMR-H Bridging to Cisco Webex
✓ Video Endpoints: Transitioning On-Premises Devices to Cisco Webex
✓ Messaging: Transitioning from IM & P / Webex Messenger to Jabber Team Messaging Mode
✓ Messaging: Transitioning from Distributed to Centralized Unified CM IM & P
• Coming soon:
» Calling: Transitioning from Unified CM to Webex Calling
97
What’s Next?
Additional transitions under consideration:
• Meetings:
» Cisco Meeting Server to Cisco Webex
» Cisco Webex Meeting Server to Cisco Meeting Server ** SUBJECT TO CHANGE **
• Calling: Cisco may NOT

document these
» Cisco IP Communicator to Cisco Jabber
transitions
» Cisco Unified CM / BExK to Cisco HCS (or Unified CM Cloud)
» Endpoints: Cisco Immersive to Cisco Webex Room Kit (or Webex Panorama)
What
.. Weelse?
. would like to hear from you!!
98
Cisco Webex Teams
Questions?
Use Cisco Webex Teams to chat
with the speaker after the session
How
1 Find this session in the Cisco Events Mobile App WEBEX TEAMS
2 Click “Join the Discussion”

3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
99
Complete your
online session
survey • Please complete your session survey
after each session. Your feedback
is very important.
• Complete a minimum of 4 session
surveys and the Overall Conference
survey (starting on Thursday) to
receive your Cisco Live t-shirt.
• All surveys can be taken in the Cisco Events
Mobile App or by logging in to the Content
Catalog on ciscolive.com/emea.
Cisco Live sessions will be available for viewing on

demand after the event at ciscolive.com.
100
Continue your education
Demos in the
Walk-In Labs
Cisco Showcase
Meet the Engineer

Related sessions
1:1 meetings
101
Continue your education Demos in the
Cisco campus
Cloud Meetings: Webex
Prem Meetings: CMS

Cloud Calling: Webex Calling
Journey to the Cloud
Collab Flex / Webex Adoptions

World of Solutions
102
Continue your education
• BRKCOL-1793 Cisco Webex Calling Overview

[Wednesday, January 29, 12:15 – 13:15]
• BRKCOL-2221 Cisco Jabber – Have you Heard About the Latest Functionality?
[Thursday, January 30, 14:45 – 16:15]
• BRKCOL-2004 Technical Overview of the Journey to the Cloud for On-Premises

Video Deployments
[Friday, January 31, 9:00 – 10:30]
• BRKCOL-2602 Migrating your Existing Jabber Deployments to the Cisco

Collaboration Cloud
[Friday, January 31, 9:00 – 11:00]
• BRKCOL-2792 Cisco Webex Calling Design and Deployment

[Friday, January 31, 9:00 – 11:00]
Also might want to review:
BRKCOC-2997 Cisco IT: Migration of On-Prem (UCM) Video Endpoints to the Cloud (Webex) Platform
103
Thank you
104
105

Brkcol 2356 Notes

Uploaded by

Document Information

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 2356 Notes

Uploaded by

Copyright:

Available Formats

1

Matt Jordy, Technical Marketing Engineer - CTG

• Summary / Learn More

BRKCOL-2356: Cisco Collaboration Transitions

• Attendees should have some Please consult the most recent

Come see me after the session, send me an email, or Webex Teams

Note: Collaboration Transitions was formerly known

existing deployments to move to the latest Cisco B

collaboration applications & services.

Deployment model focused on…TRANSITIONING

• Identification of gaps and barriers

2. Deployment Guides [Format: PDF]

Documents published at: https://www.cisco.com/go/ct

• Also reachable via https://www.cisco.com/go/mcp (Mixed Cloud

✓ Meetings: Transitioning from TelePresence Server / CMR-H Bridging to Cisco Webex

✓ Video Endpoints: Transitioning On-Premises Devices to Cisco Webex

✓ Messaging: Transitioning from Distributed to Centralized Unified CM IM&P

• Simplified scheduling experience with @meet scheduling

• Robust APIs provides the ability to customize the solution as required

This scenario applies specifically to customers

• Not supported without VQ Manager: One-time meeting passcodes, DTMF-

On-Premises Expressway MRA1 On-Premises Expressway MRA1

On-Premises Expressway MRA1 On-Premises Expressway MRA1

• SMP = Shared Multi-Party

1 TelePresence Server (or CMR-Hybrid)

0 Cisco Video Deployment

[see next section]

Webex Edge Video

0 Cisco Video Deployment

[see next section]

Webex Edge Video

0 Cisco Video Deployment

[see next section]

Webex Edge Video

Video endpoints: Webex Meeting URIs:

TMS/TMSXE Without VMN, media travels directly from endpoints to

Video conference resources: TS Meeting URIs:

Webex Meeting URIs:

Video endpoints: Webex Meeting URIs:

Video Endpoints: On-

• Cisco Webex cloud-based endpoints reduce installation time and

• Automatic Firmware Management

0 Cisco Video Deployment

Webex Edge Video

0 Cisco Video Deployment

Refer to the Meetings: Transitioning On-Premises

Webex Edge Video

TMS Video Mesh Node

Call Control: Cisco

1 Cisco always recommends running the latest build available on https://www.cisco.com/

Room/video system On-premises resources: Video

Video Mesh Node

Video Endpoints Cisco

Jabber IM&P to Jabber

• Instant global federation with other Webex Teams organizations

On-Premises Expressway Webex Cisco

1 Expressway MRA is an optional feature.

Unified CM IM&P Expressway-C/E

1 Expressway MRA is an optional feature.

On-Premises Expressway Webex Cisco

1 Expressway MRA is an optional feature.

Unified CM IM&P Expressway-C/E

1 Expressway MRA is an optional feature.

1 Expressway MRA is an optional feature.