PDF(580.8 KB) View with Adobe Reader on a variety of devices
ePub(539.5 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(648.4 KB) View on Kindle device or Kindle app on multiple devices
Updated:November 1, 2018
Document ID:213865
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the configuration steps for Extensible Messaging and Presence Protocol (XMPP) federation on Expressway.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
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.
Background Information
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
Configure
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.
Expressway C logs will show: "Module="network.axl" Level="INFO" Action="Send" URL="https://cups.ciscotac.net:8443/axl/" Function="executeSQLQuery"
3. Ensure that the Public DNS is updated with the XMPP server SRV records for all domains with which federation is needed.
_xmpp-server._tcp.domain.com on port 5269
Verify the XMPP Configuration on Expressway
Step 1. Verify if the database changes were succesfully accepted by the IM&P server by running this query from CUP Command Line Interface (CLI) :
Solution 1 : Update password, refresh CUP server discovery
Symptom 2: Federation fails, XCP router on CUP is bouncing packets
Cause 2 : XCP Router on CUP has not been restarted
This can be verified on CUP Administration under the Notifications page.
Solution 2 : Restart XCP router on CUP
Sometimes there will be no notification, but the XCP Router log on CUP is still bouncing packets. If restarting the XCP Router service does not resolve this, rebooting the IM&P Cluster does.
Verify
There is currently no verification procedure available for this configuration.
Troubleshoot
There is currently no specific troubleshooting information available for this configuration.