Guidelines; Flags Controlling Cascade Layouts - Polycom RealPresence 800s Administrator's Manual

Collaboration server
Hide thumbs Also See for RealPresence 800s:
Table of Contents

Advertisement

Polycom® RealPresence Collaboration Server 800s Administrator's Guide
During
Cascading
Figure 5-1

Guidelines

To ensure that conferences can be cascaded and video can be viewed in all conferences the
following guidelines are recommended:

Flags controlling Cascade Layouts

For more details on defining system flags, see "Modifying System Flags" on page 21-1.
5-2
Video layout of Conf. B in
window of Conf. A
Video Layouts in Cascaded Conferences
The same version installed on all MCUs participating the cascading topology
The same license installed on all MCUs participating the cascading topology
Same Conference Parameters are defined in the Profile of the conferences participating
in the cascading topology
— Conference line rates should be identical
— Content rate should be identical
— Same encryption settings
DTMF codes should be defined with the same numeric codes in the IVR services
assigned to the cascading conferences
DTMF forwarding is suppressed
The video layout of the link is set to 1x1 by the appropriate system flag.
When the Mute Participants Except Lecturer option is enabled in the Conference
Profile, all participants (including the link participants) except the lecturer are muted.
Only the lecturer is not muted.
Setting the FORCE_1X1_LAYOUT_ON_CASCADED_LINK
_CONNECTION System Flag to YES (default) automatically forces the cascading link to
Full Screen (1x1) in CP conferences, hence displaying the speaker of one conference to a
full window in the video layout of the other conference.
Set this flag to NO when cascading between an Collaboration Server and an MGC that
is functioning as a Gateway, if the participant layouts on the MGC are not to be forced
to 1X1.
Setting the AVOID_VIDEO_LOOP_BACK_IN_CASCADE System Flag to YES
(default) prevents the speaker's image from being sent back through the participant
link from the cascaded conference. This can occur in cascaded conferences with
conference layouts other than 1x1. It results in the speaker's own video image being
displayed in the speaker's video layout.
This option is supported with Basic Cascading. If a Master MCU has two slave MCUs,
participants connected to the slave MCUs will not receive video from each other.
Video layout of Conf. A in
window of Conf. B
Polycom, Inc.

Advertisement

Table of Contents
loading

Table of Contents