Lync 2013 – XMPP Federation

Within Lync 2013, XMPP is first class service i.e. now we have native support – no gateway is required. This not only eases the deployment and manageability, but also provides scalability and high availability.

1. Get-CsXmppAllowedPartner (Returns information about XMPP partners authorized to communicate with your organization)
2. 
   Set-CsXmppAllowedPartner (Modifies an existing XMPP allowed partner)
3. 
   Get-CsXmppGatewaySettings (Returns information about the XMPP gateway configuration settings in use in the organization)
4. 
   Set-CsXmppGatewaySettings (Modifies the XMPP gateway configuration settings in use in the organization)

TOPOLOGY

XMPP support is defined in the topology on Site level:

 

…where the edge server used for federation route in the topology will be enabled automatically for XMPP support:

 To enable support for XMPP federation,  the Edge Federation must be enabled. To verify your setting, use Get-CsAccessEdgeConfiguration and examine “AllowFederatedUsers” parameter. If “False”, use: Set-CsAccessEdgeConfiguration -AllowFederatedUsers $true to enable federation.

***It is important to note that the above command will enable federation for all partners, not only XMPP – something the Administrator must consider before proceed further.

DNS

To enable support for XMPP Federation, a new SRV record for every supported SIP domain must be created in the Public DNS. For example:

SRV record for _xmpp-server._tcp.domain.com to resolve to the Access Edge FQDN of the Edge server and port must be set to 5269.

FIREWALL

The firewall must be configured to allow inbound and outbound connections for the Access edge IP address on TCP port 5269.

Additional steps

Next step is to configure XMPP allowed partner. This can be done via eitherControl Panel and Lync management Shell. To set Google Talk as XMPP partner:

New-CsXmppAllowedPartner gmail.com -TlsNegotiation NotSupported -SaslNegotiation NotSupported -EnableKeepAlive $false -SupportDialbackNegotiation $true

Alternatively via CSCP:

After replication, test the new XMPP setup - presence and IM capabilities: