Table 2-3
Bidirectional Ports to Open on the Scopia Elite 6000 Series MCU
Port Range
Protocol Destination
Functionality
Result of Blocking
Port
Required
1024-1324
H.245
(TCP)
Any H.323
device
Enables H.245
signaling
Cannot connect H.323
calls
Mandatory
To configure, see
“Configuring the TCP Port
Range for H.245 on the
Scopia Elite MCU” on page
38
1719
RAS
(UDP)
H.323
gatekeeper
Enables RAS
signaling
Cannot communicate
with H.323
gatekeeper
Mandatory
To configure, see
“Configuring the UDP Port
for RAS on the Scopia Elite
MCU” on page 40
and
“Configuring the UDP Port
for the Gatekeeper on the
Scopia Elite MCU” on page
41
1720
Q.931
(TCP)
Any H.323
device
Enables Q.931
signaling
Cannot connect H.323
calls
Mandatory
To configure, see
“Configuring the TCP Port
Q.931 on the Scopia Elite
MCU” on page 42
3336
XML
(TCP)
Conference
Control web
client
endpoint,
Scopia
Management,
or third-party
controlling
applications
Enables you to
manage the MCU
via the XML API
Cannot use MCU
Conference Control
web user interface.
Cannot use XML API to
control MCU.
Mandatory if deployed with
Scopia Management
3337
XML
(TCP)
Other MCUs
Enables use of MCU
Cascading XML API
Cannot cascade
between two MCUs
Mandatory if multiple
MCUs are deployed with
Scopia Management
3338
XML
(TCP)
Scopia
Management,
or third-party
configuration
applications
Enables you to
configure the MCU
via the XML API
Cannot configure MCU
via the XML API
Mandatory if deployed with
Scopia Management
RADVISION | Installation Guide for Scopia Elite 6000 Series MCU Version 8.0
Planning your MCU Deployment | 13
