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.

Gateway Calls<br />

Chapter 18-Gateway Calls<br />

The <strong>RMX</strong> can be used as a gateway that provides connectivity across different physical<br />

networks and translates multiple protocols for point-to-point rich media communications.<br />

The <strong>RMX</strong> supports the widest range of video and audio algorithms. It allows sites with<br />

different frame rates, connection speeds, audio algorithms, video resolutions and network<br />

protocols to transparently connect with one another. It also enables multipoint conference<br />

creation from an endpoint.<br />

A special conference acting as a Gateway Session is created on the <strong>RMX</strong>. It includes one dialin<br />

connection of the endpoint initiating the Gateway Session and one or several dial-out<br />

connections to endpoints. It provides connectivity between the various protocols: H.323,<br />

SIP, ISDN and PSTN.<br />

To enable the gateway functionality a special Gateway Profile is defined on the <strong>RMX</strong>.<br />

Gateway Functionality<br />

The following features and capabilities are supported in gateway calls:<br />

• Gateway Sessions are in CP mode only.<br />

If Video Switching is selected in the Profile assigned to the Gateway Session, the system<br />

ignores this setting and will run the Gateway Session in CP mode.<br />

— From <strong>Version</strong> 7.2, Gathering phase is not supported in gateway calls, even if it is<br />

defined in the Profile assigned to the Gateway Profile.<br />

• H.239 Content<br />

• FECC (IP participants)<br />

• Recording. The Recording Link is not considered as a participant and therefore, the<br />

gateway session will automatically end when only one of the participants remains<br />

connected in addition to the recording link. The video of the Recording Link is not<br />

included in the display of the video of the gateway call.<br />

• Forwarding of DTMF codes from the Gateway Session to a conference running on<br />

another gateway, MCU or DMA. This enables the participant to enter the required<br />

conference and/or chairperson password when connecting to another conference.<br />

DTMF forwarding is enabled when there are only two participants connected to the<br />

Gateway Session.<br />

• Forwarding of all DTMF codes sent by participants in the Gateway Session to all PSTN<br />

and ISDN participants. This is enabled by adding the<br />

ALWAYS_FORWARD_DTMF_IN_GW_SESSION_TO_ISDN System Flag to<br />

system.cfg and setting its value to YES.<br />

• Up to 80 gateway calls (same as conferences) may be run on a fully configured <strong>RMX</strong><br />

1500/<strong>2000</strong>/4000.<br />

• Gateway Profiles are included in the Backup and Restore Configuration operations.<br />

• CDR files are generated for Gateway Sessions in the same way as for conferences.<br />

• Cascading. To support cascading, the gateway indicates a lower number than the MCU<br />

for master-slave relation (directly or through DMA).<br />

• Gateway calls are supported in Microsoft and Avaya environments.<br />

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

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

Saved successfully!

Ooh no, something went wrong!