Cisco Cisco Expressway Maintenance Manual
4.
To manage the domains and chat node aliases in the allow or deny lists, click either Federation allow list or
Federation deny list as appropriate.
Federation deny list as appropriate.
In the resulting page you can add, modify or delete the items in the allow/deny list. Wildcards or regexes are
not allowed in the names; it must be an exact match.
not allowed in the names; it must be an exact match.
All domains and chat node aliases that are configured as static routes are included automatically in the allow list.
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.
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:
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
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.
address.
Group Chat
If you configure the Group Chat feature on a Unified CM IM&P server in an XMPP federation deployment, you must
publish DNS SRV records for the federated chat node aliases.
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
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.
in DNS.
Alternatively, to use group chat aliases on federated servers, you can configure static routes on the Expressway-E
(Configuration > Unified Communications > Federated static routes) for each chat node alias.
(Configuration > Unified Communications > Federated static routes) for each chat node alias.
Note that:
■
The chat node aliases are configured on Unified CM IM&P Administration (Messaging > Group Chat Server
Alias Mapping).
Alias Mapping).
■
Internal users do not need to use DNS to discover chat nodes; they get the chat room details from their local
IM&P servers.
IM&P servers.
chat.
75
Cisco Expressway Administrator Guide