This document describes the configuration steps for Extensible Messaging and Presence Protocol (XMPP) federation on Expressway.
There are no specific requirements for this document.
The information in this document is based on these software and hardware versions:
Cisco Expressway X8.2 or later
Unified Call Manager(CM) Instant Messanger (IM) and Presence Service 9.1.1 or later
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
This diagram illustrates the high level communication:
If you enable XMPP Federation on Expressway, the active Server to Server(S2S) moves from Cisco Unified Presence (CUP) to Expressway Edge (Expressway E). This component is manages all XMPP communications between the federated domains.
S2S uses port 5269 to communicate with the federated domains
Internal XMPP traffic between XCP routers on ExpresswayE, C and CUP runs on port 7400
XMPP Provisioning information from Expressway E is send to Expressway C through the SSH tunnel on port 2222
Expressway C updates CUP with the necessary routing information via AXL port 8443
Step 1. Enable XMPP Federation on Expressway E
Configuration > Unified Communication > > On
After you enable XMPP federation this will be observed:
1. Expressway-E updates it's local configuration and replicates this setting with Expressway Core (Expressway C).
Expressway E logs will show: "Detail="xconfiguration xcpConfiguration is_federation_enabled - changed from: 0 to: 1"
2. Expressway-C updates the "xmpps2snodes" table on the CUP database with the realms of the Expressway E S2S component.