Messaging transitions

4.IM&P/Webex Messenger to Jabber Team Messaging Mode

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 (Cisco Webex Meetings).
Persistent messaging with file sharing, 1-on-1 messaging and multi-person Spaces.
Reduced total cost of ownership as no requirement for on-premises Unified CM IM&P services nodes, and no need for external database and file servers for persistent chat.
Instant global federation with other Webex Teams organizations.

We do not have very strict compliance requirements like pre-delivery message blocking, ethical firewalls, or FIPS mode.
We do not have B2B federation with third-party messaging services.
We do not have Intradomain federation with Microsoft.
We do not have heavy use of Jabber IM only mode desktop share.

Acquire Flex licensing required for Jabber team messaging mode.
Acquire a Cisco Webex Teams organization in order to access Webex Control Hub for Jabber team messaging configuration.
Link Webex Messenger and Webex Teams if transitioning from Webex Messenger.
Ensure you understand Jabber team messaging authentication (SSO recommended), service discovery, directory integration and contact lists.

Enable Jabber team messaging mode for Webex Teams organization.
Enable Jabber team messaging mode for users.
Initial service discovery and first-time connection to Webex Teams messaging service.
Contact migration, if required by administrator configuration.
Jabber calling with Unified CM discovery, if enabled by administrator.

Remove TS/Conductor from production (if desired)
Disable CMR-H session type in Webex Site Admin at site and user-level (if transitioning from CMR-H)
Monitor Webex Control Hub reports for analytics and troubleshooting of meetings.

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

Our deployment does not include persistent chat.
Our deployment does not require compliance with a third-party compliance solution.
Our deployment does not require federation.
Our deployment does not have a requirement to remain on a version earlier than 11.5(1)U5
Our deployment does not have a requirement for phone line status without relying on Jabber clients.

Verify that all Jabber clients can log in and control both soft and physical phones and access voicemail.
Determine centralized Unified CM IM&P equipment location
Decide whether you intend to deploy new hardware OR promote existing hardware as the centralized Unified CM IM&P cluster.
Use the Unified CM IM&P BAT to export users’ contact lists so that you can restore their lists to the centralized Unified CM IM&P cluster.
Perform DRS backup plan for disaster recovery in case something goes wrong during the transition.

Upgrade all existing Unified CM and IM&P clusters to release 11.5(1)SU5 or later at all locations.
Upgrade Jabber clients to version 12.0 or later.
Deploy new hardware for the centralized Unified CM IM&P cluster OR promote existing cluster for the role of centralized Unified CM IM&P cluster.
Enable and start required services on the centralized Unified CM Publisher and Unified CM IM&P nodes.
Configure SSO and OAuth with Refresh Token as appropriate for your environment (optional).
Configure an AXL connection between the centralized IM&P and all remote leaf voice clusters (synchronizes private encryption keys)
Define appropriate service profiles, feature group templates, and UC services on all publishers.
Deactivate IM&P feature services and stop XCP router on all Unified CM IM&P nodes except for the centralized cluster.
Perform a full LDAP sync and then use BAT to update user' Service Profile and users' contact lists to centralized Unified CM IM&P (via BAT).
For Expressway MRA deployments, update Unified CM and Unified CM IM&P server nodes on Expressway-C to account for cluster changes.

Remove unused Unified CM IM&P clusters.
Configure inter clustering with other Unified CM IM&P clusters from sites that will not leverage centralized Unified CM IM&P (if required).