Sharing Content During A Conference - Polycom realpresence 1800 Administrator's Manual

If the CROPPING_PERCENTAGE_THRESHOLD_GENERAL System Flag value is set to 100, always
apply cropping with the exception of mobile aspect ratios. Mobile aspect ratios are those with a larger
vertical aspect than horizontal for example 3:4.
Example: A mobile Lync client sends 288x352 (3:4) aspect ratio. Cropping this resolution to 16:9 would
require the cropping of 190 pixels on the vertical aspect. The mismatch calculation would yield 190/352 ~54.
If the applicable System Flag's value is set to >= 54, striping, rather than cropping, is applied.
For more information see,

Sharing Content During a Conference

As part of supporting video conferencing in a Polycom-Lync environment, Polycom supplies Polycom®
ContentConnect® for Microsoft Lync environments (previously known as Content Sharing Suite, or CSS),
which enables content sharing between Lync and non-Lync conference participants.
During content sharing, content is sent from the Collaboration Server via H.264 to the ContentConnect
server, and from there via Microsoft Remote Desktop Protocol to the Lync AVMCU, and vice versa.
Note: Content in RealConnect Environments
In conferences using Polycom® RealConnect™ technology between remotes premises, content is
shared using Polycom® ContentConnect for Microsoft environments.
In this scenario, content sharing requires one of the following:
• Content transmission method is set to Multiple Content Resolutions, with the H.263 check-box
selected.
• H.264 Cascade Optimized (see
• H.264 HD (likewise)
Two implementations of the Polycom® ContentConnect™ (previously known as CSS - Content Sharing
Suite) are available in Lync 2010 and Lync 2013 environments:
● Polycom® ContentConnect™ Gateway
● Polycom® ContentConnect™ Plug in
RealPresence Polycom® ContentConnect™ Gateway
The Polycom® ContentConnect™ Gateway provides Content interoperability between Lync clients and non
Lync clients in a conference. Lync clients connected to a Lync AVMCU use their native Content protocol,
RDP (Remote Desktop Protocol) and Polycom endpoints, use their native SIP BFCP Content protocol, to
send or receive Content, to or from the Polycom® ContentConnect™ Gateway, which renders a RDP
SIP BFCP Content stream.
The Gateway functionality was previously enabled by a combination of: Content Add-on for Lync; Content
Sharing Server; and BFCP Content-Only Client Plug-in. These functionalities have been incorporated into
the Polycom® ContentConnect™, eliminating the need for plug-ins. The Polycom® ContentConnect™ Plug
in is still supported for backward compatibility.
For more information see:
RealPresence Polycom® ContentConnect™ Plug in
RealPresence® ContentConnect Administrator Guide
Unified Communications Deployment Guide for Microsoft Environments
Polycom®, Inc.
Modifying System Flags
MCU Usage Modes of Content
Appendix H - Deployment Into Microsoft Environments
.
Protocols)

1000