Filter
Top Products
Sharing Content During Conferences
Polycom®, Inc. 138
Content Sharing Related Issues
Sharing Content in Cascaded Environments
In cascaded environments, content must be shared using the same content rate, and in H.264 conferences,
the same resolution and frame rate as well.
Sharing content has different constraints and guidelines over each of the signaling protocols:
● Over H.323 cascaded links -
Fixed content rate is used.
In cascading environments with non-Polycom MCUs, the Polycom MCU must be defined as
Master
For H.263 cascading links:
The cascading link must be created before connecting the participants.
The cascaded link’s Master/Slave role must be determined, in topologies including more than
two MCUs.
The value of the content-related system flag H263_ANNEX_T must be identical in both Master
and Slave MCUs.
For H.264 cascading links, the following should be determined in advance:
The cascaded link’s Master/Slave role must be configured for the link’s participants.
The H.264 Cascade Optimized content protocol must
be selected.
High/Base profile must be configured identically between Master and Slave. Endpoints with
lower capabilities cannot share content, and can only view content on the people video layout
(see Sending Content to Legacy Endpoints).
● Over ISDN - For information on sharing content over ISDN cascaded links, see Basic Cascading
Using ISDN Cascaded Link.
● Over SIP - No content sharing is supported over SIP cascaded links.
Sending Content to Legacy Endpoints
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.
• 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 Sending Content to Legacy Endpoints).
• Content cannot be snatched in cascaded environments.
The Content to Legacy feature is applicable for CP conferences, and in mixed CP and SVC
conferences, for AVC endpoints only.