Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM Documentation > Previous Versions > VoIP and Network Quality Manager 4.2.4 system requirements

VoIP and Network Quality Manager 4.2.4 system requirements

Created by Rodim Suarez_ret, last modified by Caroline Juszczak on Aug 18, 2016

Views: 1,543 Votes: 0 Revisions: 4

UPDATED August 18, 2016


The following requirements are based on a minimum installation of SolarWinds VoIP and Network Quality Manager with SQL Server on a separate database server. To optimize database scalability, SolarWinds recommends that you maintain your SQL Server installation on its own server. If you must host your SQL server on the same server, SolarWinds recommends a quad-processor, 2.67 GHz, 64-bit CPU and at least 16 GB of RAM.

SolarWinds VoIP and Network Quality Manager requirements

Environment SolarWinds VoIP and Network Quality Manager supports IP SLA for Cisco IP SLA capable devices. It is possible to monitor Cisco CallManager, CallManager Express, and Avaya Communication and Media Server devices with SolarWinds VoIP and Network Quality Manager.
CPU Dual processor, 3GHz
Hard drive space 20 GB
Operating system

Windows Server 2008 R2 SP1

Windows Server 2012, 2012 R2

.NET Framework

Version 4.5

Compatible with 4.6.1

Web browser

Internet Explorer 11

Microsoft Edge

Mozilla Firefox - two most recent versions

Google Chrome - two most recent versions

SQL Server requirements


Dual processor, 3 GHz

Quad-processor, 2.67 GHz, 64-bit (for large networks)


8 GB

16 GB (for large networks)

Hard drive space 20 GB

SQL Server 2008, 2008 SP1, 2008 SP2, 2008 SP3, or 2008 SP4

SQL Server 2008 R2, 2008 R2 SP1, 2008 R2 SP2, or 2008 R2 SP3

SQL Server 2012, 2012 SP1, 2012 SP2, or 2012 SP3 (also with AlwaysOn Availability Groups)

SQL Server 2014 (also with AlwaysOn Availability Groups) or 2014 SP1

SQL Server 2016 RC

  • 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 quadprocessor CPU and 16 GB of RAM. We do not support more than six million calls per month.
  • If you are installing SolarWinds VoIP and Network Quality Manager with SolarWinds NPM, see NPM Requirements.

Server port requirements

The following table provides a list of all of the ports needed for communication with SolarWinds VNQM.

21 TCP FTP (CDR/CMR download)
22 TCP

SFTP (CDR/CMR download)

SSH for CLI (operation polling)

23 TCP TELNET for CLI (operation polling)
80 TCP

HTTP port

Default port used by additional web servers. If you change this setting, you must include the port in the URL used to access the web console.

161 UDP Default UDP port of NPM, used by SNMP
443 TCP Used for conducting secure SSL communications.
17777 TCP Must be opened for Orion module traffic.


Last modified