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.
VoIP and Network Quality Manager v4.0.1 includes the following new features and improvements:
Windows Server 2012, Windows 8, and SQL Server 2012 are now supported.
Added support for the latest version of Orion.
Added supported for Internet Explorer 10.
|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.||-|
|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 |
|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.|
|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 |
|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.|
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:
Program Files\SolarWinds\Orion\on your original VoIP and Network Quality Manager server.
Shift+Clickas necessary, and then click Edit > Copy.
Your original VoIP reports are now available to your second VoIP and Network Quality Manager installation.
Copyright 1995-2013 SolarWinds Worldwide, LLC. All rights reserved worldwide.
No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of SolarWinds. All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds, the SolarWinds & Design, ipMonitor, LANsurveyor, Orion, and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies. Microsoft®, Windows® and SQL Server® are registered trademarks of Microsoft Corporation in the United States and/or other countries.