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

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

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

Connection Indications<br />

Chapter 18-Gateway Calls<br />

Gateway Sessions are monitored in the same way as the conferences. For more details on<br />

monitoring conferences, see <strong>RMX</strong> <strong>2000</strong> Administrator’s <strong>Guide</strong>, "Conference Level Monitoring”<br />

on page 12-3.<br />

During the connection process to the other endpoints, the system displays on the calling<br />

participant’s screen the called number and the connection status.<br />

A Maximum of 32 characters can be displayed for connection indications. If the displayed<br />

information is longer than 32 characters the text is truncated.<br />

If the system dials out to only one destination endpoint, the dialed number is not shown,<br />

only the connection status.<br />

If the destination endpoint is ISDN, the system displays the connection progress in<br />

percentages, where the percentages represent various stages in the connection process as<br />

follows:<br />

• Up to 60% the connection of the ISDN channels (up to 30 channels can be connected<br />

when E1 is used for the connection).<br />

• 60% - 80% BONDING stage<br />

• 80% - 90% Capability exchange stage<br />

• 90% - 99% Media connection stage<br />

Once the call is completed, the indications are cleared.<br />

If the call is not completed after trying all possible protocols, the system displays the<br />

number that was dialed on the calling endpoint’s screen and one of the following causes:<br />

• Busy - the far endpoint is in another call. In such a case, the system does not try to<br />

connect using another communication protocol.<br />

• Rejected - the far endpoint has rejected the call. In such a case, the system will try to<br />

connect using another communication protocol.<br />

• Unreached - the number could not be resolved by the gatekeeper or the SIP proxy or<br />

could not be found on the network. In such a case, the system will try to connect using<br />

another communication protocol.<br />

• Failed - any reason causing the system not to complete the connection process. In such a<br />

case, the system will try to connect using another communication protocol.<br />

You can hide the connection indications by changing the system configuration. For more<br />

details, see "System Configuration” on page 18-16.<br />

Gateway Session Parameters<br />

Additional ISDN and PSTN Participants cannot dial in directly to the Gateway Session once it was<br />

started.<br />

Gateway Session Name<br />

The <strong>RMX</strong> creates a new conference that acts as a Gateway Session with a unique ID whose<br />

display name is composed of the following components:<br />

• The prefix GW_,<br />

• The Gateway Profile display name. For example, Default_GW_Session<br />

• (number) where the number is a gateway conference counter.<br />

<strong>Polycom</strong>, Inc. 18-17

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

Saved successfully!

Ooh no, something went wrong!