Sending Content To Legacy Endpoints - Polycom realpresence 1800 Administrator's Manual

● Gateway calls are implemented as cascaded links, typically SIP, in which case, content cannot be
shared via the content channel. It may be viewed over the people video layout, depending on Legacy
configuration (see
When a Master MCU is not in Exclusive Content Mode,
snatch the content,
ENABLE_CONTENT_SNATCH_OVER_CASCADE system flag is NO.

Sending Content to Legacy Endpoints

The Content to Legacy feature is applicable for CP conferences, and in mixed CP and SVC
conferences, for AVC endpoints only.
The Collaboration Server can be configured to send content to endpoints not supporting the conference
content parameters (legacy endpoints) over the people video layout, thus allowing the participants to view
content. However, these endpoints cannot share content.
Guidelines for Sending Content to Legacy Endpoints
● A separate HD video resource is allocated to the conference for content sending to legacy endpoints.
Allocation is performed only once a legacy content endpoint is connected to the conference, and a
content session is initiated and transmitted via the people video layout. Once the resource is
allocated, it remains allocated to the conference until its end.
If the system cannot allocate the resource required for sending the content, the conference status
changes to Content Resource Deficiency, and content cannot be sent to the legacy endpoints.
● Endpoints receiving content via the people video layout, use the same video protocol and resolution
they use for receiving video.
● Content cannot be sent to Legacy endpoints when Same Layout mode is selected for the conference.
● This option in not supported in Video Switching conferences.
● Content can be sent to Legacy endpoints in gateway calls, depending on content configuration on
Master/Slave MCUs (for example, if the gateway conference is using H.263 content media protocol,
and the conference MCU is using H.264 content media protocol).
● FX endpoints dialing into the MCU, share content via the content channel (People+Content), whereas
FX endpoints dialing out to the MCU, view content via the people video layout.
Content Display on Legacy Endpoints
When content is sent to content legacy endpoints, their video layout automatically changes to the content
layout defined by the system flag LEGACY_EP_CONTENT_DEFAULT_LAYOUT (default layout is
CP_LAYOUT_1P4VER), and the content is shown in the larger/top-left cell. The video layouts of the other
conference participants do not change. (To modify the default layout, see
LEGACY_EP_CONTENT_DEFAULT_LAYOUT
The switch to the content layout occurs in Auto Layout, Presentation Mode, Lecture Mode, and when a
layout is selected for the conference.
In Lecture Mode, when content is sent to legacy endpoints, switching to the content layout, results in the
content shown in the lecturer/speaker window, while the lecturer is shown in the second window. If the layout
Polycom®, Inc.
Sending Content to Legacy
even if the value of the
Endpoints).
another participant in the same MCU may
Flag.)
Sharing Content During Conferences
-
135