Polycom RealPresence 2000, Administrator'S Manual

Page: 250 / 1130

Polycom® RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide
5-14
Polycom, Inc.
Star Cascading Topology
In the Star topology (as well as in the Basic topology), the MCUs are usually installed at
different locations (states/countries) and participants connect to their local MCU to facilitate
the connection and save long distance call costs. Star Topology Cascading requires that all
cascaded MCUs reside on the same network.
Content sharing is available to all conferences over the H.323 Cascading Link.
In this topology, the MCUs are networked together using two modes:
•
Master-Slave Cascading
• Cascading via Entry Queue
Master-Slave Cascading
It is similar to MIH (Multi Hierarchy) cascading, with only two levels: one Master MCU on
level 1 and several Slave MCUs on level 2.
The cascading hierarchy topology can extend to four levels (Figure 5-9) and should be
deployed according to the following guidelines:
•
If an RMX is deployed on level 1:
—
RMX systems can be used on level 2
—
MGC with version 9.0.4 can be used on level 2 if RMX version 7.0.2 and higher is
deployed in level 1
• If an MGC is deployed on level 1:
— MGC or RMX can be used on level 2.
Figure 5-6 Master-Slave Star Cascading Topology
Although participants in Star Cascading conferences can connect to their local conference using
H.323, SIP and ISDN, the Cascading Links between conferences must connect via H.323.