EasyManua.ls Logo

Polycom realpresence 1800 - MIH Cascading Guidelines in CP Licensing; Master - Slave Conferences

Polycom realpresence 1800
449 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Cascading Conferences
Polycom, Inc. 92
DST MCS 4000 and other MCUs can be deployed on levels 3 and 4.
DST MCS 4000 MCUs connect as endpoints to the RMXs or MGCs on higher levels.
MIH Cascade Levels
MIH Cascading Guidelines in CP Licensing
Master - Slave Conferences
It is recommended to have RMX systems at all levels to leverage the high quality video and content
offered by the RMX.
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 can be
configured at any level if MGC Version 9.0.4 is installed, otherwise, it must be set as Level 1 MCU.
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 the lowest level in the configuration (for example, level 3 in a
3-level hierarchy configuration) 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.

Table of Contents

Other manuals for Polycom realpresence 1800

Related product manuals