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 />

Table 15-6 Default IP Service – Conferencing – Gatekeeper Parameters (Continued)<br />

Field Description<br />

Refresh Registration<br />

every __ seconds<br />

Aliases:<br />

8 Click the Ports tab.<br />

The frequency with which the system informs the gatekeeper that it is<br />

active by re-sending the IP address and aliases of the IP cards to the<br />

gatekeeper. If the IP card does not register within the defined time<br />

interval, the gatekeeper will not refer calls to this IP card until it reregisters.<br />

If set to 0, re-registration is disabled.<br />

Note:<br />

• It is recommended to use default settings.<br />

• This is a re-registration and not a ‘keep alive’ operation – an<br />

alternate gatekeeper address may be returned.<br />

Alias The alias that identifies the <strong>RMX</strong>’s Signaling Host within the network.<br />

Up to five aliases can be defined for each <strong>RMX</strong>.<br />

Note: When a gatekeeper is specified, at least one alias must be<br />

entered in the table.<br />

Additional aliases or prefixes may also be entered.<br />

Type The type defines the format in which the card’s alias is sent to the<br />

gatekeeper. Each alias can be of a different type:<br />

• H.323 ID (alphanumeric ID)<br />

• E.164 (digits 0-9, * and #)<br />

• Email ID (email address format,<br />

e.g. abc@example.com)<br />

• Participant Number (digits 0-9, * and #)<br />

Note: Although all types are supported, the type of alias to be used<br />

depends on the gatekeeper’s capabilities.<br />

15-14 <strong>Polycom</strong>, Inc.

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

Saved successfully!

Ooh no, something went wrong!