What are Performance Thresholds?

For most metrics, UC Monitor provides default performance thresholds that establish a foundation for VoIP performance monitoring and reporting. Performance thresholds define the boundaries of acceptable performance behavior.

UC Monitor uses performance thresholds to determine when incidents are created and to rate collected data. For example, a call quality latency threshold of 150 milliseconds indicates a Degraded condition. If latency data crosses that threshold, UC Monitor rates the data as Degraded in call quality reports. Similarly, a measurement of 400-millisecond latency indicates an Excessive condition in reports.

Default thresholds were selected according to well-defined industry standards for acceptable VoIP and video performance from the perspective of network users. UC Monitor offers the following sets of performance thresholds:

Call setup thresholds, which trigger incidents in response to poor call setup, such as an excessive delay to dial tone.
Call quality thresholds, which trigger incidents in response to poor call quality, such as low MOS.
Video quality thresholds, which trigger incidents in response to poor video quality, such as video packet loss.

Note: Call quality incidents, which include video quality incidents, take precedence over call setup incidents when the incidents occur during the same incident interval, and the severity of the call quality incidents is equal to or greater than the severity of the call setup incidents.

For a monitored metric, two threshold levels are available:

Degraded threshold: Indicates a decline in performance
Excessive threshold: Indicates a severe decline in performance

Threshold values are not inclusive. They must be crossed, not met, before an incident is created.

This section contains the following topics:

Call Quality Thresholds

Call Setup Threshold

Video Quality Thresholds