Transition between messaging platforms can be difficult. In an effort to ease the transition, Cisco has released the ability to allow users to communicate between Jabber and Spark. Interoperability between Cisco Spark and Cisco Jabber enables users to receive both Cisco Spark and Cisco Jabber message in either application. At this time, only 1-to-1 messages are viewable from either application. Interop is not available for Jabber on premise but will be available in Jabber Release 12 in 2018. Cisco Jabber customers are encouraged to run the latest version of Cisco Jabber (11.9+) for the best user experience.
1-to-1 messages are viewable from either application. Note: Users encouraged to use only one application to avoid duplicate notifications.
Presence, in limited form, is shared between applications
Content sharing allows files posted to a Cisco Spark Space to be accessible as a web link in Jabber. Limitations include:
Content posted from Jabber is not viewable in Cisco Spark.
Jabber links for "Share My Desktop" and "Meet Now" will not load in Cisco Spark.
Organization must have and existing WebEx Messenger license.
Cisco Spark License:
Existing Cisco Spark Customer - Any type of Cisco Spark License will work
Not an existing Cisco Spark Customer? Not a problem, Cisco will create the new Org in CI and give the customer Free Cisco Spark license.
We recommend you enable DOMAIN CLAIM within Control Hub on the Spark Org
Messenger Domain must be Synchronized to Common Identity - account team submits a SalesForce Provisioning Ticket to Sync the domain to CI - (KB article: WBX000026976)
The organization can’t have Directory Sync (DirSync) enabled in Spark. If the organization does have DirSync enabled, they must disable it before proceeding. Messenger/Org Admin must be the source of truth for user management (not DirSync).
Cisco Jabber Users login will be redirected to CI; Jabber login background screen will change but that is the only noticeable difference for end users.
SSO (Single Sign On) Setup - SSO must be setup the same on both the Messenger side AND the Spark side. We can't have a mis-match of SSO settings - meaning SSO can't be setup on the Spark side and not the Messenger/Jabber side.
Once the Synchronization is completed, the admin will see the Interop option in the Cisco Spark Control Hub (formally known as Cloud Collaboration Management) - can take 24 hours to take affect.
The organization must use Jabber 11.9 or higher.
A Customer Success Manager or Partner Success Manager can submit a ticket on the customer’s behalf to have Messenger domain synchronized - see KB article: WBX000026976
Cisco Spark Admin logs into Cisco Spark Control Hub Portal (Services>Messenger link) and enables Interop on the domain – enablement is 1 hr
Cisco Spark Admin enables users to have interop either manual or CSV import – can take up to 24 hours for users to begin using interop
Within the 24 hour period, Cisco Jabber users will start to receive 1 to 1 Interop Messages. For Spaces (Beta Feature), the user will have to restart the Cisco Jabber client to see the Spaces tab); Cisco Spark users do not need to restart the client.
NOTE: Customers are encouraged to run just one application on their device otherwise they will receive the same message multiple times. For example, if the user has both Cisco Spark and Cisco Jabber running on their phone, a single message to them will trigger the message notification twice. The same is true for the desktop experience.
More information is available on the Collaboration Help Site: https://help.webex.com/docs/DOC-21634