Polycom 1500/1800/2000/4000 Manual De Usuario
Defining Cascading Conferences
Polycom®, Inc.
233
The dialing string format:
<GW A Prefix in GK><Gateway Profile_ID on GW A>*<ISDN Number assigned to the
Meeting Room/Conference/Entry Queue>
For Example:
Meeting Room/Conference/Entry Queue>
For Example:
SIP participant dials (if Central Signaling IP address of Gateway A is 172.22.177.89) 9999@
172.22.177.89 IP* 4444100
If dialing an Entry Queue, when prompted for the Destination number enters 3456 followed by the pound
172.22.177.89 IP* 4444100
If dialing an Entry Queue, when prompted for the Destination number enters 3456 followed by the pound
key (#) using DTMF codes to create a new conference or join an ongoing conference with that ID.
MCU to MCU Calls via ISDN Cascading Link
A dial out ISDN participant is defined (added) to conference A running on MCU A. The participant’s dial out
number is the dial-in number of the Entry Queue or conference running on MCU B (for example 54145106).
MCU A dials out to an Entry Queue or conference B running on MCU B using the Entry Queue number (for
example 54145106) or the conference number.
When the participant, who is a dial-in participant in conference B, 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 (or if connecting to a conference directly, the participant is requested to enter the
conference password).
number is the dial-in number of the Entry Queue or conference running on MCU B (for example 54145106).
MCU A dials out to an Entry Queue or conference B running on MCU B using the Entry Queue number (for
example 54145106) or the conference number.
When the participant, who is a dial-in participant in conference B, 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 (or if connecting to a conference directly, the participant is requested to enter the
conference password).
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.
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.
and enable the move of the participant to the destination conference B.
Once the DTMF codes are entered and the IVR session is completed, the participant is connected to the
conference and the connection between the conferences is established. The system automatically identifies
the calling participant as an MCU and the connection is identified as a cascading link and the cascading link
icon is displayed for the participant (
conference and the connection between the conferences is established. The system automatically identifies
the calling participant as an MCU and the connection is identified as a cascading link and the cascading link
icon is displayed for the participant (
).
RealPresence Collaboration Server Configuration Enabling ISDN Cascading Links
To enable Gateway-to-Gateway, Gateway-to-MCU and MCU-to-MCU calls over ISDN Cascading links, the
following configurations are required:
following configurations are required:
● Modifying the IP Network Service to include the MCU Prefix in the Gatekeeper (in the Gatekeepers
● ISDN Network Service is configured in both MCUs. For more details,
.
● Configuring a Gateway Profile and assigning dial-in ISDN/PSTN numbers. For details, see
GW A prefix in Gatekeeper - (not used with SIP)
22
Gateway Profile ID in GW A
9999
ISDN Dial-in Number assigned to the Entry Queue/MR/conference
4444100
H.323 participant dials
229999*4444100