Polycom realpresence 1800 - Realpresence Collaboration Server (RMX) Network Port Usage

IP Network Services
Polycom, Inc. 531
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
Type
Port
Number Protocol Description Configurable
HTTP 80 TCP Management between the
Collaboration Server and
Collaboration Server Web Client.
No
HTTPS 443 TCP Secured Management between the
Collaboration Server and
Collaboration Server Web Client.
No
DNS 53 UDP Domain name server. Can be disabled in the IP
Network Service.
DHCP 68 UDP Dynamic Host Configuration
Protocol.
Can be disabled in the IP
Network Service.
SSH 22 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 Mode.
No
NTP 123 UDP Network Time Protocol. Enables
access to a time server on the
network.
No
H.323 GK RAS 1719 UDP Gatekeeper RAS messages traffic. No
H.323 Q.931 1720 -
incoming;
49152-599
99 -
outgoing
TCP H.323 Q.931 call signaling.
Each outgoing call has a separate
port.
The port for each outgoing call is
allocated dynamically.
Yes - for outgoing calls
only.
It is configured in the
Fixed Ports section of the
IP service.