Webex Teams Jabber

Posted on by admin




This article provides interoperability between your cloud-based Jabber deployment and Webex. This is different to the interoperability between on-premises Jabber deployments and Webex users (see https://www.cisco.com/go/hybrid-services-message for more on that deployment).

With the Cisco Webex / Jabber Interop setting enabled:

Webex Teams Jabber

  • People can send or receive messages between Webex and Jabber apps.

  • Jabber users see a status of On Cisco Webex, when their contact is using Webex.

Deployment Requirements

We've got all the tools and information you need to move from Jabber with Webex Messenger or Jabber Team Messaging Mode to the Webex app. Meet your team on video, schedule meetings, and more. With pre- and post-meeting collaboration and the ability to see files and conversations across all devices, teamwork has never been easier. Cisco Jabber upgrade to Webex Teams will be pushed to all machines via SCCM in batches and will take 2-3 weeks to be installed on every machine. New accounts will be requested through the service desk and approved by managers. A new process may be required. Cisco Jabber upgrade to Webex Teams will be pushed to all machines via SCCM in batches and will take 2-3 weeks to be installed on every machine. New accounts will be requested through the service desk and approved by managers. A new process may be required. More recently, we have developed Webex Teams to take team collaboration to the next level. Webex Teams offers persistent messaging, calling, meetings, content sharing, whiteboarding. And new cognitive collaboration experiences! In November we announced Jabber /w Teams Messaging Mode. Jabber is generally an on-premise UC solution (chat, presence, calling) Webex Teams is the same, but is primarily a cloud based UC solution for these features and more.

Supported for Cisco Jabber cloud deployments only.

Teams

Before you enable this setting, check the following:

  • Your organization must be added to the Cisco Platform identity service. You can check in Cisco Webex Control Hub to see if your organization has been added. If your organization hasn't been added, you can contact the Cisco Customer Support team or your Cisco Customer Success Manager to request that your organization is added to the Cisco Platform identity service. This process to add users to the identity service takes some time to complete.

    For more information on the request process for Cisco Customer Support or Cisco Customer Success Manager, see this support article.

    Cisco Jabber (Webex Messenger) and Webex domains must be identical for the Webex Messenger Org to be synched into the Cisco Platform identity service.

    Cisco Directory Connector must be disabled in Control Hub, as this method of managing users is not compatible with how users are managed in a Jabber cloud deployment.

Webex Teams Jabber-config.xml

  • If you use Single Sign On (SSO) for Webex Messenger then you must set up SSO for Cisco Platform identity service. For more information about configuring SSO, see the Cisco Webex Messenger Install and Upgrade documentation.

Known Limitations

  • Users can only send text between Jabber and Webex, sending any other content is not supported.

  • You can only send messages in a space with one person, you can't send messages in group spaces.

  • End-to-end AES encryption is not supported.

  • All users must have the Cisco Webex / Jabber Interop setting enabled.

    When a Jabber user without interop enabled attempts to send a message to an interop enabled user who isn't signed in to Jabber, they receive this message This user is currently offline in Jabber and the message cannot be delivered.

Jabber Requirements

Jabber

Cisco Jabber clients 11.9 or later.

Ensure the following parameter is set to False in the jabber-config.xml file:<Persistent_Chat_Enabled>False</Persistent_Chat_Enabled>

AES encryption must be disabled in Cisco Webex Messenger Administration Tool (Org Admin). In the Policy Editor tab, disable the Support End-To-End Encryption for IM setting.

Cisco Webex Control Hub Settings

You can enable the Cisco Webex / Jabber Interop setting in Control Hub for your entire organization and then for specific people. The setting is also available as one of the services to choose in the CSV file user setup.

Set Up Messaging Between Cisco Webex and Jabber for Your Organization

When your users are in Webex and also in Cisco Jabber, you can use this setting to allow everyone in both apps to communicate with each other.

Cisco Jabber Webex Teams

1

From the customer view in https://admin.webex.com, go to Services, and then click Message > Webex Messenger.

If you don't see this option, contact the Cisco Customer Support team or your Cisco Customer Success Manager to request that your organization is added to the Cisco Platform identity service. This process to add users to the identity service takes some time to complete.

2

Scroll to Options, click Cisco Webex / Jabber Interop, and then click Save.

Strategic Alliances and Integrations Enable Comprehensive Calling, Meetings, and Messaging Capabilities

In my role as a product manager here at Cisco, I regularly talk to customers about their collaboration environments. One question I get asked is what they can do to bring together collaboration tools from different vendors…

The Webex unified app is providing our customers with comprehensive calling, meetings, and messaging capabilities that integrate with our award-winning video devices and IP phones. The result is seamless and consistent workflows.

Cisco Webex Teams Vs Jabber

But we are also aware that many customers have existing investments in place with collaboration tools from other vendors, and we are committed to making sure that Webex is an open platform, that integrates with 3rd party applications to ensure our mutual customers have a solution that delivers the best possible outcomes.

Earlier this year one of my colleagues talked about how we are enabling organizations with Microsoft Teams and Slack messaging users to start Webex Meetings from these applications.

Webex Teams Jabber

Now, new Cisco calling integrations allow you to use all your enterprise-grade voice and video calling features in combination with these messaging platforms.

Cisco Calling Integrations

Calling integrations allow you to expose Cisco calling buttons directly in other vendors messaging apps. We’ve built the Cisco calling integrations to provide you with flexible solutions plus we’ve made them very easy to deploy. We started with Microsoft Teams and Slack messaging apps. To deploy a Cisco calling integration you simply select the Cisco client you are using for calling and the calling platform you want to use.

When you have added the Cisco calling integration, you can launch a Webex Teams or Cisco Jabber call directly from your messaging app. When you click the call button, the integrations identify who you’re chatting with, resolves their calling address, and passes this information to your installed Cisco client which starts a Cisco voice or video call. The integrations support all Cisco calling platforms including Cisco Unified Communication Manager (UCM) based on-premises and hosted deployments, and Webex Calling for cloud.

There are no complex back end changes to make as these are client integrations. There are no call routing policies or dial plan changes to make, no additional licenses required, and no new hardware to manage. You can even use the calling integrations with desk phone control, which means your users don’t have to replace their handsets.

Cisco Calling from Slack

Slack has made its messaging platform very open to integrating calling providers like Cisco. Adding the Cisco calling integration to Slack means you use the native Slack call button to start a Cisco call directly from Slack.

This could be using Webex Teams or Cisco Jabber as your softphone or controlling your desk phone. If your Cisco client is controlling your Cisco desk phone clicking the call button in Slack causes your Cisco desk phone to go off-hook and call your colleague.

Slack is popular with developers where users tend to like keyboard commands to take actions like making calls. Talking to Slack users it becomes clear this is a requirement for Slack users so we implement “/jabber” and “/webexteams” slash command allowing you to make calls at the command line.

We are continuing to work in partnership with Slack and plan to implement Slack’s new shortcut controls shortly. This will give you more calling destination selectable directly in Slack.

Cisco Calling from Microsoft Teams

The Cisco calling integration for Microsoft Teams has been available from the Microsoft Teams app store for just over a month now. This month we have extended it with new features and functionality. In addition to supporting Microsoft Teams desktop and web users, this month we added support for mobile and tablet devices. We also added new contact search capabilities, you can now search your Microsoft 365 Outlook contacts and call them using your Cisco calling platform via the integration.

Webex

Building Bridges with Webex

Will Webex Teams Replace Jabber

These two new calling integrations are just examples of the many integrations that the Webex platform supports, enabling people to enhance their communication and collaboration within their everyday workflows. For example, we’ve also worked with Microsoft to integrate Microsoft SharePoint and OneDrive Enterprise Content Management (ECM) solutions into Webex team messaging services to streamline collaboration on documents.

What Next…

If you’re interested in learning more about Cisco calling integration contact your Cisco account team to discuss how to build on your current Cisco UC investments with Webex to enhance the collaboration experience for your users and/or integrate with 3rd party collaboration tools.

Jabber

Read More