Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM - Knowledgebase Articles > Search for calls reaching warning or critical thresholds returns incorrect results after modifying threshold values

Search for calls reaching warning or critical thresholds returns incorrect results after modifying threshold values

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 16, 2016

Views: 644 Votes: 0 Revisions: 7

Issue:

After modifying the values for the critical or warning level thresholds of call quality data in the VoIPConfig database table, the new values are not considered by VNQM when you search for calls reaching warning or critical levels on the Search VoIP Calls page.

Resolution:

After modifying the values in the VoIPConfig database table, make sure that you restart IIS so that VNQM picks up the new values.

Last modified

Tags

Classifications

Public