19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Polycom</strong> <strong>RMX</strong> 1500/<strong>2000</strong>/4000 Administrator’s <strong>Guide</strong><br />

MIH Cascading <strong>Guide</strong>lines<br />

Master and Slave Conferences<br />

• In MIH Cascading conferences, although there are multiple levels of Master and Slave<br />

relationships between conferences, the conference that runs on the MCU on level 1 of<br />

the hierarchy must be the Master for the entire cascading session. When an MGC is part<br />

of the cascading topology, it must be set as Level 1 MCU, unless MGC <strong>Version</strong> 9.0.4 is<br />

installed.<br />

• Conferences running on MCUs on levels 2 and 3 and can be both Masters and Slaves to<br />

conferences running on MCUs on levels above and below them.<br />

• All conferences running on MCUs on level 4 are Slave conferences.<br />

• When the DST MCS 4000 is on level 3 and acting as slave to level 2, the <strong>RMX</strong> on level 2<br />

must dial out to it in order for the DST MCS 4000 to be identified as slave. The link<br />

between the two MCU (dial out participant) is defined as a standard participant and not<br />

as a cascading link.<br />

Cascade Links<br />

Conference B<br />

Slave Conference of A<br />

Master of Conferences D and E<br />

Conference A Master of Conferences B and C<br />

Conferences D & E<br />

Slaves of Conference B<br />

Figure 4-4 MIH Cascading – Master-Slave Relationship<br />

Conference C<br />

Slave Conference of A<br />

Master of Conferences<br />

F and G<br />

Conferences F & G<br />

Slaves of Conference C<br />

Participant<br />

Connections<br />

Video Session Mode, Line Rate and Video Settings<br />

The types of MCUs, their position in the cascade topology and the endpoint capabilities<br />

(HD/CIF and H.263/H.264) determine the Video Session Mode of the MIH Cascading<br />

conference.<br />

• When creating a cascading link between two <strong>RMX</strong>s:<br />

— The <strong>RMX</strong>s operate in CP (Continuous Presence) mode.<br />

• When creating a cascading link between MGCs and <strong>RMX</strong>s:<br />

— If there are no MGCs on level 2, the MGCs can operate in either in CP or VSW<br />

(Video Switching) mode.<br />

— If there are MGCs on level 2, the MGCs can only operate in VSW mode.<br />

• When creating a cascading link between two MGCs:<br />

— The MGCs must be configured to operate in VSW mode.<br />

For more details about the MGC to MGC connection, see the MGC Manager User’s<br />

<strong>Guide</strong>, Volume II, Chapter 1, “Ad Hoc Auto Cascading and Cascading Links”.<br />

• To enable the connection of the links between cascaded conferences, they must run at<br />

the same line rate.<br />

4-28 <strong>Polycom</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!