Polycom 1500/1800/2000/4000 Life Jacket User Manual


  Open as PDF
of 1101
 
Appendix H - Deployment Into Microsoft Environments
Polycom®, Inc. 989
Sharing Content During a Conference
Two implementations of the Content Sharing Suite (CSS) are available in Lync 2010 and Lync 2013
environments:
RealPresence CSS Gateway
RealPresence CSS Plug in
RealPresence CSS Gateway
The CSS Gateway provides Content interoperability between Lync clients and non Lync clients in a
conference. Lync clients connected to a Lync AV MCU 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 CSS 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 CSS, eliminating the need for plug-ins. The CSS Plug in is still supported for backward compatibility.
For more information see:
RealPresence CSS Plug in
RealPresence® Content Sharing Suite Administrator Guide
Unified Communications Deployment Guide for Microsoft Environments
The Gateway allows Polycom endpoints, using native SIP BFCP, and Lync clients, using native RDP, to
share Content in a conference.
CSS Gateway Usage Guidelines
MS AV MCU Cascade is the only Deployment Architecture that is supported.
For more information see Deployment Architecture 2 - MS AV MCU Cascade.
One CSS RDP Gateway connection is supported per conference in the Collaboration Server, initiated by
the DMA through the CSS server.
There is no Lync client associated with the CSS Gateway connection and even if the AV MCU is empty the
CSS will be still be connected. The Collaboration Server does not consider the CSS RDP Gateway
connection as a participant and if the conferences on both the Collaboration Server and the AV MCU are
empty it will disconnect the CSS RDP Gateway and the AV MCU link.
When a Content sharing endpoint is detected by the Collaboration Server side the CSS RDP Gateway will
receive BFCP message triggering the RDP session on the Lync side of the topology.
RealPresence CSS Plug in
For backward compatibility the Collaboration Server supports Content sharing using either the CSS
Gateway or the lug-in based Content sharing solution, however not in the same conference.
Using Polycom CSS Plug in, Lync 2013 clients are able to share content in Polycom Content sessions in
both Collaboration Server Hosted calls and Cascaded Lync 2013 AVMCU calls, with both Lync 2010 & 2013
clients.