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.0.1 Release Notes

VoIP and Network Quality Manager 4.0.1 Release Notes

Created by Beatrix.Turan, last modified by MindTouch on Jun 23, 2016

Views: 622 Votes: 0 Revisions: 6

Updated 01/07/2013

These release notes provide additional guidance for VoIP and Network Quality Manager v4.0.1.

Formerly known as "VoIP Monitor" and "IP SLA Manager," VoIP and Network Quality Manager maintains the functionality of previous versions and adds the ability to monitor realtime VoIP calls. VoIP and Network Quality Manager offers extensive monitoring capabilities, presenting detailed realtime and historical statistics, for devices on your Network.

VoIP Monitor and IP SLA Manger version 3.5 and earlier have entered the End-Of-Life (EOL) cycle. View the SolarWinds EOL Policy online.

Note: If you are installing VoIP and Network Quality Manager with SolarWinds NPM, you must install NPM version 10.4 or later.


New Features and Improvements


VoIP and Network Quality Manager v4.0.1 includes the following new features and improvements:

  • Expanded Microsoft Support

    Windows Server 2012, Windows 8, and SQL Server 2012 are now supported.

  • Orion Core 2012.2 Support

    Added support for the latest version of Orion.

  • Internet Explorer 10

    Added supported for Internet Explorer 10.

Fixed Issues

Issue Case Number
Upgrades fail due to NULL key -
Occasionally receive an unexpected website error when viewing Managed Nodes -
Node Detail resource missing -
VoIP Operation Availability view shows empty data in the operation availability charts 379839
A unique phone is included in the license count multiple times based on unregistered, redundant listings in multiple call managers 373103
Reports do not filter correctly based on device limitations 400369
IP SLA events are displayed in UTC instead of the system time 397725
When customizing the IP SLA Operation Details page, clicking the Preview button results in an error. -

Open Issues

The "Calls by 24 Hours" report may need to be viewed in Report Writer if the report takes longer to export than the page refresh rate. This frequently happens when you have a large amount of call data to export.
Some default headers in Report Writer for do not display correctly. You must manually modify the column headers.
Cisco Call Manager version 4.1 is not fully supported at this time.
VoIP and Network Quality Manager will continue to poll and display IP SLA operation data after unmanaging associated nodes.
The VoIP Call Path resource indicates invalid latency thresholds when highlighting values in red. This resource does not use the latency thresholds configured when editing individual IP SLA Operations as it should. Instead, the resource uses an old global threshold setting that is no longer used by VoIP and Network Quality Manager.
You cannot add the Operation Availability resource when editing the Custom Object resource.
Old IP SLA jobs are not deleted after configuring to the new database format and sometimes after upgrading from 3.5 to 3.5.1
There is not a way to change the operation number of an existing manual operation created by the user.
When the number of open telnet connections are limited on a router, results may take longer than expected to appear.
Operations running on devices using a time zone code set to something other than UTC will show an incorrect time offset. The time zone will be considered to be UTC+0. Consider the following work-arounds:
  • Change the time zone code on the device to UTC format.
  • Modify the ipsla.timezones.xml file located in the C:\Program Files\SolarWinds\Orion\VoIP Monitor folder and add a new time zone using the example provided with an offset in minutes. Restart the Orion Module Engine and Job Engine.
CLI operations without read/write SNMP credentials cannot be deleted. To work around this issue, specify the read/write community string for the operations you want to delete before deleting them.
Hops are not displayed for ICMP Path Echo operations when the operations have been manually created with an invalid configuration. In this situation, the operation status is still displayed as Up, but will only report the entire round trip time instead of each individual hop.
Using > characters in graph names causes rendering failures. To work around this issue, do not use the > character in your graph names.
VoIP and Network Quality Manager only reports what the network devices are reporting. In some cases, path operations will not show all hops in a path or show one hop more than once because the device is reporting these hops inaccurately.
URLs that have uppercase letters for "ftp" and "http" are not processed properly. When creating or editing IP SLA operations, type URLs using lowercase letters for ftp and http. For example, instead of HTTP://
Reports that include details from two identical operations will only list one instance the operation.
If the SolarWinds Information service is stopped, IP SLA web resources may display SQL errors.
Additional pollers may indicate a "down" status when the poller is actually up and running on the Collector Services resource.
When editing IP SLA Node properties, clicking Use Default does not set the source IP address to the IP address assigned to the Orion node.
The Operation Availability resource does not have an Edit button to allow users to configure the resource and specify a date range.
Administrative functions may be limited if your VoIP and Network Quality Manager server and your Orion NPM server are not in the same domain. SolarWinds recommends that you install VoIP and Network Quality Manager on the same server as Orion NPM.
An SQL exception may occur when you try to open VoIP and Network Quality Manager on an additional Orion Web Console if the Orion server hosting the shared database does not also have VoIP and Network Quality Manager installed. SolarWinds recommends that you not install VoIP and Network Quality Manager on an additional Orion Web Console unless the original Orion server is also hosting VoIP and Network Quality Manager.

Migrating Reports to Another VoIP and Network Quality Manager Installation

Custom reports that you have created for a standard installation of VoIP and Network Quality Manager are easily migrated to a second installation, typically an Additional Poller. The following procedure copies existing reports from one VoIP and Network Quality Manager installation to another.

To migrate VoIP and Network Quality Manager reports from one installation to another:

  1. Open the Orion Reports folder, located in Program Files\SolarWinds\Orion\ on your original VoIP and Network Quality Manager server.
  2. Select the reports you want to copy to your second VoIP and Network Quality Manager server, using Ctrl+Click or Shift+Click as necessary, and then click Edit > Copy.
  3. Locate your second VoIP and Network Quality Manager server on your network, and then open its Orion Reports folder, located in Program Files\SolarWinds\Orion\.
  4. Click Edit > Paste to paste your reports in the Reports folder on your second VoIP and Network Quality Manager server.

Your original VoIP reports are now available to your second VoIP and Network Quality Manager installation.


Last modified


This page has no custom tags.