Cisco Cisco TelePresence Video Communication Server Expressway
DNS SRV Records for XMPP Federation
If federating parties are not using static routes to access federated XMPP services, suitable DNS SRV
records must be published.
records must be published.
_xmpp-server records
You must publish an _xmpp-server DNS SRV record in DNS for your local domain so that remote
enterprises can access your federated XMPP services. For example:
enterprises can access your federated XMPP services. For example:
Domain
Service
Protocol
Priority
Weight
Port
Target host
example.com
xmpp-server
tcp
0
0
5269
vcse.example.com
Similarly, to allow federating parties to discover a particular XMPP federated domain (if they are not using
static routes), the federated enterprise must publish an _xmpp-server DNS SRV record in its public DNS
server. For example:
static routes), the federated enterprise must publish an _xmpp-server DNS SRV record in its public DNS
server. For example:
Domain
Service
Protocol
Priority
Weight
Port
Target host
federated.com
xmpp-server
tcp
0
0
5269
xmppserver.federated.com
All enterprises must publish the service on port 5269. The published FQDNs must also be resolvable in DNS
to an IP address.
to an IP address.
Group Chat
If you configure the Group Chat feature on a Unified CM IM and Presence Service server in an XMPP
federation deployment, you must publish DNS SRV records for the federated chat node aliases.
federation deployment, you must publish DNS SRV records for the federated chat node aliases.
To allow IM and Presence Service to discover a particular XMPP federated chat node alias, the federated
enterprise must publish an _xmpp-server DNS SRV record in its public DNS server. Similarly, IM and
Presence Service must publish the same DNS SRV record in DNS for its domain. For example:
enterprise must publish an _xmpp-server DNS SRV record in its public DNS server. Similarly, IM and
Presence Service must publish the same DNS SRV record in DNS for its domain. For example:
Domain
Service
Protocol
Priority
Weight
Port
Target host
chatroom1.example.com
xmpp-server
tcp
0
0
5269
vcse.example.com
Both enterprises must publish the service on port 5269. The published FQDN must also be resolvable to an
IP address in DNS.
IP address in DNS.
Alternatively, to use group chat aliases on federated servers, you can configure static routes on the Cisco
VCS Expressway (
VCS Expressway (
Configuration > Unified Communications > Federated static routes
) for each chat
node alias.
Note that:
n
The chat node aliases are configured on
Cisco Unified CM IM and Presence Service Administration
(
Messaging > Group Chat Server Alias Mapping
).
n
Internal users do not need to use DNS to discover chat nodes; they get the chat room details from their
local IM and Presence Service servers.
local IM and Presence Service servers.
Cisco Unified Communications XMPP Federation Deployment Guide (1.4)
Page 15 of 59