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

Call Flows<br />

IP Participants<br />

Call flow changes according to the connection protocols: IP or ISDN. This section describes<br />

the call flows between two endpoints connect via one gateway. For call flows describing<br />

connections between two endpoints via two gateways, or a connection of an endpoint to a<br />

conference running on MCU via a gateway, see "Basic Cascading using ISDN Cascaded Link”<br />

on page 4-5.<br />

Two calling methods are available:<br />

• Direct - the dialing string includes the destination number/conference ID and the call is<br />

routed directly to the destination endpoint/conference. This is the recommended<br />

method.<br />

• Via Gateway IVR - the call connects to the gateway, where through interaction with<br />

the IVR, the destination number is entered using DTMF codes.<br />

Direct Dialing<br />

The calling endpoint enters the dialing string that includes the access numbers to the <strong>RMX</strong><br />

Gateway Profile and the number of the destination endpoint. Up to 10 destination numbers<br />

can be entered in one string.<br />

The call connects to the <strong>RMX</strong> Gateway Profile and a Gateway Session is created. The dial-in<br />

participant is automatically connected to it.<br />

During the connection phase, the number being dialed is displayed on the screen of the<br />

calling endpoint.<br />

If the call is not answered or it cannot be completed using one communication protocol, the<br />

system will try to connect the endpoint using the next communication protocol according to<br />

the selected protocols in the following order: H.323, SIP and ISDN. PSTN numbers are<br />

identified separately and are dialed immediately without trying other connections.<br />

If the call is busy, the system will not try to connect the endpoint using another protocol.<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 the reason for not completing<br />

the call. For details, see "Connection Indications” on page 18-17.<br />

When the call is connected, a new Gateway Session is created and added to the ongoing<br />

Conferences list.<br />

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

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

Saved successfully!

Ooh no, something went wrong!