Filter
Top Products
Appendix H - Integration Into Microsoft Environments
Polycom®, Inc. 789
Content Sharing Behavior by Lync Connection and MCU Type
Connection Type Content Sharing Behavior
Point to point: Lync client to
Lync client.
Microsoft Content is used for the entire session.
Lync calls MS AV MCU
conference with no
Collaboration Server cascade
participant.
Microsoft content is used until Collaboration Server will joins, from which time it
will switch to Polycom content
Lync calls VMR directly Polycom Content is used for the entire session.
Collaboration Server joins an
MS AV MCU conference
before Content sharing is
initiated.
Polycom Content is used until Collaboration Server leaves the conference.
Collaboration Server joins an
MS AV MCU conference while
Content is being shared.
When the CSS plug in of the Content speaker detects that Microsoft Content is
being sent by the Lync client, it automatically stops the Microsoft Content and
switches to Polycom Content and starts sending Polycom Content.
Polycom Content is used until the Collaboration Server leaves the MS AV MCU
conference.
CSS Behavior by Lync Content Type
Lync Content Type CSS Behavior
Desktop Sharing Send the desktop In cases where the is more than one monitor, the Lync client asks
which monitor to use and the CSS will comply.
Program Sharing Only the application is sent.
Power Point Sharing Not supported. CSS should not send the Power Point to the Collaboration Server but
the Lync clients will be able to send/receive the Power Point. CSS issues a notification
in the Lync Content presenter device stating that the Power Point cannot be shared
with non Lync devices.
Whiteboard Sharing Not supported. CSS should not send the whiteboard to the Collaboration Server but the
Lync clients will be able to send/receive the whiteboard. CSS issues a notification in the
Lync Content presenter device stating that the whiteboard cannot be shared with non
Lync devices.