Appendix H - Integration Into Microsoft Environments
Polycom®, Inc. 760
When set to AUTO (default), the system uses the default resolution matrix based on the conference line
rate.
To change the default flag setting, add the MAX_RTV_RESOLUTION flag to the System Configuration flags
and set its value. For information, see the <Italic>RealPresence Collaboration Server 800s Administrator’s
Guide, the <Italic>RealPresence Collaboration Server 800s Administrator’s Guide, Modifying System
Flags.
The following table summarizes the Collaboration Server resources allocated to a Lync Client based on the
MAX_RTV_RESOLUTION flag setting, the connection line rate and the video resolution.
Selected video resolution based on flag setting and conference line rate and core processorThe following table
describes the number of allocated video resources for each video resolution when using the RTV protocol.
Allocated video resolutions per video resolution

Threshold HD Flag Settings using the RTV Video Protocol

The system flag MAX_ALLOWED_RTV_HD_FRAME_RATE defines the threshold Frame Rate (fps) in
which RTV Video Protocol initiates HD resolutions.
Flag values are as follows:
Default: 0 (fps) - Implements any Frame Rate based on Lync RTV Client capabilities
Range: 0-30 (fps)
For example, when the flag is set to 15 and the Lync RTV Client declares HD 720P at 10fps, because the
endpoint’s frame rate (fps) of 10 is less than flag setting of 15, then the endpoint’s video will open VGA and
not HD.
In another example, when the flag is set to a frame rate of 10 and the Lync RTV Client declares HD 720P
at 13fps, because the endpoint’s frame rate (fps) of 13 is greater than flag setting of 10, then the endpoint’s
video will open HD and not VGA
Sharing Content via the Polycom CSS Plug-in for Lync Clients
From version 8.1, Polycom CSS (Content Sharing Suite) Plug-in for Lync clients allows Lync clients to
receive and send Content on a separate channel, without having to use the video channel. Content is
transmitted using SIP BFCP.
When Lync clients connect, each endpoint is represented twice in the RMX Manager or Collaboration Server
Web Client. One connection represents the actual Lync client, while the second connection represents the
content channel via the Polycom plug-in.
The name of the plug-in “participant” is derived from the name of the Lync client with the suffix “_cssplugin”.
When a Lync client connects to a conference, the plug-in connects automatically, regardless of whether the
Lync client dials into a conference or is called from the MCU.