Mih Cascading Guidelines - Polycom RMX 1500 Administrator's Manual

Polycom RMX 1500/2000/4000 Getting Started Guide
3-36

MIH Cascading Guidelines

Master and Slave Conferences
• In MIH Cascading conferences, although there are multiple levels of
Master and Slave relationships between conferences, the conference
that runs on the MCU on level 1 of the hierarchy must be the Master
for the entire cascading session. When an MGC is part of the
cascading topology, it must be set as Level 1 MCU, unless MGC
Version 9.0.4 is installed.
• Conferences running on MCUs on levels 2 and 3 and can be both
Masters and Slaves to conferences running on MCUs on levels above
and below them.
• All conferences running on MCUs on level 4 are Slave conferences.
• When the DST MCS 4000 is on level 3 and acting as slave to level 2,
the RMX on level 2 must dial out to it in order for the DST MCS 4000
to be identified as slave. The link between the two MCU (dial out
participant) is defined as a standard participant and not as a
cascading link.
Cascade Links
Slave Conference of A
Master of Conferences D and E
Figure 3-4 MIH Cascading – Master-Slave Relationship
Video Session Mode, Line Rate and Video Settings
The types of MCUs, their position in the cascade topology and the
endpoint capabilities (HD/CIF and H.263/H.264) determine the Video
Session Mode of the MIH Cascading conference.
• When creating a cascading link between two RMXs:
— The RMXs operate in CP (Continuous Presence) mode.
Conference A
Conference B
Conferences D & E
Slaves of Conference B
Master of Conferences B and C
Conference C
Slave Conference of A
Master of Conferences
F and G
Conferences F & G
Slaves of Conference C
Participant
Connections