Filter
Top Products
RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide
5-34 Polycom, Inc.
Method I
Depending on the dialing direction, the following procedures must be performed:
For details on the participant definition on the Collaboration Server, see "Creating a Cascade
Enabled Dial-out/Dial-in Participant Link” on page 5-15.
For a detailed description of the participant definition in the MGC, see the MGC Manager
User’s Guide, Volume II, Chapter 1, Cascading Conferences.
Table 5-3 Set up Procedures according to the Dialing Direction
Dialing
Direction
Collaboration Server - Level 1 MGC - Level 2
MGC to
Collaboration
Server
Set the appropriate flags (done once
only).
Set the appropriate flags (done once
only).
Define the conference setting and
its line rate to be the same as the
one set on the Collaboration Server.
Define the conference setting and its line
rate to be the same as the one set on the
MGC.
Define the dial-in participant
(Cascaded Link) with the calling
number from the MGC.
The alias that will be used to identify
the dial-in participant can be the
name of the calling slave
conference.
Set the Cascading option as Master.
Define the dial-out participant (Cascaded
Link) to the conference running on the
Collaboration Server. Set the dial-out
alias to be the prefix of the MCU and the
name of the master conference running
on the Collaboration Server.
Collaboration
Server to MGC
Set the appropriate flags (done once
only)
Set the appropriate flags (done once
only)
Define the conference setting and
its line rate to be the same as the
one set on the Collaboration Server.
Define the conference setting and its line
rate to be the same as the one set on the
MGC.
Define the dial-out participant
(Cascaded Link). Set the dial-out
alias to be the prefix of the MGC
and the name of the slave
conference running on the MGC.
Set the Cascading option as Master.
Define the dial-in participant (Cascaded
Link) to the conference running on the
Collaboration Server.
The alias that will be used to identify the
dial-in participant can be the name of the
calling slave conference.
To enable Content sharing between the Collaboration Server and the MGC, the rate allocated to the
content must be identical in both conferences. Make sure that the line rate set for both conferences,
and the Content Settings (Graphics, Hi-res Graphics or Live video) are selected correctly to ensure
the compatible rate allocation. For more details on the Collaboration Server rate allocation to the
Content channel, see "SIP BFCP Content Capabilities” on page 4-3.