19.08.2013 Views

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 5-Address Book<br />

5-8<br />

Table 5-2 New Participant – General Properties (Continued)<br />

Field Description<br />

Extension/<br />

Identifier String<br />

Dial-out participants that connect to an external device<br />

such as Cascaded Links or Recording Links may be<br />

required to enter a conference password or an<br />

identifying string to connect. Enter the required string<br />

as follows:<br />

[p]…[p][string]<br />

For example: pp4566#<br />

p - optional - indicates a pause of one second before<br />

sending the DTMF string. Enter several concatenated<br />

[p]s to increase the delay before sending the string.<br />

The required delay depends on the configuration of<br />

the external device or conference IVR system.<br />

String - enter the required string using the digits 0-9<br />

and the characters * and #. The maximum number of<br />

characters that can be entered is identical to the<br />

H.323 alias length.<br />

If the information required to access the device/<br />

conference is composed of several strings, for<br />

example, the conference ID and the conference<br />

password, this information can be entered as one<br />

string, where pauses [p] are added between the<br />

strings for the required delays, as follows:<br />

[p]…[p][string][p]…[p] [string]...<br />

For example: p23pp*34p4566#<br />

The <strong>RMX</strong> automatically sends this information upon<br />

connection to the destination device/conference. The<br />

information is sent by the <strong>RMX</strong> as DTMF code to the<br />

destination device/conference, simulating the<br />

standard IVR procedure.

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

Saved successfully!

Ooh no, something went wrong!