Documentation forVoIP & Network Quality Manager

VNQM 2026.4 system requirements

Release date: October 20, 2026

SolarWinds strongly recommends that you install the SolarWinds Platform on a server that is neither public, nor internet-facing. To learn about best practices for configuring your SolarWinds Platform installation securely, see Secure Configuration for the SolarWinds Platform.

VNQM supports IP SLA for Cisco IP SLA-capable devices. With VNQM, you can monitor:

  • Cisco CallManager devices
  • Cisco CallManager Express devices
  • Avaya Communication and Media Server devices
  • Juniper RPM devices.

Important: These system requirements define the minimum requirements for VoIP and Network Quality Manager 2026.4 as a single product installed on SolarWinds Platform 2026.4. Requirements may increase for medium or large environments, or environments with multi-modules installed.

See the following sections:

Common SolarWinds Platform requirements

VNQM 2026.4 runs on the SolarWinds Platform and has the same base requirements as SolarWinds Platform 2026.4. See the 2026.4 system requirements for details.

For additional information about requirements and configurations, see the Multi-module system guidelines. You should also review your product administration guides and release notes for the exact product requirements beyond these minimums.

Additional SQL Server requirements

If you anticipate six million standard, device to device calls per month with a peak hour of 20,000 calls, we recommend using a dedicated SQL server with a 64-bit, 2.67 GHz quad-processor CPU and 16 GB of RAM. We do not support more than six million calls per month.

If you are installing VNQM with NPM, see SolarWinds Platform Requirements.

Port requirements

SolarWinds does not recommend the use of HTTP (Port 80). Please use HTTPS (Port 443) to ensure that any web-related connections are secure.

Port

Protocol Service/Process Direction Description
21 TCP SolarWinds Collector Service Bidirectional The port used for FTP (CDR/CMR download).
22 TCP SolarWinds Collector Service Bidirectional

The port used for SFTP (CDR/CMR download) and for SSH for CLI (operation polling).

23

TCP SolarWinds Collector Service Bidirectional The port used for TELNET for CLI (operation polling).

80

TCP World Wide Web Publishing Service Bidirectional HTTP port. The port used by Additional Web Servers. If you change this setting, you must include the port in the URL used to access the SolarWinds Platform Web Console.
161 UDP SolarWinds Collector Service Outbound The default UDP port of NPM, used by SNMP.
443 TCP World Wide Web Publishing Service Bidirectional The port used for conducting secure SSL communications.
5005 UDP SolarWinds Collector Service Bidirectional

The port used for RTCP data (call metrics) listening from Avaya Call Manager.

5022 TCP SolarWinds Collector Service Bidirectional The port used for communication with Avaya Call Manager via CLI through SSH.
8443 HTTPS SolarWinds Orion Module Engine/Business Layer Plugin Outbound The port used for Cisco Call Manager AXL credentials troubleshooting.
17777 TCP SolarWinds Information Service Bidirectional

The port used for communication from your polling engine to the SolarWinds Platform Web Console, and from the SolarWinds Platform Web Console to your polling engine.

50000 TCP SolarWinds Collector Service Bidirectional The port used for CDR data (call records) listening from Avaya Call Manager.