Realpresence Collaboration Server (Rmx) Network Port Usage - Polycom realpresence 1800 Administrator's Manual

No additional configuration is needed on the Collaboration Server.
Should a SIP Proxy failure occur in one of the RealPresence DMA system servers:
● The other RealPresence DMA system server takes over as SIP Proxy.
● Ongoing calls may be disconnected.
● Previously ongoing calls will have to be re-connected using the original IP address, registration and
connection parameters.
● New calls will connect using the original IP address, registration and connection parameters.
RealPresence Collaboration Server (RMX) Network
Port Usage
The following table summarizes the port numbers and their usage in the <Product Name>:
Server Network Port Usage Summary
Connection Port
Type Number
HTTP 80
HTTPS 443
DNS 53
DHCP 68
SSH 22
NTP 123
H.323 GK RAS 1719
H.323 Q.931 1720 -
incoming;
49152-599
99 -
outgoing
Polycom, Inc.
Protocol Description
TCP Management between the
Collaboration Server and
Collaboration Server Web Client.
TCP Secured Management between the
Collaboration Server and
Collaboration Server Web Client.
UDP Domain name server.
UDP Dynamic Host Configuration
Protocol.
TCP Secured shell. It is the Collaboration
Server terminal.
SSH is not supported when the
Collaboration Server is in Ultra
Secure Mode. For more information
see Ultra Secure
UDP Network Time Protocol. Enables
access to a time server on the
network.
UDP Gatekeeper RAS messages traffic.
TCP H.323 Q.931 call signaling.
Each outgoing call has a separate
port.
The port for each outgoing call is
allocated dynamically.
Configurable
No
No
Can be disabled in the IP
Network Service.
Can be disabled in the IP
Network Service.
No
Mode.
No
No
Yes - for outgoing calls
only.
It is configured in the
Fixed Ports section of the
IP service.
IP Network Services
531