Creating and Assigning Call Quality Thresholds › Create a Call Quality Threshold

Create a Call Quality Threshold

A call quality threshold includes two severity settings for each metric that is monitored: degraded and excessive. Threshold properties include a unique name for the custom settings, an incident response, and an optional description of the settings.

Threshold values are not inclusive. Metrics must exceed a threshold to create an incident. For example, based on the default values, latency of 150 milliseconds does not launch an incident. Latency of 151 milliseconds does launch an incident.

Follow these steps:

1. Click Administration, Policies, Call Performance, Call Quality Thresholds in the navigation bar.

   The Call Quality Threshold List opens.

2. Click New.

   The Call Quality Threshold Properties page opens.

3. Complete the following fields:
   • Name. Provide a name for the custom threshold.
   • Incident Response. Select a response to launch when the threshold is exceeded. The response you created appears in this list.
   • Description. (Optional) Briefly describe the threshold. The description can indicate which pairs of Locations and media devices are assigned the threshold, for example.
4. Select a unit of measure for the MOS and Network MOS metrics, or select None to disable the threshold:
   • MOS: Select this option to monitor call quality that is based on a fixed MOS value for the degraded and excessive thresholds.
   • Codec: Select this option to monitor call quality that is based on the codec that is detected during call monitoring. UC Monitor uses the degraded and excessive thresholds for the detected codec. Codec is the default unit of measure.

     Note: For information about setting codec thresholds, see the use case titled Understanding and Managing Codec Thresholds in the CA Unified Communications Monitor bookshelf on CA Support Online.

5. Select Milliseconds, Percentage, or Decibel (dB) as the unit of measure for the remaining audio and video metrics, or select None to disable the threshold. Disabling thresholds is not recommended.
6. Provide a value for the units of measure. The value for the excessive threshold must be larger than the degraded threshold value.
7. Provide a new value in the Minimum Calls Minutes field. This value sets the minimum amount of time that a metric can cross the threshold during a monitoring interval before an incident is created. The following list describes the default values for each field.
   • MOS and Network MOS: The default values are 4.03 for the degraded MOS threshold, 3.6 for the excessive MOS threshold, and a minimum of 15 call minutes.
   • Packet Loss and Jitter Buffer Loss: The default values are 1 percent for the degraded threshold, 5 percent for the excessive threshold, and a minimum of 15 call minutes.
   • Latency and Video Latency: The default values are 150 milliseconds for the degraded threshold, 400 milliseconds for the excessive threshold, and a minimum of 15 call minutes.
   • ACOM: The default values are 15 dB for the degraded threshold, 6 dB for the excessive threshold, and a minimum of 15 call minutes.
   • Frozen Video, Video Frame Loss, and Video Packet Loss: The default values are 1 percent for the degraded threshold, 5 percent for the excessive threshold, and a minimum of 15 call minutes.

     Tip: Set a lower value for the Minimum Call Minutes field to see incidents more quickly in response to poor call quality performance. Set a higher value to see incidents more slowly, after more data is collected.

8. Save the threshold:
   • Click Save to save the threshold and return to the Call Quality Threshold List. The new threshold appears in the list.
   • Click Save and Add Another to save the threshold and remain on the Call Quality Threshold Properties page to add another custom threshold.

   You can now assign the threshold to a Location or a media device.