Current Publication | x
Close

System Ports

After installing a new Polycom RealPresence DMA system in a core, an edge, or a combination configuration, the default ports for all services should not overlap. This helps to avoid potential port conflicts.

The following table lists the inbound ports that may be open on the RealPresence DMA system and the outbound ports from which RealPresence DMA system traffic may originate. Port settings depend on signaling and security settings, integrations, and system configuration.

RealPresence DMA System Inbound and Outbound Ports

Port

Protocol

Direction

Description

10000 - 13000
UDP+TCP
inbound, outbound
Access proxy dynamic ports.
3268
TCP
outbound
Active Directory integration. Global Catalog.
8989
UDP
inbound, outbound
Cluster and supercluster communication
53
TCP+UDP
inbound
DNS. Only available if the embedded DNS server is enabled.
35001 - 40000
TCP
inbound, outbound
H.323 dynamic ports (H.245)
1720
TCP
inbound
H.323 H.225
1719
UDP
inbound
H.323 RAS
1718
UDP
inbound
H.323 RAS. Gatekeeper discovery (multi and uni-cast)
80
TCP
inbound
HTTP. Redirects to 443 (HTTP access is not allowed).
8080
TCP
inbound
HTTP. Redirects to 8443. Used for uploading upgrade packages and backups. During upgrades, the progress page is served from this port.  
443
TCP
inbound
HTTPS. Management interface access.
389
TCP
outbound
LDAP. Active Directory integration.
4449
TCP
inbound
Legacy LDAP port for Polycom CMA and RealPresence Resource Manager integration.
514
UDP
outbound
Log forwarding
8443
TCP
inbound
Management/API
40002-45500
UDP+TCP
inbound, outbound
Media traversal (private)
23002-28500
UDP+TCP
inbound, outbound
Media traversal (public)
636
TCP
outbound
Microsoft Active Directory integration
123
UDP
inbound
NTP (private only). Available only if an NTP server is specified in Time Settings.
3333
TCP
outbound
RealPresence Resource Manager licensing
9333
TCP
outbound
RealPresence Resource Manager licensing
3269
TCP
outbound
Secure Global Catalog. Active Directory integration.
13001 - 23000
UDP+TCP
outbound
SIP outbound ports (private)
13001 - 23000
UDP+TCP
outbound
SIP outbound ports (public)
5060
UDP+TCP
inbound, outbound
SIP signaling (default). Other ports can be configured in SIP Settings.
5061
TLS (TCP)
inbound, outbound
SIP signaling (default). Other ports can be configured in SIP Settings.
161
UDP
inbound
SNMP (private only). Default port; can be changed or disabled.
162
TCP/UDP
outbound
SNMP notifications (Traps or Informs). Used if SNMP is enabled and configured to send notifications, or if system is monitored with a RealPresence Resource Manager system.
22
TCP
inbound
SSH. Only available if Linux console access is enabled.
52000 - 60000
UDP+TCP
outbound
System generic ephemeral. May be used for miscellaneous outbound connections if a service/operation doesn't otherwise have a defined port range and the RealPresence DMA system needs to make network connections. For example, if auto configuring another RealPresence DMA peer (HA, VPN, Admin configuration menus), an ephemeral port may be used to initiate the HTTPS REST API call to the other system.
60002 - 65535
UDP
inbound, outbound
TURN relay
3478
UDP
inbound
TURN
5986
TCP/TLS
 
WinRM 2.0 communication during Polycom contact creation in Active Directory.

View System Port Ranges

You can view all current port assignments for a RealPresence DMA system from the management user interface.

Port assignments must be configured on the individual settings page for each service (for example, Access Proxy Settings).

To view system port ranges:

Go to Service Config > System Port Ranges.

The following port information displays:

Column

Description

Service
The service (function) that uses the port or port range.
First Port
For a port range, the beginning port in the range.
Last Port
For a port range, the ending port in the range.
<Network Interface>
The network interface(s) to which the listed service is assigned.

 

Related Topics

Machine Translation

You are cautioned that the translation of this document is generated by a machine; therefore, the translated document may have errors and be inconsistent with the original English language version of the document.

The English language version of this document shall be considered the governing document related to the Polycom product.

If there is any contradiction between the English language version of the document and the translated version of the document, the English language version of the document shall take precedence.

The translation is provided for your convenience only. Neither Google nor Polycom shall be responsible for translated content or for the performance of the translation tool. If you require further assistance on non-translation issues, please contact Polycom support.

Translated documents are not available in PDF format.