Filter
Top Products
Chapter 15-Gateway Calls
15-10
• Unreached - the number could not be resolved by the gatekeeper or
the SIP proxy or could not be found on the network. In such a case,
the system will try to connect using another communication protocol.
• Failed - any reason causing the system not to complete the connection
process. In such a case, the system will try to connect using another
communication protocol.
You can hide the connection indications by changing the system
configuration. For more details, see "Displaying the Connection Information -
System Configuration” on page 15-21.
Gateway Functionality
The following features and capabilities are supported in gateway calls:
• Gateway Sessions are in CP mode only.
If High Definition Video Switching is selected in the Profile assigned
to the Gateway Session, the system ignores this setting and will run the
Gateway Session in CP mode.
• H.239 Content
• FECC (IP participants)
• Recording. The Recording Link is not considered as a participant and
therefore, the gateway session will automatically end when only one
of the participants remains connected in addition to the recording
link. The video of the Recording Link is not included in the display of
the video of the gateway call.
• Forwarding of DTMF codes from the Gateway Session to a conference
running on another gateway, MCU or DMA. This enables the
participant to enter the required conference and/or chairperson
password when connecting to another conference.
DTMF forwarding is enabled when there are only two participants
connected to the Gateway Session.
• Up to 80 gateway calls (same as conferences) may be run on a fully
configured RMX 2000/4000.
• Gateway Profiles are included in the Backup and Restore Configuration
operations.
• CDR files are generated for Gateway Sessions in the same way as for
conferences.