RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

Polycom RMX 1500/2000/4000 Administrator’s Guide
• Gateway to MCU
Figure 6 Gateway to MCU/ MCU to Gateway Topology
In this topology, an IP participant calls a conference running on an MCU via a gateway
and over an ISDN link.
• MCU to MCU
Figure 7 Cascading Between Two MCUs Using an ISDN Link
In this topology, an ISDN participant from conference running on MCU A calls a
conference running on MCU B over an ISDN link.
Guidelines
RMX Gateway A RMX MCU B
• Content is restricted. When another endpoint wants to send content, the first endpoint
must stop sending content before the second endpoint can initiate or send content.
• Endpoints that do not support H.239 can receive the Content using the Send Content to
Legacy Endpoints option.
• When a participant joins a conference with active Content, content cannot be viewed by
the new participant. Restart the Content.
• Cascaded MCUs/Gateways must be registered with the same Gatekeeper or
neighboring Gatekeepers. MCUs and endpoints must also be registered with
Gatekeepers.
• Gateway/MCU calls require definition of IVR Services. For more information see
"Defining the IVR Service for Gateway Calls” on page 18-9
In version 7.1, H.239 content protocol is H.263 when sent over ISDN or H.323 Cascading link.
4-6 Polycom, Inc.