DNS summary - Extensible messaging and presence protocol (XMPP) federation in Lync Server 2013
Topic Last Modified: 2014-04-08
To configure extensible messaging and presence protocol (XMPP) for your deployment, you create two Domain Name System (DNS) records in an external DNS server that will resolve the records to the Access Edge service of your Edge Server or Edge pool.
DNS Summary for Extensible Messaging and Presence Protocol
| Location/TYPE/Port | FQDN | IP address/FQDN host record | Maps to/Comments |
|---|---|---|---|
External DNS/SRV/5269 |
_xmpp-server._tcp.contoso.com |
xmpp.contoso.com |
XMPP proxy external interface on the Access Edge service or Edge pool.Repeat as necessary for all internal SIP domains with Lync enabled users where contact with XMPP contacts is allowed through the configuration of the External Access Policy through a global policy, site policy where the user is located, or user policy applied to the Lync-enabled user. An allowed XMPP domain must also be configured in the XMPP Federated Partners policy. See topics in See Also for additional details |
External DNS/A |
xmpp.contoso.com (for example) |
IP address of Access Edge service on your Edge Server or Edge pool hosting XMPP proxy |
Points to the Access Edge service or Edge pool that hosts the XMPP proxy service. Typically, the SRV record that you create will point to this host (A or AAAA) record |