Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

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: 646 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