• Port Usage on VSX Systems

These tables list VSX system port usage. You may need this information when
you configure your network equipment for video conferencing.

The following table shows H.323 port usage.

Port / Function
80-Static / TCP HTTP interface (optional)
389-Static / TCP ILS registration (LDAP)
1503-Static / TCP T.120
1718-Static / TCP Gatekeeper discovery (must be bidirectional)
1719-Static / TCP Gatekeeper RAS (must be bidirectional)
1720-Static / TCP H.323 call setup (must be bidirectional)
1731-Static / TCP Audio call control (must be bidirectional)
8080-Static / TCP HTTP server push (optional)
1024-65535 / Dynamic TCP H245. Can be set to “Fixed Ports” on Polycom systems.
1024-65535 / Dynamic UDP - RTP (video data). Can be set to “Fixed Ports” on Polycom systems.
1024-65535 / Dynamic UDP - RTP (audio data). Can be set to “Fixed Ports” on Polycom systems.
1024-65535 / Dynamic UDP - RTCP (control information). Can be set to “Fixed Ports” on Polycom systems.

The following table shows GMS port usage.

Port / Function
21 / (FTP) Software updates and provisioning for VSX systems and ViewStations
24 / (FTP) FTP Telnet trace log
80 / (HTTP) Pulling VSX system, ViewStation, and VS4000
information
80 / (HTTP) Software updates iPower & Provisioning iPower
3601 / (Proprietary) (Data Traffic) - GAB data
3603 / TCP - Pulling ViaVideo info (since might be non-web server PC)
389 / LDAP and ILS
1002 / ILS

The following table shows other VSX port usage.

Port / Function
21 / (FTP) Software updates and GMS provisioning
23 / (Telnet) For diagnostics
24 / (FTP) API control
  • PolycomAddressBookUtilityPort Usage

The Polycom Address Book Utility communicates with Polycom Video endpoints over:

  • HTTP port 80
  • FTP port 24
  • Port Usage for ReadiManager LX100

Communication between ReadiManager LX100 and Devices

Port / Devices Function / Protocol
21 / Polycom Codecs Management, Provisioning, and SoftUpdate / FTP
23 / Polycom ViewStation MP/512/etc.
Tandberg Codecs Management and Control / Telnet
24 / Polycom ViewStation FX/EX/4000 Management and Control / Telnet
25 / SMTP Server Remote Alerts to SMTP Server / SMTP
80 / Polycom Codecs
WebServers (for status) Monitoring and Management / HTTP
161 / Managed Device / SNMP
162 / SNMP Server Remote Alerts to SNMP Server / SNMP
389 / LDAP Server Replication of Global Address Book / LDAP
1002 / ILS Server Replication of Global Address Book / LDAP
2773 / Polycom iPower
VCON Codecs
NOTE: Uses remote codec application Management and Control / TCP/IP
3601 / Polycom Codecs Global Address Book / Proprietary
3603 / ViaVideo Management and Control / HTTP
5001 / MGC Management and Control / Proprietary
User Selected / Non-Polycom devices/web-servers Monitoring and Management / HTTP

Communication between ReadiManager LX100 and client

Port / Device/App / Function / Protocol
80 / Web browser / General communication / HTTP
2771 / Remote SQL server
Outlook mail server / Data communication / TCP/IP
2773 / ReadiManager LX100 server / Remote Management / TCP/IP
2777 / Outlook mail server / Mail and Calendar communication / TCP/IP

Port Usage for Polycom People+Content IP

Solution

  • Port Usage for Polycom People+Content IP

< INTERNAL SOLUTION ONLY >

Polycom People + Content IP uses a custom protocol to allow sharing of documents in a Video Conference.

The TCP and UDP ports used for showing content are :

  • TCP - 5001
  • UDP - 5001

Interacting with firewalls using fixed ports and Polycom H.323 products

Solution

  • Interacting with firewalls using fixed ports and Polycom H.323 products
    H.323 uses a single fixed TCP port (1720) to start a call using the H.225 protocol (defined by H.323 spec) for call control. Once that protocol is complete, it then uses a dynamic TCP port for the H.245 protocol (also defined by the H.323 spec) for caps and channel control. Finally, it opens up 2 dynamic UDP ports for each type of media that was negotiated for the call (audio, video, far-end camera control). This first port carries the RTP protocol data (defined by the H.225 spec) and the second one carries the RTCP data (defined by the H.225 spec). So, a typical H.323 ViewStation call would use 2 TCP fixed ports (3230-3231) and 6 UDP fixed ports (3230-3235). The PVX uses fixed ports TCP 3230-3237 For a complete listing of Polycom products and H.323 port usage click here. As per TCP/IP standards, ports are divided into 3 sections: 0-1023 (privileged ports), 1024-49151 (registered ports) and 49152-65535 (dynamic ports). H.323 specifies the dynamic ports in the dynamic range are open.Polycom has added a feature to its product line that allows the ports to use fixed ports (instead of dynamic ports) so that it can more easily traverse a firewall. Only the systems behind the firewall need to turn on this feature, since the firewall will prevent the audio/video/FECC from the outside from coming in unless this is enabled. In addition, the user must "punch holes" in the firewall using the previously mentioned exact port numbers and exact protocol types for outgoing calls. To receive incoming calls, the user must also punch a hole using the 1720 TCP port.

What Communication Service Ports are used for Polycom products?

Solution

  • Communication Service Ports used for Polycom products

Communication across the network for Polycom products requires the usage of certain Internet service ports. Global Management System and PathNavigator communicates with the web client, video devices and other services. This document provides information regarding the protocols and ports used for this communication. In the tables below, “Direction” indicates how a particular communication is initiated; for example, “Web browser to Global Management System” means the web browser opens a connection with Global Management System which is then used to interchange information.

From the Web Browser

The web client is a web browser running on a PC station that is used to access Global Management System, Path Navigator, or video devices. The table below shows the rotocol and port used. The ports listed must be open for two-way communication.

Direction / Protocol / Ports / Purpose
Web browser to Global Management System / HTTP: TCP / 80 / Web client communicating with Global Management System
Web browser to video devices except for ViaVideo / HTTP: TCP / 80 / Web client communicating with video devices user interface
Web browser to ViaVideo / HTTP: TCP / 3603 / Web client communicating with ViaVideo web interface
Web browser to Other
Devices web server / HTTP: TCP / Arbitrary port (assigned by admin when adding this device to Global Management System) / Web client communicating with Other Devices web interface
Web browser to
PathNavigator / HTTP: TCP / 80 / Web client communicating with PathNavigator

Global Management System and video devices communications

Different features offered in Global Management System use different ports when communicating with video devices. The port most often used is port 80. However, other protocols such as FTP and Telnet require the usage of ports other than 80.

Global Management System to / from ViewStation model
Direction / Protocol / Ports / Purpose
Global Management System to video devices / HTTP: TCP / 80 / Monitoring and Management
Video devices to Global
Management System / HTTP: TCP / 80 / Monitoring and Management
Global Management System to video devices / FTP: TCP / 21 / Management, Provisioning, SoftUpdate
Video devices to Global Management System / FTP (data): TCP / Dynamic port / Management, Provisioning, SoftUpdate
Global Management System to video devices / Telnet: TCP / 23 / Diagnostic Logging (next release of Global Management System)
Video devices to Global Management System / Proprietary: TCP / 3601 Global Address Book
Global Management System to / from iPower (model)
Direction / Protocol / Ports / Purpose
Global Management System to Video devices / HTTP: TCP / 80 / Monitoring and Management
Video devices to Global
Management System / HTTP: TCP / 80 / Monitoring and Management
Global Management System to / from ViaVideo
Direction / Protocol / Ports / Purpose
Global Management System to Video devices / HTTP: TCP / 3603 / Monitoring and Management
Video devices to Global
Management System / HTTP: TCP / 80 / Monitoring and Management
Global Management System to / from WebCommander, PathNavigator (EP)
Direction / Protocol / Ports / Purpose
Global Management System to endpoint / HTTP: TCP / 80 / Monitoring and Management
Global Management System to /from Other Devices (EP)
Direction / Protocol / Ports / Purpose
Global Management System to endpoint / HTTP: TCP / Arbitrary port (assigned by admin when adding this device to Global Management System) / Monitoring and Management

Global Management System communications with other services

Global Management System uses other services to replicate information to other databases or to perform other tasks such as sending remote alerts to an SNMP server. Non-HTTP protocols are used here and require ports other than 80 to be opened.

Global Management System to / from other Services
Direction / Protocol / Ports / Purpose
Global Management System to ILS / LDAP: TCP / 389 or 1002 / Global Address Replication to ILS server
Global Management System to LDAP / LDAP: TCP / 389 / Global Address Replication to LDAP server
Global Management System to SNMP / SNMP: UDP / 162 / Remote Alerts to an SNMP server
Global Management System to SMTP / SMTP: TCP / 25 / Remote Email Alerts

PathNavigator communications with endpoints

PathNavigator communications with endpoints requires certain ports to be opened. The Registration, Admission and Status (RAS) and Q.931, used for call setup, utilizes certain ports during two-way communication between PathNavigator and the endpoint.

Direction / Protocol / Ports / Purpose
PathNavigator to Endpoint / RAS: UDP / Varies by endpoint / RAS communication from PathNavigator back to the endpoints
PathNavigator to Endpoint / Q.931: TCP / 1720 (usually, may vary) / For setting up calls when PathNavigator is in routed mode
Endpoint to PathNavigator / RAS: UDP / 1719 / For endpoints to communicate with PathNavigator, registration, admission, etc…
Endpoint to PathNavigator / Q.931: TCP / 1720 / For setting up calls when PathNavigator is in routed mode

H.323 ports used by Polycom video conferencing units

Solution

  • H.323 ports used by Polycom video conferencing units

H.323 Ports (IP based video conferencing):

  • 80 - Static TCP - HTTP Interface (optional)
  • 389 - Static TCP - ILS Registration (LDAP)
  • 1503 - Static TCP - T.120
  • 1718 - Static UDP - Gatekeeper discovery (Must be bidirectional)
  • 1719 - Static UDP - Gatekeeper RAS (Must be bidirectional)
  • 1720 - Static TCP - H.323 call setup (Must be bidirectional)
  • 1731 - Static TCP - Audio Call Control (Must be bidirectional)
  • 1024-65535 Dynamic TCP H245
  • 1024-65535 Dynamic UDP - RTP (Video data)
  • 1024-65535 Dynamic UDP - RTP (Audio data)
  • 1024-65535 Dynamic UDP RTCP (Control Information)

These ports above, can be set to "Fixed Ports" on Polycom systems, as opposed to dynamic.

GMS Ports:

  • 21 (FTP) - Software Updates & Provisioning
  • 23 (Telnet/TCP) - Diagnostic Logging>
  • 25 (SMTP:TCP) -Remote email alerts
  • 80 (HTTP) - Pulling ViewStation/VS4000 info
  • 389 (LDAP and ILS)
  • 1002 (ILS)
  • 3601 (Proprietary) (Data Traffic) - GAB data
  • 3603 - TCP - Pulling ViaVideo info (since might be non-web server PC)
  • 8080 - Static TCP - HTTP Server Push (optional)
  • 9090 - Static TCP - HTTP Server Push (optional user configurable on the server for GMS/PCS/Path Nav)

GMS listens for connections on ports 80 and 3601 (GAB) and in the future will listen on port 3604 (ViaVideo) and other potentials later.

VSX, ViewStationsPorts:

  • 21 (FTP) - Software Updates & GMS Provisioning
  • 23 (Telnet) - For Diagnostics & API Control (used by PCS) by MP/512/etc.
  • 24 (Telnet) - For Diagnostics & API Control (used by PCS) by FX/EX/4000 and VSX
  • 3220 to 3225 - TCP Ports ViewStation
  • 3230 to 3247 - UDP Ports ViewStation
  • 3230 to 3235 - TCP Ports VSX
  • 3230 to 3253 - UDP Ports VSX

People+Content IP Ports:

  • 5001 - Static TCP

ViaVideo/PVX Ports:

  • 3604 (GMS Server Discovery)(Used by ViaVideo)(Broadcast)
  • 3230-3237 TCP Signaling and control for audio, call, video and data/FECC

PCS Ports:

Communication between PCS and devices:

  • 23 (Telnet) – Management & Control – Tandberg Codecs.
  • 24 (Telnet) – Management & Control – Polycom ViewStations and VSX.
  • 161(SNMP) – Managed device
  • 2000 (TCP/IP) – Gatekeeper call authorization for outbound communications – Cisco MCM
  • 2773 (TCP/IP) – Management & Control – Polycom iPower, VCON codecs
  • 3603 (HTTP) – Management & Control – Polycom ViaVideo and PVX
  • 4000-4004 (TCP/IP) – Management & Control – Lantronix
  • 5001 (API via TCP/IP) – Management & Control – Polycom MGC
  • 8000 (TCP/IP) – Gatekeeper call authorization for outbound communications – Cisco
    MCM, RADVision ECS

Communication between PCS and client:

  • 80 (HTTP) – General Communication – Web browser.
  • 2771 (TCP/IP) – Data communication – Remote SQL server, Outlook / Notes Mail server
  • 2773 (TCP/IP) – remote – Polycom Conferencing Suite Server
  • 2777 (TCP/IP) – Mail & Calendar communication – Outlook / Notes mail server

Communication between PCS servers:

  • 700 (TCP/IP) – Redundant server communication - PCS
  • 2771 (TCP/IP) – Distributed Server communication - PCS

PathNavigator Ports:

From PathNavigator to endpoint

  • Varies by endpoint - UDP – RAS (Registration, Admission and Status)
  • 1720 – TCP (Q.931) – Setting up calls when PathNavigator is in routed mode

From endpoint to PathNavigator

  • 1791 – UDP – RAS
  • 1720 – TCP (Q.931) - Setting up calls when PathNavigator is in routed mode

WebOffice Ports:

  • 80 / 85 (HTTP / TCP) – WO client communications with WO sever
  • 443 / 85 (HTTP / TCP) – WO client communications with WO sever
  • 5005 (proprietary) – WO Server uses this service to translate commands to MGC (usually
    internal port)
  • 5001 / 1205 (proprietary) – WO server and MGC communication

MGC (Polycom Network Systems) Additional Ports:

  • 5001 - Static TCP - MGC Manager (5003 can be chosen instead within MGC)
  • 21 - Static TCP - FTP (retrieve MGC config. Files etc.)

RADVision Additional:

  • 1820 - Gateway Signaling/Call Setup
  • 2720 - MCU Signaling/Call Setup