Chapter 2-Additional Conferencing Information
2-50
Cascading Conferences - Star Topology
Cascading enables administrators to connect one conference directly to
another conference using an H.323 connection, creating one large
conference. The conferences can run on the same MCU or different MCUs.
There are many reasons for cascading conferences, the most common are:
Connecting two conferences on different MCUs at different sites.
Utilizing the connection abilities of different MCUs, for example,
different communication protocols, such as, serial connections, ISDN,
etc....
The link between the two conferences is created when a participant that is
defined as a dial-out cascaded link in one conference (Conference A)
connects to the second conference (Conference B) via a special cascaded
Entry Queue (EQ). When MCU A dials out to the cascaded link to connect
it to conference A, it actually dials out to the cascaded Entry Queue
defined on MCU B.
Figure 2-3 Cascaded Conferences - Star Topology
Though the process of cascading conferences mentioned in this section
refers to conferences running on two different RMX units, it is possible to
cascade conferences running between RMX units and other MCUs.
Simple cascade links are treated as endpoints in CP conferences and are
allocated resources according to Table2-3 on page 2-6. Cascaded links in
1x1 video layout are in SD resolution.
In HD Video Switching, simple cascade links behave like HD endpoints if
all HD prerequisites are met - if not, the link is audio only.
Conference
A
Conference
B
MCU A MCU B
EQ
Cascaded
Link
Cascaded
Link