Polycom DOC2702A User Manual

Chapter 5-Cascading Conferences

Polycom, Inc.

The connection between the two conferences is created when a dial out IP participant is 

defined (added) to conference A whose dial out number is the dial-in number of the 

conference or Entry Queue running on MCU B.

Dial out IP participant in conference A dials out to the conference running on MCU B 

entering the number in the format: 

[MCU B Prefix/IP address][conference B ID]. 
For example, if MCU B prefix is 76 and the conference ID is 12345, the dial number is 

7612345.

When dialing to an Entry Queue, the dial out participant dials the MCU B prefix or IP 

address of MCU B and the Entry Queue ID in the format:
[MCU B Prefix/IP address][EQ B ID]. 
For example, if MCU B prefix is 76 and the Entry Queue ID is 22558, the dial number is 

7622558.
When the participant from conference A connects to the Entry Queue, the system plays to all 

the participants in Conference A the IVR message requesting the participant to enter the 

destination conference ID.
At this point, the Conference A organizer or any other participant in the conference can 

enter the required information for the IVR session using DTMF codes. For example, the 

meeting organizer enters the destination conference ID - 12345.
Any DTMF input from conference A is forwarded to the Entry Queue on MCU B to 

complete the IVR session and enable the move of the participant to the destination 

conference B.
Once the DTMF codes are entered and forwarded to the Entry Queue on MCU B, the IVR 

session is completed, the participant moved to the destination conference and the 

connection between the two conferences is established. 

In both dialing methods, the system automatically identifies that the dial in participant is an 

MCU and creates a Cascading Link and displays the link icon for the participant (

). The 

master-slave relationship is randomly defined by the MCUs during the negotiation process 

of the connection phase.

ISDN connection can be used to link between two MCUs or MCU and gateway and create a 

cascading conference. Content can be sent across the ISDN Cascading Link.

ISDN Cascaded links that support H.239 Content can be created between two gateways, 
gateway-to-MCU or between two MCUs in the following network topologies:
•