19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Polycom</strong> <strong>RMX</strong> 1500/<strong>2000</strong>/4000 Administrator’s <strong>Guide</strong><br />

[Conference/Meeting Room/Entry Queue ISDN/PSTN number] - the dial-in<br />

number assigned to the Entry Queue/Meeting Room/Conference defined on MCU B,<br />

including the required country and area codes.<br />

Information required that is not part of the dialing string:<br />

[Destination Conference ID] - Only if using the Entry Queue on MCU B for routing<br />

calls or creating new ad hoc conferences. The ID of the destination conference on MCU B.<br />

The dialing string format:<br />

*<br />

For Example:<br />

GW A prefix in Gatekeeper - (not used with SIP) 22<br />

Gateway Profile ID in GW A 9999<br />

ISDN Dial-in Number assigned to the<br />

Entry Queue/MR/conference 4444100<br />

H.323 participant dials: 229999*4444100.<br />

SIP participant dials (if Central Signaling IP address of Gateway A is 172.22.177.89): 9999@<br />

172.22.177.89 IP* 4444100.<br />

If dialing an Entry Queue, when prompted for the Destination number enters 3456 followed<br />

by the pound key (#) using DTMF codes to create a new conference or join an ongoing<br />

conference with that ID.<br />

MCU to MCU Calls via ISDN Cascading Link<br />

A dial out ISDN participant is defined (added) to conference A running on MCU A. The<br />

participant’s dial out number is the dial-in number of the Entry Queue or conference<br />

running on MCU B (for example 54145106).<br />

MCU A dials out to an Entry Queue or conference B running on MCU B using the Entry<br />

Queue number (for example 54145106) or the conference number.<br />

When the participant, who is a dial-in participant in conference B, connects to the Entry<br />

Queue, the system plays to all the participants in Conference A the IVR message requesting<br />

the participant to enter the destination conference ID (or if connecting to a conference<br />

directly, the participant is requested to enter the conference password).<br />

At this point the Conference A organizer or any other participant in the conference can enter<br />

the required information for the IVR session using DTMF codes. For example, the meeting<br />

organizer enters the destination conference ID - 12345.<br />

Any DTMF input from conference A is forwarded to the Entry Queue on MCU B to<br />

complete the IVR session and enable the move of the participant to the destination<br />

conference B.<br />

Once the DTMF codes are entered and the IVR session is completed, the participant is<br />

connected to the conference and the connection between the conferences is established. The<br />

system automatically identifies the calling participant as an MCU and the connection is<br />

identified as a cascading link and the cascading link icon is displayed for the participant.<br />

( ).<br />

4-8 <strong>Polycom</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!