Help Center

Port Requirements

Prognosis 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

Upon installation, Prognosis reserves the use of several port numbers. By default, this is the base port 1960 followed by the next six port numbers.

Port

Protocol

Executable

Prognosis Server Connection 

Usage

<PortNumber>+0
Default 1960

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
Default 1961

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
Default 1962

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
Default 1963

N/A

N/A

N/A

Not currently used.

<PortNumber>+4
Default 1964

TCP

IRLSTNR

Inbound

Used by the Tivoli Integration interface.

<PortNumber>+5
Default 1965

N/A

N/A

N/A

Not currently used.

<PortNumber>+6
Default 1966

TCP

IRJVMCOL

Inbound

Listening port for connections from JVM probe (HPE NonStop only).

Changing the Base Port

The default base port used by Prognosis (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 Prognosis use. Prognosis 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 Prognosis 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. This is used in order to remotely connect to Prognosis and request information via IRCLVIEW.

23

TCP

Outbound

Telnet port used by a number of Prognosis for Unified Communications 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

Default IIS port between the Prognosis 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 Prognosis Usage Analytics, if enabled.

514

UDP

Inbound and Outbound

Syslog - Used for sending receiving system logging messages.

636

TCP

Outbound

LDAP secure access.

1970

TCP

Inbound

Default port for the Prognosis 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, Prognosis uses the encrypted channel. 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 Prognosis for 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 Unified Communications

The following vendor specific ports are also used in addition to the set of Prognosis base ports and any required Common ports.

AudioCodes SBC

Port

Protocol

Monitoring Server Connection 

Usage

161

UDP

Outbound

SNMP queries from the Monitoring Server.

514UDPInboundDefault 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 Communication Manager

Port

Protocol

Prognosis 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 Prognosis.

Defaults:
50000 for AVAYA_PBX,
50001 for AVAYA_LEGACY
50002 for AVAYA_DEFINITY.

For details of using a non-default port, see the Non-default CDR Port.

135 and
49152 - 65535

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 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 Communication Server 1000

Port

Protocol

Prognosis Server Connection 

Usage

22

TCP

Outbound

Common SSH port to access the CLI interface for the PBX.

23

TCP

Outbound

Common Telnet port to access the CLI interface for the PBX.

161

UDP

Outbound

SNMP queries to the Call Server and Signalling Server for server statistics.

162

UDP

Inbound

Standard port to receive SNMP Traps from the Signalling Server.

Avaya IP Office

Port

Protocol

Prognosis Server Connection 

Usage

161

UDP

Outbound

SNMP queries from the Prognosis Monitoring Server.

5005

UDP

Inbound

Port for receiving RTCP packets from Avaya SIP end points.

Avaya Modular Messaging

Port

Protocol

Prognosis Server Connection 

Usage

161

UDP

Outbound

Message Storage Server (MSS)

SNMP queries from the Monitoring Server.

135 and
49152 - 65535

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.

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
49152 - 65535

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
49152 - 65535

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
49152 - 65535

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 Presence

Port

Protocol

Monitoring Server Connection 

Usage

22TCPOutboundCLI 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 Unity Connection

Port

Protocol

Monitoring Server Connection 

Usage

22

TCP

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 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

Prognosis Server Connection 

Usage

161

UDP

Outbound

SNMP queries from the Prognosis Monitoring server to the Cisco device to obtain system metrics.

162UDPInboundSNMP notifications from the Cisco device to the Prognosis Monitoring server for alerting error conditions.

22

TCP

Outbound

SSH Command Line Interface (CLI) requests from the Prognosis Monitoring server to the Cisco device.

Microsoft Skype for Business

Port

Protocol

Monitoring Server Connection 

Usage

389

TCP

Outbound

LDAP Non-secure access.

636

TCP

Outbound

LDAP secure access.

3268TCPOutboundLDAP Non-Secure access to Active Directory Domain Controller with Global Catalog role. Recommended instead of the standard LDAP/LDAPS ports 389 / 636
3269TCPOutboundLDAP 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
49152 - 65535

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
49152 - 65535

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.

(*)  Effective with version 11.4, Skype for Business monitoring will no longer use the unencrypted port 5672 for RabbitMQ communication and will instead use the encrypted port 5671. For upgrade scenarios when 11.4 manages 11.1/11.2/11.3, port 5672 will continue to be used for backward compatible communication between servers. However, after all the servers have been upgraded to version 11.4, it is recommended to run the Post Upgrade Procedure for Skype for Business which will close off port 5672. Therefore, port 5672 can only be used and will only be supported in upgrade scenarios prior to running the post-upgrade script.

Microsoft Teams

Port

Protocol

Connection to Prognosis server

Usage

443TCPOutbound

To connect to Prognosis Cloud to retrieve Microsoft Teams data. The IR Cloud uses CDN IP Address ranges, if specific whitelist of IP Address is required for Data Center installations, then the following IP Address ranges should be listed.


120.52.22.96/27
205.251.249.0/24
180.163.57.128/26
204.246.168.0/22
205.251.252.0/23
54.192.0.0/16
204.246.173.0/24
120.253.240.192/26
116.129.226.128/26
99.86.0.0/16
205.251.200.0/21
223.71.71.128/25
13.32.0.0/15
120.253.245.128/26
13.224.0.0/14
70.132.0.0/18
210.51.40.0/24
13.249.0.0/16
205.251.208.0/20
58.254.138.0/25
116.129.226.0/25
52.222.128.0/17
64.252.128.0/18
205.251.254.0/24
71.152.0.0/17
216.137.32.0/19
204.246.172.0/24
120.52.39.128/27
118.193.97.64/26
223.71.71.96/27
130.176.0.0/16
54.240.128.0/18
205.251.250.0/23
180.163.57.0/25
52.46.0.0/18
223.71.11.0/27
52.82.128.0/19
54.239.128.0/18
36.103.232.128/26
52.84.0.0/15
111.51.66.0/24
143.204.0.0/16
144.220.0.0/16
120.52.153.192/26
119.147.182.0/25
120.232.236.0/25
54.182.0.0/16
58.254.138.128/26
120.253.245.192/27
54.239.192.0/19
120.52.12.64/26
99.84.0.0/16
54.230.0.0/16
52.124.128.0/17
204.246.164.0/22
13.35.0.0/16
204.246.174.0/23
36.103.232.0/25
119.147.182.128/26
118.193.97.128/25
120.232.236.128/26
204.246.176.0/20
120.253.241.160/27
13.124.199.0/24
35.167.191.128/26
18.200.212.0/23
99.79.169.0/24
52.15.127.128/26
34.223.12.224/27
54.233.255.128/26
13.54.63.128/26
13.59.250.0/26
3.234.232.224/27
52.66.194.128/26
13.228.69.0/24
64.252.64.0/18
18.216.170.128/25
3.231.2.0/25
52.220.191.0/26
34.232.163.208/29
35.162.63.192/26
34.223.80.192/26
34.226.14.0/24
13.113.203.0/24
34.195.252.0/24
52.52.191.128/26
52.56.127.0/25
34.216.51.0/25
52.199.127.192/26
52.212.248.0/26
13.210.67.128/26
35.158.136.0/24
52.57.254.0/24
52.78.247.128/26
52.47.139.0/24

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.

Ports for Contact Center

The following vendor specific ports are also used in addition to the set of Prognosis base ports and any required Common ports.

Avaya Application Enablement Services

Port

Protocol

Prognosis Server Connection 

Usage

161

UDP

Outbound

SNMP queries from the Monitoring Server.

Avaya Aura Contact Center

Port

Protocol

Prognosis 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

Prognosis 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.

Cisco Unified Contact Center Enterprise

Port

Protocol

Prognosis Server Connection 

Usage

161

UDP

Outbound

SNMP queries from the Monitoring Server

162UDPInboundSNMP Traps sent to Prognosis Monitoring server

7890

TCP

Outbound

REST Diagnostic API.

514UDPInboundStandard 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.

514UDPInboundStandard Syslog port.

Cisco Voice Portal (CVP) and Cisco Voice XML Gateways

Port

Protocol

Prognosis Server Connection 

Usage

161

UDP

Outbound

SNMP queries from the Monitoring Server to the Cisco Voice Portal and Cisco Voice XML Gateways.

Ports for Call Recording Assurance

The following vendor specific ports are also used in addition to the set of Prognosis base ports and any required Common ports.

Verint Enterprise Infrastructure Monitoring

Port

Protocol

Prognosis Server Connection 

Usage

135 and 49152 - 65535

TCP


Standard WMI ports on all Verint servers

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

162

UDP


SNMP Trap port for all Verint alarming.

1433

TCP


MSSQL infrastructure monitoring for the Verint database server roles.

Verint Call Recording Assurance

Port

Protocol

Prognosis Server Connection 

Usage

443

TCP


Default HTTPS Verint DAS API port on the Verint Application server.

Ports for Media Integrity

Verint

Port

Protocol

Prognosis Server Connection 

Usage

80

TCP


Default HTTP Verint DAS API port on the Verint Application Server.

7001TCP
Default HTTP authentication port on the Verint Application Server

29500 (HTTP)

29501 (HTTPS)

TCP


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)

Port

Protocol

Prognosis Server Connection 

Usage

62201 - 62220

TCP


Default HTTPS port on BSF Server.

Media Integrity

Port

Protocol

Prognosis Server Connection 

Usage

5671

TCP


Default HTTPS port on Media Integrity Server for RabbitMQ TLS Communication.

5671

TCP


Default HTTPS port on Prognosis CRA server for communicating with IR Media Integrity Server via RabbitMQ TLS Communication.

15672

TCP


RabbitMQ management port on IR Media Integrity Server.

25672

TCP


Default port for Erlang distribution on IR Media Integrity Server

Provide feedback on this article