Content Sharing Related Issues - Polycom realpresence 1800 Administrator's Manual

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
● Over ISDN - For information on sharing content over ISDN cascaded links, see
Using ISDN Cascaded
● Over SIP - No content sharing is supported over SIP cascaded links.
From version 8.6 and on, content can be snatched in cascaded environments, that is the content token
ownership can be taken/snatched by another participant wishing to share content where content is currently
shared by another participant.
This capability depends on the conference configuration (Exclusive Content Mode is off), and the
ENABLE_CONTENT_SNATCH_OVER_CASCADE system flag (see
ENABLE_CONTENT_SNATCH_OVER_CASCADE).
Guidelines for Content Snatching in Cascaded Conferences
● Content Snatching is available only over anH.323 cascaded link. It is not applicable to either SIP
(BFCP) or PSTN.
● All the MCUs within the (H.323) cascading topology should:
 Use RealPresence Collaboration Server version 8.6 and up.
 Have Exclusive Content Mode turned off (meaning, Exclusive Content Mode check-box in
conference profile Properties > Advanced tab should be cleared).
 Have the system flag ENABLE_CONTENT_SNATCH_OVER_CASCADE value set to YES.
Polycom®, Inc.
Endpoints).
Link.
Sharing Content During Conferences
Basic Cascading
134