Star Cascading Topology; Master-Slave Cascading - Polycom RMX 1500 Administrator's Manual

Polycom RMX 1500/2000/4000 Getting Started Guide

Star Cascading Topology

Master-Slave Cascading

3-18
System Flag Settings
The DTMF_FORWARD_ANY_DIGIT_TIMER_SECONDS flag
determines the time period (in seconds) that MCU A will forward DTMF
inputs from conference A participants to MCU B.
Once the timer expires, most of the DTMF codes (excluding five
operations as for IP links) entered in conference A will not be forwarded
to conference B. This is done to prevent an operation requested by a
participant individually (for example, mute my line) to be applied to all
the participants in conference B.
Flag range (in seconds): 0 - 360000
This flag is defined on MCU A (the calling MCU).
If a flag is not listed in the System Flags list it must be added to the
system.cfg file before it can be modified. For more details on defining
system flags, see "Modifying System Flags" on page 19-5.
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.
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.
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
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.