RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Administrator’s Guide
Polycom®, Inc. 167
Sending Content to Legacy Endpoints (AVC Only)
The Collaboration Server can be configured to send Content to IP (H.323/SIP) or ISDN (Collaboration
Server 1500/2000/4000) endpoints that do not support H.239 Content (legacy endpoints) over the video
(people) channel, allowing the participants using legacy endpoints to view Content instead of the other
conference participants.

Guidelines for Sending Content to Legacy Endpoints

●This option is valid when sending Content as a separate stream is enabled in the System
Configuration and the flag: ENABLE_H239 is set to YES.
●One additional HD video resource is allocated to the conference when Content is sent to legacy
endpoints.
The allocation is done only when a legacy endpoint is connected to the conference and a Content
session is initiated and transmitted via the video channel. Once the resource is allocated, it remains
allocated to the conference until the conference ends.
If the system cannot allocate the resource required for sending the Content, the conference status
changes to Content Resource Deficiency, and Content will not be sent to the legacy endpoints.
As the resource required for sending Content to legacy endpoints is allocated on the fly, when
scheduling a reservation, in rare occasions when the MCU is fully loaded, Resource deficiency may
be encountered. This may prevent participants from connecting to the conference or from Content
being sent to the legacy endpoint. To ensure resource for sending Content to legacy endpoints, add
one resource to the number of resources defined in the Reserve Resources for Video Participants
field, in the Conference Properties - General dialog box.
●H.323, SIP, ISDN, and Telepresence non-H.239 (legacy) endpoints receive the Content via the video
channel using the same video protocol and resolution with which they receive video.
●The highest content resolution for legacy endpoints is: HD720p30.
●Once an endpoint is categorized as a Legacy Endpoint and receives the content over the video
channel, it remains in this mode without the ability to receive content over the Content channel.
●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.
●When content is transmitted, the Site Name of the endpoints cannot be viewed.
●Content can be sent to legacy endpoints in gateway calls.
●When moving a legacy participant to the Operator conference, content will not be available to the
legacy endpoint.
●A Polycom FX endpoint dialing in to a Collaboration Server with MPMx cards will receive content
using People + Content. An FX endpoint dialed out from a Collaboration Server with MPMx cards will
only receive content via the video channel using People + Content if Send Content to Legacy
Endpoints is enabled in the Conference Profile.

Content Display on Legacy Endpoints

When Contents is sent to legacy endpoints, their video layout automatically changes to a Content Layout
which is defined by the system flag LEGACY_EP_CONTENT_DEFAULT_LAYOUT and the Content is
shown in the larger/top left (speaker) window. The video layouts of the other conference participants do not
change.