Coming Soon! We're giving you a sneak peek of the new designs and features in Cisco Webex Control Hub.

Webex Teams supports Extensible Messaging and Presence Protocol (XMPP) with third party apps that recognize XMPP. For example, Jabber and Pidgin. Your users can communicate with people who are using XMPP apps.

Configuring XMPP

  • DNS service with associated XMPP SRV record

  • Enable settings in Cisco Webex Control Hub

Things to Keep in Mind

  • Your users can only create a space with one person using XMPP, creating group spaces is not supported.

  • When your users add people using XMPP, there is no status displayed in Webex Teams for these people.

  • End-to-end encryption is not available for third party federated users.

  • TLS encrypted connections between Webex Teams and external XMPP services is only available when the external service allows unauthenticated TLS.

  • Any configuration you applied to block external communication for your organization also applies for XMPP federation.


From the customer view in, go to Services and on the Message card click Settings.


Scroll to XMPP Federation and select the following:

  • Select your XMPP domain from your verified domains.
  • Create an _xmpp-server._tcp XMPP SRV record that points to your cluster on port 5269 on your DNS server.

    The following are the clusters:

    • US cluster—

    • EU cluster—

    For example, for a customer with an XMPP domain of on a US cluster, the SRV record is as follows:

    1 | dig +short SRV

    2 | 5 0 5269

  • Click Verify.

Enable XMPP Federation.

A Jabber ID is created for each user in your organization using information from the user's email address and your XMPP domain in the format Username@XMPP_Domain.

For example: a user with an email address and an XMPP domain example, the Jabber ID is

You can change this for individual users. Go to Users, choose a user, and under Hybrid Services choose Jabber Service. Update the username in the Jabber ID.