Cisco Cisco Expressway
Prerequisites
Before configuring your Cisco Expressway system for external XMPP federation:
n
Ensure that you are running the following software versions:
l
Cisco Expressway X8.2 or later.
l
Unified CM IM and Presence Service 9.1.1 or later.
Note XMPP federation can only be supported on a single Cisco Expressway cluster.
n
Ensure that Interdomain XMPP federation has been disabled on Unified CM IM and Presence Service:
Go to
Go to
Cisco Unified CM IM and Presence Service Administration > Presence > Inter Domain
Federation > XMPP Federation > Settings
and ensure that XMPP Federation Node Status is set to
Off.
n
Cisco Expressway-E does not support XMPP address translation (of email addresses, for example).
External systems must federate with the Jabber IDs that are native to Unified CM IM and Presence
Service. You can make the user's Unified CM IM and Presence Service Jabber ID resemble the user's
email address, so that the federated partner can approximate email addresses for federation, by:
External systems must federate with the Jabber IDs that are native to Unified CM IM and Presence
Service. You can make the user's Unified CM IM and Presence Service Jabber ID resemble the user's
email address, so that the federated partner can approximate email addresses for federation, by:
a. Setting the Unified CM Lightweight Directory Access Protocol (LDAP) attribute for User ID to be the
user's sAMAccountName.
b. Setting the Unified CM IM and Presence Service presence domain to be the same as the email domain.
c. Setting your email address so that it is the same as samaccountname@presencedomain.
c. Setting your email address so that it is the same as samaccountname@presencedomain.
n
Simultaneous internal federation managed by Unified CM IM and Presence Service and external federation
managed by Cisco Expressway is not supported. If only internal federation is required then you must use
interdomain federation on Unified CM IM and Presence Service. The available federation deployment
configuration options are:
managed by Cisco Expressway is not supported. If only internal federation is required then you must use
interdomain federation on Unified CM IM and Presence Service. The available federation deployment
configuration options are:
l
External federation only (managed by Cisco Expressway).
l
Internal federation only (managed by Cisco Unified CM IM and Presence Service).
l
Internal and external federation managed by Cisco Unified CM IM and Presence Service, but requires
configuring your firewall to allow inbound connections.
configuring your firewall to allow inbound connections.
For more information, see
n
If you intend to use both Transport Layer Security (TLS) and group chat, the Cisco Expressway-C and
Cisco Expressway-E server certificates must include in their list of subject alternate names the Chat
Node Aliases that are configured on the IM and Presence Service servers. Use either the XMPPAddress
or DNS formats. Note that the Cisco Expressway-C automatically includes the chat node aliases in its
certificate signing requests (CSRs), providing it has discovered a set of IM and Presence Service servers.
When generating CSRs for the Cisco Expressway we recommend that you copy-paste the chat node
aliases from the equivalent
Cisco Expressway-E server certificates must include in their list of subject alternate names the Chat
Node Aliases that are configured on the IM and Presence Service servers. Use either the XMPPAddress
or DNS formats. Note that the Cisco Expressway-C automatically includes the chat node aliases in its
certificate signing requests (CSRs), providing it has discovered a set of IM and Presence Service servers.
When generating CSRs for the Cisco Expressway we recommend that you copy-paste the chat node
aliases from the equivalent
Generate CSR
page on the Cisco Expressway-C. See
for more information.
Cisco Unified Communications XMPP Federation Deployment Guide (1.4)
Page 5 of 59
External XMPP Federation through Cisco Expressway