Topic Last Modified: 2012-12-23
For details about licensing requirements and how to complete the provisioning process, see the "Public IM Connectivity Provisioning Guide for Microsoft Lync Server, Office Communications Server, and Live Communications Server" at http://go.microsoft.com/fwlink/p/?linkId=155970
If you are implementing audio/video (A/V) federation with Windows Live Messenger, there are two parameters that you need to modify: the Lync Server encryption level and the EnablePublicCloudAccess policy. By default, the encryption level is set to Required. You must change this setting to Supported. If the EnablePublicCloudAccess policy is set to false, this needs to be set to True. You can do this from the Lync Server Management Shell.
|More than ever, Lync is a powerful tool for connecting across organizations and with individuals around the world. Federation with Windows Live Messenger requires no additional user/device licenses beyond the Lync Standard Client Access License (CAL). Next year, Skype federation will be added to this list, enabling Lync users to reach hundreds of millions of people with IM and voice.|
Configure Federation for Windows Live
Start the Lync Server Management Shell on the Front End server: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Management Shell.
From the command prompt, type the following commands:
Set-CsMediaConfiguration -EncryptionLevel SupportEncryption
Set-CsExternalAccessPolicy Global -EnablePublicCloudAccess $true -EnablePublicCloudAudioVideoAccess $true
Note: This is required step because Windows Live Messenger does not support encryption of audio/video. The command sets your global policy to a support encryption setting instead of requiring encryption of the audio/video data. Clients that support encryption will still use encryption, such as Lync 2013.