Port Requirements
The Prognosis Server requires the use of a number of Ports on each machine. This section details each of the 'Base' ports that are required and also any other ports that might be required in specific circumstances.
Base Ports
During installation, the installer reserves the use of several port numbers. By default, this is the base port 1960 followed by the next six contiguous port numbers.
Port | Protocol | Executable | Prognosis Server Connection | Usage |
<PortNumber>+0 | TCP | IRNETRTR | Inbound | Default base port. This port is used for; router-to-router, local process to router and Windows Client to router communications where TCP/IP is used. All requests and data messages are sent via this port across servers as well as to individual collectors that gather raw data. It is also the port that the Windows Client connects to. On HPE NonStop, IPC is used for internal messaging and messaging to other HPE NonStop servers. Therefore, on HPE NonStop, this port is only used for Windows Client connections and cross-platform (Windows/UNIX) connections. |
<PortNumber>+1 | TCP | IRPROMGR | N/A (Local only) | Used for connections from child processes back to Process Manager in order to detect process failures and to instigate process restarts. It is used for local communications only. On HPE NonStop this function is performed via IPC, so this port is not used. |
<PortNumber>+2 | UDP | IRNETRTR | Inbound and Outbound | Used to send and receive Auto-Discovery multicasts (UDP protocol) in order to discover other Prognosis Servers. This port is not used if Auto-Discovery is disabled (e.g. if Managing-Nodes are used). Auto-Discovery between HPE NonStop nodes is done via IPC, but this port is still used on HPE NonStop for Auto-Discovery of cross-platform systems. |
<PortNumber>+3 | N/A | N/A | N/A | Not currently used. |
<PortNumber>+4 | TCP | IRLSTNR | Inbound | Used by the Tivoli Integration interface. |
<PortNumber>+5 | N/A | N/A | N/A | Not currently used. |
<PortNumber>+6 | TCP | IRJVMCOL | Inbound | Listening port for connections from the JVM probe (HPE NonStop only). |
Changing the Base Port
The default base port used (i.e. 1960) can be changed after installation by amending the port number in the TCPIP-PORT statement of the NETWORK Configuration; this will also automatically reserve the next six ports for use. The software will need to be restarted after amending the NETWORK Configuration for the change to take effect.
Common Ports
The following 'Common' ports are applicable for data collection and should be enabled where the specified service is to be used, e.g. LDAP authentication.
Port | Protocol | Prognosis Server Connection | Usage |
22 | TCP | Outbound | SSH port used for integration with the EMC Smarts VoIP Availability Manager product. |
23 | TCP | Outbound | Telnet port used by a number of Collaborate collectors. |
25 | TCP | Outbound | Port for Dispatch Manager email alerts via SMTP. |
389 | TCP | Outbound | LDAP Non-secure access. Only required if LDAP is to be used instead of Active Directory. |
443 | TCP | Inbound and Outbound | Default IIS port between the Web Application and the IIS Web Server. If not available, the installer will check the availability of port 8080, if this is not available it will continue to search incrementing the port number by 1 each time up to port 8089. This port will also be used by Usage Analytics, if enabled. This port is also used in Collaborate solutions that require Web access using HTTPS protocol. |
514 | UDP | Inbound and Outbound | Syslog - Used for sending receiving system logging messages. |
636 | TCP | Outbound | LDAP secure access. |
1970 | TCP | Inbound | The default port for High Availability. |
5432 | TCP | Inbound | Port for PostgreSQL communication. |
5671 | TCP | Inbound and Outbound | Encrypted (TLS) channel for AMQP which is used by Alerts CI mapping and Skype for Business monitoring. Typically, this is set on Monitoring Servers as the outbound port for supplying alerts as AMQP data. It is also used as the Inbound and outbound port for Management Servers. |
5672 | TCP | Outbound | Unencrypted channel for AMQP which is used by Alerts CI mapping. Typically, this is set on Monitoring Servers as the outbound port for supplying alerts as AMQP data. By default, the Encrypted (TLS) channel is used. However, it may be configured to use either the unencrypted or encrypted channel, therefore this setting is only required if the unencrypted channel is chosen. This port is only used by Skype for Business monitoring in upgrade deployment scenarios (multiple Prognosis versions). |
6514 | TCP | Inbound and Outbound | TLS Syslog - Used for sending and receiving TLS system logging messages. |
6767 | TCP | Inbound | Default port between the IIS Web Server and the Prognosis Server. |
Ports for Collaborate
The following vendor specific ports are also used in addition to the set of base ports and any required Common ports.
AudioCodes SBC
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server. |
| 514 | UDP | Inbound | Default Syslog port for receiving messages. |
1813 | UDP | Inbound | RADIUS listener port. This is the default port for RADIUS Accounting information to be received. For more information, see RADIUS Accounting Setup for AudioCodes SBC. |
5060 | UDP | Inbound | Port for receiving RTCP data from the SIP Interface Table. |
Avaya Aura Application Enablement Services
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server. |
Avaya Aura Communication Manager
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server. |
5005 | UDP | Inbound | Port for receiving RTCP packets from Avaya SIP end points. |
5022 | TCP | Outbound | Common SSH port for the Avaya PBX to issue SAT commands. |
5023 | TCP | Outbound | Common Telnet port for the Avaya PBX to issue SAT commands. Only needed for Avaya PBX if SSH is not supported. |
50000-50002 | TCP | Inbound | Configurable ports for Avaya PBX to push CDR data to the Monitoring Server. Defaults: For details of using a non-default port, see the Non-default CDR Port. |
135 and | TCP | Outbound | WMI - Dynamic port range used for soft phone host metrics. For easier firewall traversal this can be configured to use a fixed port with Windows Server 2008 and higher, for details see: http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v=vs.85).aspx |
Avaya Aura Contact Center
Port | Protocol | Monitoring Server Connection | Usage |
162 | UDP | Inbound | Standard port to receive SNMP Traps. |
135 and dynamic 1024 - 65535 | TCP | DCE/RPC protocol used to collect Real Time Data (RTD) from the AACC servers. Note some firewalls support inspection of DCE/RPC protocol, MS Windows should already allow outbound traffic using default Windows firewall rules. | |
135 and 49152 - 65535 | TCP | Server statistics from the AACC WMI – Dynamic port range used for server host metrics. This can be configured to use a fixed port with Windows Server 2008, and higher, for easier firewall traversal, for details see: http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v=vs.85).aspx | |
1972 | TCP | SQL queries from the AACC database. |
Avaya Experience Portal
Port | Protocol | Monitoring Server Connection | Usage |
80 or 443 | TCP | Avaya Experience Portal Manager (EPM) HTTPS port for web service traffic. | |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to the EPM. |
162 | UDP | Inbound | Standard port to receive SNMP Traps. |
Avaya Aura System and Session Manager
Port | Protocol | Monitoring Server Connection | Usage |
22 | TCP | Outbound | Open for SFTP connections to the Session Manager for CDRs. |
161 | UDP | Outbound | SNMP queries from the Monitoring Server. |
5005 | UDP | Inbound | Port for receiving RTCP packets from Avaya SIP end points. |
Avaya IP Office
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server. |
5005 | UDP | Inbound | Port for receiving RTCP packets from Avaya SIP end points. |
Avaya Modular Messaging
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | Message Storage Server (MSS) SNMP queries from the Monitoring Server. |
135 and | TCP | Outbound | Message Application Server (MAS) WMI - Dynamic port range used for server host metrics. For easier firewall traversal this can be configured to use a fixed port with Windows Server 2008 and higher, for details see: http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v=vs.85).aspx |
Avaya Session Border Controller for Enterprise
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to Avaya SBC-E device. |
Call Recording Assurance
Vendor | Port | Protocol | Connection to Prognosis Server | Usage |
Common | 4000 | TCP | Internal | Internal communication port used to send data from the CRA service to Prognosis Server. |
Common | 5432 | TCP | Inbound | Port for PostgreSQL communication with the SOT. |
Common | 135 and | TCP | Outbound | WMI - Dynamic port range used for file system metadata retrieval. For easier firewall traversal, this can be configured to use a fixed port with Windows Server 2008 and higher, for details see: http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v=vs.85).aspx |
Verint | 1433 | TCP | Outbound | MSSQL infrastructure monitoring for the Verint database server roles and retrieving recording and configuration metadata from the central data warehouse. |
| Verint | 162 | UDP | Inbound | SNMP Trap port for all Verint alarming. |
NICE NIM/Engage | 1433 | TCP | Outbound | MSSQL infrastructure monitoring for the NICE database server roles and retrieving recording and configuration metadata from the central data warehouse. |
NICE NIM/Engage | 161 | UDP | Outbound | SNMP queries from the CRA Server for infrastructure monitoring. |
NICE NTR | 3306 | TCP | Outbound | MySQL - retrieval of recording and configuration metadata from the central data warehouse. |
NICE NTR | 161 | UDP | Outbound | SNMP queries from the CRA Server for infrastructure monitoring. |
Media Integrity Port Requirements
Media Integrity requires ports to be opened to download recordings and to communicate with the CRA servers.
Vendor | Port | Protocol | Connection to Prognosis Server | Usage |
Verint | 80 | TCP | Outbound | Default HTTP Verint DAS API port on the Verint Application Server. |
| Verint | 443 | TCP | Outbound | Default HTTPS Verint DAS API port on the Verint Application Server. |
| Verint | 7001 | TVP | Default HTTP authentication port on the Verint Application Server. | |
Verint | 29500 (HTTP) 29501 (HTTPS) | TCP | External (Verint system) | Default HTTP/HTTPS port on which to listen for web requests on the Verint Content servers. |
NICE (Where the BSF service is used to download recordings) | 62201 - 62220 | TCP | Outbound | Default HTTPS port on BSF Server |
Media Integrity Servers | 5671 | TCP | Inbound/Outbound | Default HTTPS port on Media Integrity Server for RabbitMQ TLS Communication. |
Media Integrity Servers | 5671 | TCP | Inbound/Outbound | Default HTTPS port on CRA Server for communicating with Media Integrity Server via RabbitMQ TLS Communication. |
Media Integrity Servers | 15672 | TCP | Internal | RabbitMQ management port on Media Integrity Server. |
Media Integrity Servers | 25672 | TCP | Internal | The default port for Erlang distribution on Media Integrity Server |
Cisco Emergency Responder
Port | Protocol | Monitoring Server Connection | Usage |
22 | TCP | Outbound | SSH port set up to collect data. CLI port to collect certificate information. |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to Cisco Emergency Responder. |
Cisco Expressway
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to the Cisco device to obtain system metrics. |
443 | TCP | Outbound | HTTPS requests from the Monitoring Server to the Cisco device. |
Cisco Meeting Server
Port | Protocol | Connection to Monitoring Server | Usage |
22 | TCP | Outbound | Port is used to connect to the SSH terminal in order for the Command Line Interface to retrieve CMS certificate information. |
445 | TCP | Outbound | Port used by the Monitoring Server to send web requests to the CMS Web Admin interface. |
6000 | TCP | Inbound | Port used to listen for incoming CDRs from the Cisco Meeting Server. |
Cisco TelePresence Management Suite
Port | Protocol | Monitoring Server Connection | Usage |
443 | TCP | Outbound | Port used by the Monitoring Server to send web requests to the TMS Administration console. |
135 and | TCP | Outbound | WMI – Dynamic port range used for server & soft phone host metrics. For easier firewall traversal, this can be configured to use a fixed port with Windows Server 2008 and higher, for details see: http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v=vs.85).aspx |
135, 445 and | TCP | Outbound | Remote Event Log - Dynamic port range used for remote event log management. For easier firewall traversal, this can be configured to use a fixed port with Windows Server 2008 and higher, for details see: http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v=vs.85).aspx |
Cisco Unified Communications Manager
Port | Protocol | Monitoring Server Connection | Usage |
22 | TCP | Inbound and Outbound | SSH port for SFTP to collect Call Detail Records (CDR) and Call Detail Diagnostic Records (CMR) from CUCM clusters. CLI port to collect certificate information. |
80 | TCP | Outbound | Used for polling Cisco IP phones for QOS and device data via HTTP and/or XML. |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to Cisco CUCM Clusters, H.323 Gateways, SCCP Gateways and TelePresence 500, 1000 and 3000 series devices. |
443 or 8443 | TCP | Outbound | The standard port on Cisco Clusters for 3rd party applications, to retrieve data via SOAP AXL and SOAP Perfmon. The standard port on Cisco TelePresence Endpoints to retrieve call statistics. |
135 and | TCP | Outbound | WMI - Dynamic port range used for soft phone host metrics. For easier firewall traversal this can be configured to use a fixed port with Windows Server 2008 and higher, for details see: http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v=vs.85).aspx |
Cisco Unified Computing System
Cisco UCS B-Series
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to Cisco UCS B-Series. SNMP interface for UCS Manager. |
Cisco UCS C-Series
Port | Protocol | Monitoring Server Connection | Usage |
22 | TCP | Outbound | SSH port set up to collect data. |
Cisco Unified Contact Center Enterprise
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server |
7890 | TCP | Outbound | REST Diagnostic API. |
| 514 | UDP | Inbound | Standard Syslog port |
Cisco Unified Contact Center Express
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to Cisco UCCX. |
443 or 8443 | TCP | Outbound | The standard port on Cisco Clusters for 3rd party applications to retrieve data via SOAP Perfmon. |
| 514 | UDP | Inbound | Standard Syslog port. |
Cisco Unified Presence
Port | Protocol | Monitoring Server Connection | Usage |
| 22 | TCP | Outbound | CLI port to collect certificate information. |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to Cisco Unified Presence devices. |
443 or 8443 | TCP | Inbound | The standard port on Cisco Clusters for 3rd party applications, to retrieve data via SOAP Perfmon. |
Cisco Unified Border Element
Port | Protocol | Monitoring Server Connection | Usage |
22 | TCP | Outbound | SSH port set up to collect data. |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to Cisco Unified Border Element devices. |
1812 or 1645 and 1813 or 1646 | UDP | Inbound | RADIUS Authorization and Accounting ports. The specific ports required will depend on how RADIUS is configured in the environment. |
Cisco Unified SIP Proxy
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to the Cisco device to obtain system metrics. |
| 162 | UDP | Inbound | SNMP notifications from the Cisco device to the Monitoring Server for alerting error conditions. |
22 | TCP | Outbound | SSH Command Line Interface (CLI) requests from the Monitoring Server to the Cisco device. |
Cisco Unity Connection
Port | Protocol | Monitoring Server Connection | Usage |
22 | TCP | Inbound/ Outbound | SSH port for SFTP to collect data. CLI port to collect certificate information. |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to the Cisco Unity Connection devices. |
443 or 8443 | TCP | Outbound | Standard port on Cisco Clusters for 3rd party applications, to retrieve data via SOAP Perfmon. |
Cisco Voice Portal (CVP) and Cisco Voice XML Gateways
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to the Cisco Voice Portal and Cisco Voice XML Gateways. |
Microsoft Skype for Business
Port | Protocol | Monitoring Server Connection | Usage |
389 | TCP | Outbound | LDAP Non-secure access. |
636 | TCP | Outbound | LDAP secure access. |
| 3268 | TCP | Outbound | LDAP Non-Secure access to Active Directory Domain Controller with Global Catalog role. Recommended instead of the standard LDAP/LDAPS ports 389 / 636 |
| 3269 | TCP | Outbound | LDAP Secure access to Active Directory Domain Controller with Global Catalog role. Recommended instead of the standard LDAP/LDAPS ports 389 / 636 |
1433 | TCP | Outbound | SQL - Default port used by SQL monitoring. |
135 and | TCP | Outbound | WMI – Dynamic port range used for server and soft phone host metrics. For easier firewall traversal this can be configured to use a fixed port with Windows Server 2008 and higher, for details see: http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v=vs.85).aspx |
135 and | TCP | Outbound | Remote Event Log - Dynamic port range used for remote event log management. For easier firewall traversal this can be configured to use a fixed port with Windows Server 2008 and higher, for details see: http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v=vs.85).aspx |
3000 | TCP | Inbound | SDN- Port used by the Skype SDN API to send real-time inflight voice quality (for Office 2016 client or later) information. For HTTP this will default to port 3000 inbound, but it can use a configurable port depending on what is set in the Skype SDN API. |
5671 (*) | TCP | Inbound and Outbound | Port number used for inbound and outbound communications with the RabbitMQ™ messaging tool. Skype for Business monitoring only uses the encrypted port number 5671. This port will only need to be opened in environments where more than one Prognosis Server has been deployed (e.g. Management & Monitoring Server scenario). |
5985 or 5986 | TCP | Inbound | Used instead of WMI in NATed Skype environments to collect MS Windows and Skype for Business performance metrics. By default ports 5985 and 5986 are used for HTTP and HTTPS respectively. |
Microsoft Teams
Port | Protocol | Connection to Monitoring Server | Usage | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 443 | TCP | Outbound | To connect to Prognosis Cloud to retrieve Microsoft Teams data. The Prognosis Cloud uses CDN IP Address ranges, if a specific whitelist of IP Address is required for Data Center installations, then the following IP Address ranges should be listed.
|
Oracle SBC
Port | Protocol | Monitoring Server Connection | Usage |
22 | TCP | Inbound | Open for SFTP connections for CDRs pushed from the Oracle SBCs. |
161 | UDP | Outbound | SNMP queries from the Monitoring Server to the SBCs. |
Ribbon SBC
Port | Protocol | Monitoring Server Connection | Usage |
161 | UDP | Outbound | SNMP queries from the Monitoring Server. |
1813 | UDP | Inbound | Ribbon RADIUS listener port. This is the port that Ribbon uses when pushing RADIUS accounting information. |