Cisco Cisco TelePresence Video Communication Server Expressway
Troubleshooting External XMPP Federation
This section describes how to troubleshoot your external XMPP federation deployment and describes the
impact of making configuration changes on a live system.
impact of making configuration changes on a live system.
n
n
n
n
n
n
n
n
Checking the Basic Status of your System
If you encounter issues with the XMPP federation status service, you should first check the
Status
> Unified Communications
page on both the Cisco VCS Control and the Cisco VCS Expressway.
This will highlight any basic connection or configuration problems and provide information and links to help
correct the problem.
correct the problem.
General Configuration Checklist
Ensure that the following Cisco VCS configuration items have been specified correctly:
n
Port 5269 is open in both directions between the internet and Cisco VCS Expressway in the DMZ.
n
DNS settings: host name, domain name, and default DNS server (
System > DNS
).
n
An accessible NTP server (
System > Time
).
n
An active Unified Communications traversal zone on the Cisco VCS Control and its associated Cisco
VCS Expressway (
VCS Expressway (
Status > Zones
).
n
Unified Communications mode is set to Mobile and remote access on both the Cisco VCS Control and
Cisco VCS Expressway (
Cisco VCS Expressway (
Configuration > Unified Communications > Configuration
).
n
XMPP federation support is On on the Cisco VCS Expressway (
Configuration > Unified
Communications > Configuration
).
n
If static routes are enabled, ensure that the appropriate routes for the federated XMPP domains have been
added to the Cisco VCS Expressway (
added to the Cisco VCS Expressway (
Configuration > Unified Communications > Federated static
routes
).
n
At least one domain is configured on the Cisco VCS Control with XMPP federation set to On
(
(
Configuration > Domains
).
n
IM and Presence Service servers have been discovered on the Cisco VCS Control and have an active
status (
status (
Configuration > Unified Communications > IM and Presence Service servers
).
Discovery, Connectivity, and Firewall Issues
n
If using DNS lookup, check that _xmpp-server public DNS records exist for the domains and chat node
aliases of all federated parties, and that they use port 5269.
aliases of all federated parties, and that they use port 5269.
Cisco Unified Communications XMPP Federation Deployment Guide (1.4)
Page 19 of 59