Topic Last Modified: 2012-10-15
XMPP federation defines an external deployment based on the eXtensible Messaging and Presence Protocol (XMPP). An XMPP configuration allows Lync users access to XMPP domain users by:
-
IM and Presence – person to person only
-
Creation of XMPP federated contacts in the Lync client
When you configure policies for support of extensible messaging and presence protocol (XMPP) federated partners, the policies apply to users of XMPP federated domains, but not to users of session initiation protocol (SIP) instant messaging (IM) service providers (for example, Windows Live), or SIP federated domains. You configure an XMPP Federated Partner for each XMPP federated domain that you want to allow your users to add contacts and communicate with. Once the policies are in place, you need to configure the XMPP Gateway certificates.
 Note: |
|---|
| To begin the XMPP Gateway migration, you need to deploy the Lync Server 2013 XMPP Gateway, and configure access policies to enable users for Lync Server 2013 XMPP Gateway. All users must be moved to the Lync Server 2013 deployment before you perform these steps. For details, see Configure XMPP Gateway on Lync Server 2013. |
Configure an External Access
Policy to Enable Users for Lync Server 2013 XMPP Gateway
-
Open Lync Server Control Panel.
-
In the left navigation bar, click Federation and External Access, and then click External Access Policy.
-
Click New and then click User policy.
-
Enter a name for the external access user policy.
-
Provide a description for external access user policy.
-
Select Enable communications with federated users.
-
Select Enable communications with XMPP federated users.
-
Click Commit to save your changes to the site or user policy.