Messaging: Transitioning from Unified CM IM&P / Webex ... · CTG Technical Marketing Engineering Team. Messaging: Transitioning from Unified CM IM&P / Webex Messenger to Jabber Team

CTG Technical Marketing Engineering Team

Messaging:

Transitioning from Unified CM IM&P / Webex Messenger to Jabber Team Messaging

Updated: January 22, 2020

COLLABORATION TRANSITIONS

© 2020 Cisco – CTG TME. Collaboration Transitions – Messaging: IM&P / Webex Messenger to Jabber Team Messaging

Scenario Introduction ................................ 3Decision TreeOverviewArchitectureScope

Mapping the Transition .............................. 9High-Level Transition MapStep 0: Cisco Jabber On-Premises Messaging Deployment

Cisco Jabber On-Premises Messaging FlowStep 1: Cisco Jabber Team Messaging

What Changes w./ Jabber Team MessagingAfter: Cisco Jabber Team MessagingCisco Jabber Team Messaging Flow

Why Move to Cisco Jabber Team Messaging?What is Different when Moving to Jabber Team Messaging?Considerations: Compliance

Federation and Presence ModelDesktop Share and Contact List

References .............................. 25

Alternate Transition: Webex Messenger to Team Messaging …………........... 27

Step 0: Before – Cisco Jabber w/ Webex MessengerStep 1: After - Cisco Jabber Team MessagingReferences: Webex Messenger to Jabber Team Messaging

Contents

2


Collaboration Transitions

Messaging: Transitioning to Jabber Team Messaging Mode

Scenario Introduction

3


This scenario applies specifically to transitioning Jabber messaging workload from on-premises Unified CM IM&P to Webex Teams.

Messaging: Transitioning to Jabber Team Messaging ModeScenario Introduction: Decision

Do not make the transition if you have these requirements:» Very strict compliance requirements

• Pre-delivery message blocking• Ethical firewalls• FIPS1 mode

» B2B federation with third-party messaging service» Intradomain federation with Microsoft» Heavy use of Jabber IM only mode desktop share

4

Unified CM IM & Presence

On-Premises

WebexCiscoCloud

Webex Teams

MESSAGING / PRESENCE

CALLING

MESSAGING / PRESENCE

UnifiedCM

CALLING

1 Federal Information Processing Standards


Messaging transitions scenario covering transition from an on-premises to cloud messaging service

Scenario Objective

• To evaluate the transition FROM traditional on-premises Cisco Unified CM IM & Presence (IM&P)1 TO cloud-based Cisco Webex Teams.

• To explore the messaging solution transition with a focus on:

» User experience: Messaging features and functions.

» Administrative experience: Provisioning, management, and troubleshooting.

Messaging: Transitioning to Jabber Team Messaging ModeScenario Introduction: Overview

5

1 For transitions from Cisco Webex Messenger, refer to the Alternate Transitions: Webex Messenger to Teams Messaging section near the end of this document.

MESSAGINGWebexCisco

On-Premises Cloud


Messaging: Transitioning to Jabber Team Messaging ModeScenario Introduction: Base Architecture

» Architecture based on the Enterprise On-Premises Preferred Architecture (version 12.x).

» Messaging deployment with on-premises Unified CM IM&P.

» Directory for corporate identity (Active Directory).

» Jabber clients register to on-premises Unified CM call control.

» Expressway-C/E pairs for firewall traversal: Clients connect to on-premises services directly or optionally through Expressway.

Expressway-C/E

Jabber Clients

MRA

Direct

Messaging: Unified CM IM&P

Call Control: Unified CM

Directory

6


Messaging: Transitioning to Jabber Team Messaging ModeJabber Team Messaging Target Architecture – Detail

Webex

Jabber

On-Premises

Unified CM Unity Connection

MessagingContacts/Directory Meetings

LDAP/UDS

Directory Contacts Messaging Meetings Calling VoicemailSCENARIO FOCUS

7


• Messaging resources are moved from on-premises (Unified CM IM&P) to cloud hosted (Cisco Webex Teams Messaging).

• Only features and functions for on-premises1 messaging deployment were evaluated with the Cisco Jabber Team Messaging mode solution. (Phone mode is not part of this scope).» 80/20 Rule: It is expected that this scenario will be applicable to ~80% of customers,

understanding that ~20% of customers may have additional considerations or requirements not covered. However, even in those cases, this transition map may still be used as a potential future transition path.

• Only Cisco Jabber (desktop and mobile) was evaluated.» All clients remain registered to on-premises call control: Unified CM.

» Cisco Webex Teams clients are not considered for this scenario.

Messaging: Transitioning to Jabber Team Messaging ModeScenario Introduction: Scope

8

1 Or cloud messaging in the case of Webex Messenger – see the Alternate Transition: Webex Messenger to Team Messaging section at the end of this document.




Mapping the Transition

9


Messaging: Transitioning to Jabber Team Messaging ModeMapping the Transition: High-Level Transition Map

Note: This map is a visual representation of the workload transition(s), highlighting the primary architectural changes during the deployment.

Cisco Jabber w/ Unified CM IM&P 0

Cisco Jabber Team Messaging Mode1

WebexCiscoWebex

Teams

ExpresswayMRA1

On-Premises

1 Expressway MRA is an optional feature.

ExpresswayMRA1

On-Premises

Unified CMIM&P

10


Messaging: Transitioning to Jabber Team Messaging ModeMapping the Transition: Step 0 – Jabber IM&P Messaging



WebexCiscoWebex

Teams

ExpresswayMRA

On-Premises

Note: This map is a visual representation of the workload transition(s), highlighting the primary architectural changes during the deployment.1 Expressway MRA is an optional feature.

ExpresswayMRA1

On-Premises

Unified CMIM&P

11


Expressway-C/E

Jabber Clients

Direct

Unified CM IM&P

Unified CM

Directory

Messaging: Transitioning to Jabber Team Messaging ModeCisco Jabber On-Premises Messaging Deployment

Call Control: Unified CM provides client registration and call routing.

Messaging & Presence: Unified CM IM & Presence (IM&P) provides XMPP-based messaging, presence and contact list services for Jabber

0

12

Firewall Traversal: Expressway-E/Cprovides Mobile and Remote Access (MRA) firewall traversal2 for remote Jabber clients

LDAP

Directory: Corporate users synchronized1

between LDAP directory and Unified CM.

MRA

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.


Messaging: Transitioning to Jabber Team Messaging ModeCisco Jabber On-Premises Messaging Flow0

1 Expressway MRA flow is optional.

Call Control – SIP (registration, call routing)

Messaging – XMPP (messaging, presence)

Directory – LDAP (contact search)

Directory Sync – LDAP

13

Expressway-C/E

Jabber Clients

MRA1

Direct

Unified CM IM&P

Unified CM

Directory


Messaging: Transitioning to Jabber Team Messaging ModeMapping the Transition: Step 1 – Jabber Team Messaging



ExpresswayMRA

On-Premises

Unified CMIM&P

WebexCiscoWebex

Teams

ExpresswayMRA1

On-Premises

Note: This map is a visual representation of the workload transition(s), highlighting the primary architectural changes during the deployment.1 Expressway MRA is an optional feature. 14


• Licensing: Move to Flex Licensing.

• User Accounts: Users must be synchronized with organization’s Webex identity store/added in Webex Control Hub.

• Messaging Resources: Remove on-premises Unified CM IM&P messaging / presence service nodes.1 These are no longer needed with cloud messaging.

» Interoperability (optional): Hybrid Messaging interop can be deployed for Unified CM IM&P to Webex Teams. These capabilities are optional for organizations who will do a phased migration.

• Migration Process: Administrator can enable the migration from Webex Control Hub. Jabber 12.5 or later deployments automatically discover that a migration is required.

• Contact List Migration: User Contact Lists can be migrated on a per user basis.

• Presence: Presence model is based on user activity.

Messaging: Transitioning to Jabber Team Messaging ModeWhat Changes with Jabber Team Messaging Mode?

15

WebexCisco

1 Maintain Unified CM IM&P for phased migration or if co-existence (dual messaging services) is required. Consider hybrid messaging interop to address co-existence scenarios.

1


Messaging: Transitioning to Jabber Team Messaging ModeBefore – Cisco Jabber On-Premises Messaging0

16

Expressway-C/E

Jabber Clients

Direct

Unified CM IM&P

Unified CM

Directory

MRA1


LDAP


Expressway-C/E

Jabber Clients

Direct

Unified CM IM&P3

Unified CM MRA

Active Directory

Messaging: Transitioning to Jabber Team Messaging ModeAfter – Cisco Jabber Team Messaging Deployment

WebexCisco

Webex Teams

1

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 connections3 In case of phased migration, Unified CM IM&P service nodes removed after all Jabber users have been transitioned to Team Messaging.

17

Call Control: Unified CM continues to provide client registration and call routing

Firewall Traversal: Expressway-E/Cprovides Mobile and Remote Access (MRA) firewall traversal2 for external Jabber client calling

Cloud Messaging & Presence: Webex Teams service provides HTTPS/REST-based messaging, presence and contact list services for Jabber

Directory: Corporate users synchronized1

between Active Directory and Unified CM.

LDAP


Messaging: Transitioning to Jabber Team Messaging ModeAfter – Cisco Jabber Team Messaging Flow1


Call Control – SIP (registration, call routing)

Messaging – HTTPS (messaging, presence)

Directory – LDAP (contact search)

Directory Sync – LDAP

18

Expressway-C/E

Jabber Clients

MRA1

Direct

Unified CM

Active Directory

WebexCisco

Webex Teams

Direct

Unified CM IM&P


• 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).

Messaging: Transitioning to Jabber Team Messaging ModeJabber Team Messaging is Flexible & Delivered Seamlessly

19


There are many other compelling reasons for transitioning from on-premises to Cisco Webex cloud messaging:

• 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.

• Webex Teams messaging APIs for highly accessible integrations

• Instant global federation with other Webex Teams organizations

Messaging: Transitioning to Jabber Team Messaging ModeWhy Move to Cisco Jabber Team Messaging Mode?

20


The following tables highlight key technical considerations to be aware of when transitioning from the on-premises messaging deployment toa cloud-based messaging deployment.The considerations have been divided into the following categories:

» Compliance» B2B Federation» Presence Model» Desktop Share» Contact List

Messaging: Transitioning to Jabber Team Messaging ModeWhat is Different When Moving to Jabber Team Messaging?

21


Category Considerations

Compliance

• The Webex Teams platform does support integration with third-party compliance engines.• Message blocking is implemented after message delivery.• Ethical firewalls are not currently supported in Jabber team messaging mode.• FIPS mode is not currently supported in Jabber team messaging mode.

Considerations for compliance

Messaging: Transitioning to Jabber Team Messaging ModeCompliance Considerations

22



B2B Federation

• The Webex Teams platform supports messaging federation with other Webex Teams orgs (this can be disabled).

• Webex Teams does not support native B2B federation with other vendors (XMPP or SIP). NOTE: services such as m.io can provide interop to Microsoft Teams or Slack.

• Intra domain federation to Microsoft Lync is not supported.

Presence Model

• Webex Teams implements an activity-based presence model: Active, Active 10 mins ago, On a Call, Inactive, and so on. Activity status is based on using the application.

• Unified CM IM&P implements an Availability based presence model: Available, Away, On a Call, and so on. Availability status is based on user setting/being logged into your device.

• Unified CM IM&P also supports custom presence statuses, including user set location information.

Considerations for B2B federation and presence model

Messaging: Transitioning to Jabber Team Messaging ModeFederation and Presence Model Considerations

23


Considerations for desktop sharing and contact lists

Messaging: Transitioning to Jabber Team Messaging ModeDesktop Sharing and Contact Lists Considerations

24


Desktop Sharing

• Jabber with Unified CM IM&P and Jabber team messaging mode, both support desktop sharing when on a call.

• Jabber for Windows with Unified CM IM&P supports desktop sharing from a messaging only session. This desktop sharing also supports remote control. This functionality is not supported in Jabber team messaging mode.

Contact Lists

• Jabber team messaging mode supports contact lists. Contact lists can be maintained when migrating from Unified CM IM&P to team messaging mode.

• Contact lists cannot be managed via Enterprise Groups.• Contact lists cannot be managed in bulk (administratively).




References

25


Jabber Deployment Guides• 12.x Deployment Guides:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_0/cjab_b_documentation-guide-for-cisco-jabber-12.html

Help Center• Reference: Jabber team messaging mode

https://help.webex.com/en-us/na06sg/Jabber-Team-Messaging-Mode

Adoption Toolkit• https://community.cisco.com/t5/collaboration-

applications/jabber-team-messaging-mode-adoption-toolkit/td-p/3791351

Unified CM IM&P Deployment Guides• https://www.cisco.com/c/en/us/support/unified-

communications/unified-presence/products-installation-guides-list.html

Messaging: Transitioning to Jabber Team Messaging ModeReferences

26

Messaging Transition Deployment Guide• Messaging: Transitioning from Unified CM

IM&P to Cisco Jabber Team Messaging Mode Deployment Guide:https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_MESSAGING-IMP_to_Jabber_Team_Messaging.pdf

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_0/cjab_b_documentation-guide-for-cisco-jabber-12.html

https://help.webex.com/en-us/na06sg/Jabber-Team-Messaging-Mode

https://community.cisco.com/t5/collaboration-applications/jabber-team-messaging-mode-adoption-toolkit/td-p/3791351

https://www.cisco.com/c/en/us/support/unified-communications/unified-presence/products-installation-guides-list.html

https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_MESSAGING-IMP_to_Jabber_Team_Messaging.pdf




Alternate Transition: Webex Messenger to Team Messaging

27


Messaging: Transitioning to Jabber Team Messaging ModeAlternate Transition: Webex Messenger to Team Messaging

28

Cisco Jabber w/ Webex Messenger0


WebexCiscoWebex

Teams

ExpresswayMRA1

On-Premises

WebexCisco

WebexMessenger

ExpresswayMRA1

On-Premises

Note: This map is a visual representation of the workload transition(s), highlighting the primary architectural changes during the deployment.1 Expressway MRA is an optional feature.


Messaging: Transitioning to Jabber Team Messaging ModeBefore - Cisco Jabber Webex Messenger Deployment

29

0

Expressway-C/E

Jabber Clients

Direct

Unified CM MRA

DirectoryWebexCisco

Webex Messenger

LDAP


Cloud Messaging & Presence: Webex Messenger service provides XMPP-based messaging, presence and contact list services for Jabber

Firewall Traversal: Expressway-E/Cprovides Mobile and Remote Access (MRA) firewall traversal2 for remote Jabber clients

Directory: Corporate users synchronized1 between LDAP directory and Unified CM.



Active Directory

Messaging: Transitioning to Jabber Team Messaging ModeAfter – Cisco Jabber Team Messaging Deployment1


30

Expressway-C/E

Jabber Clients

Direct

Unified CM MRA

WebexCisco

Webex Teams

LDAP


Firewall Traversal: Expressway-E/Cprovides Mobile and Remote Access (MRA) firewall traversal2 for remote Jabber client calling.

Directory: Corporate users synchronized1 between Active directory and Unified CM.

Cloud Messaging & Presence: Webex Teams service provides HTTPS/REST-based messaging, presence and contact list services for Jabber


Messaging Transitioning to Jabber Team Messaging ModeReferences: Webex Messenger to Jabber Team Messaging

31

Webex Messenger Admin Guide

• https://www.cisco.com/c/en/us/td/docs/collaboration/webex-connect/Messenger_Administration_Guide/WebEx_BK_C9864D4C_00_cisco-webex-messenger-administration-guide_chapter_00.html

Messaging Transition Deployment Guide• Messaging: Transitioning from Webex

Messenger to Cisco Jabber Team Messaging Mode Deployment Guide:https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_MESSAGING-Messenger_to_Jabber_Team_Messaging.pdf

https://www.cisco.com/c/en/us/td/docs/collaboration/webex-connect/Messenger_Administration_Guide/WebEx_BK_C9864D4C_00_cisco-webex-messenger-administration-guide_chapter_00.html

https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_MESSAGING-Messenger_to_Jabber_Team_Messaging.pdf


[END]

© 2020 Cisco and/or its affiliates. All rights reserved. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 32

Documents

Messaging: Transitioning from Unified CM IM&P / Webex ... · CTG Technical Marketing Engineering Team. Messaging: Transitioning from Unified CM IM&P / Webex Messenger to Jabber Team