Filter
Top Products
Appendix G-Setting the Collaboration Server for Integration Into Microsoft Environment
Polycom, Inc. G-3
Collaboration Server Integration into the Microsoft Lync
Server 2010 and Lync Server 2013 Environments
From Version 7.8, the The RMX interoperability level with Lync 2013 is identical to Lync
2010. Lync 2013 is backward compatible with all RMX Lync 2010 features.
In the Lync Server 2010 environment, only the Matched URI dialing (using the SIP URI
address) is available as the call routing method.
Configuring the Polycom-Microsoft Solution
See the Polycom Unified Communications Deployment Guide for Microsoft Environments,
“Deployment Process for Polycom Collaboration Server Systems” for detailed steps on how to
deploy a Polycom Collaboration Server system for use with the video conferencing solution
in Microsoft Lync Server 2010 environment.
Media Over TCP
Media is automatically transmitted through TCP when UDP, the default transport protocol,
is not available.
The media transport protocol type (UDP/TCP) is displayed in the Participant Properties -
Channel Status - Advanced dialog box.
The media transport protocol type is displayed for the following IP addresses:
• Collaboration Server IP Address
• Participant IP Address
Network Error Recovery
When a short network error occurs, for example 5 seconds, Collaboration Server
automatically recovers, enabling calls in Microsoft Lync to continue the video or audio
conference without disconnecting. However, when a longer network error occurs, the call is
disconnected. The presence status mode is correctly updated from Busy to Available. There is
no configuration required for this procedure.
SIP Dialog Recovery
Collaboration Server has the ability to automatically recover from a SIP dialog failure, which
can occur in long duration calls in Meeting Rooms using the Microsoft Lync client. There is
no configuration required for this procedure.
Non-Lync endpoints connected to the same CP AVC-based conference as Lync endpoints running
on the Collaboration Server, cannot participate in the desktop sharing session initiated by Lync
participants.