External XMPP Federation through Cisco Expressway
The preferred method for deploying external XMPP federation is through Cisco Expressway. Cisco Expressway enables users registered to IM and Presence Service to communicate via the Expressway-E with users from a different XMPP deployment. The following diagram shows how XMPP messages are routed from an on-premises IM and Presence Service server via the Expressway-C and Expressway-E Collaboration Edge solution to the federated XMPP server. It also shows the ports and connections that are used as the messages traverse DMZ firewalls.
Note |
The Expressway-C and Expressway-E combination is shown here, however the same external XMPP federation functionality is also available when using a VCS Control and VCS Expressway combination. Refer to Cisco Expressway Administrator Guide (X8.2) for more information about the Expressway series option or Cisco TelePresence Video Communication Server Administrator Guide (X8.2) for more information about the VCS option. |
Note |
SIP and XMPP federations are separate and do not impact each other. For example, it is possible to deploy SIP federation on IM and Presence Service and external XMPP federation on Cisco Expressway. |
Supported Federations
Expressway-E supports XMPP federation with the following enterprises:
-
Cisco Unified Communications Manager IM and Presence Service Release 9.1 or later
-
Cisco WebEx Connect Release 6.x
-
XMPP standards-compliant servers
Supported Deployment Configurations
The following XMPP federation deployment options are available:
-
external XMPP federation only (terminated on Cisco Expressway)
-
internal XMPP federation only (terminated on IM and Presence Service)
-
internal and external XMPP federation (terminated on IM and Presence Service) but requires you to configure your firewall to allow inbound connections.
For more information about external XMPP federation through Cisco Expressway, see Cisco Expressway Administrator Guide (X8.2)
Restrictions
-
Simultaneous internal XMPP federation terminated on IM and Presence Service and external XMPP federation terminated on Cisco Expressway is not supported.
Important
If you deploy external XMPP federation through Cisco Expressway, do not activate the Cisco XCP XMPP Federation Connection Manager feature service on IM and Presence Service.
-
Expressway-E does not support XMPP address translation (of email addresses, for example). If you are using Expressway-E for XMPP federation, you must use native presence Jabber IDs from IM and Presence Service.