4.14 CDR_CallQuality

Use this Knowledge Script to monitor call detail records (CDRs) and call management records (CMRs) retrieved from the primary Communications Manager for jitter, latency, packet loss, and MOS (Mean Opinion Score).

This script raises an event if a monitored value exceeds or falls below a threshold. In addition, this script generates data streams for average and minimum MOS, and maximum jitter, latency, and packet loss.

This script provides the following features:

Monitoring. In monitoring mode, this script checks the CDR tables at each specified interval for new records that match your query. In the first iteration of the job, this script finds the last record in the CDR table and checks back one interval from there. In subsequent iterations, this script checks for new records that match the query in each interval.
Troubleshooting. In troubleshooting mode, this script runs once and checks the CDR tables for calls whose disconnect time is within the range you select in the Select call disconnect time range parameter.

To run this script in troubleshooting mode, select Run once on the Schedule tab.
Diagnosing. In diagnostic mode, this script works in conjunction with NetIQ Vivinet Diagnostics to diagnose VoIP quality problems detected during monitoring. If a call quality threshold is exceeded, then, by default, this script launches Action_DiagnoseVoIPQuality, a Knowledge Script that in turn launches Vivinet Diagnostics to generate a diagnosis of the problem.

To turn off diagnostic mode, click on the Actions tab, select Action_DiagnoseVoIPQuality, and click Delete. Turning diagnostic mode off or on does not affect the events raised by this script.

4.14.1 Prerequisites

Run the SetupSupplementalDB Knowledge Script to create the CiscoCM supplemental database that will house the call detail records.
Run the CDR_RetrieveCallRecords and CDR_RetrieveConfigData Knowledge Script to populate the database.

For more information, see Understanding the CiscoCM Supplemental Database.

4.14.2 Resource Object

CiscoCM_CDRMgmt

4.14.3 Default Schedule

By default, this script runs every five minutes.

4.14.4 Setting Parameter Values

Set the following parameters as needed:

Parameter	How to Set It
General Settings
Job Failure Notification
Event severity when job fails	Set the event severity level, from 1 to 40, to indicate the importance of the failure of the CDR_CallQuality job. The default is 5.
Include call details?	Select Yes to include call details in the events raised by this script. Leave this parameter unchecked to suppress call details. If you select Yes, an event includes the following details: Average and minimum MOS Jitter Latency Lost Packets (%) Originating and Destination Devices Calling and Called Numbers Origination and Disconnect Times Duration (seconds) Calling and Called Number Partitions The default is Yes.
Sort call details table by this value	Select the value from the call details data by which you want to sort. Your can choose from all of the options listed in the previous parameter.
Sort type for call details table	Select a sort type for the call details data. Your options are Ascending or Descending.
Raise event if no records found?	Select Yes to raise an event if there are no CDRs to monitor. Note that we do not mean there are no CDRs with call quality data, but that there are no CDRs at all. The default is unselected.
Event severity when no records found	Set the event severity level, from 1 to 40, to indicate the importance of an event in which no CDRs were found. The default is 25.
Query Filters Despite the number of calls AppManager might find that match the filters you select, an event displays only the first 50 calls. Regardless of the filters you select (or if you select no filters at all), an event displays call data in two tables labeled Inbound and Outbound. The Inbound table contains details of calls coming into the Originating Device (according to the CMR table). The Outbound table contains details of calls going out from the Originating Device (according to the CMR table).
Minimum duration	Set this parameter to filter out records whose call duration is less than the specified value. Accept the default of 0 to ignore the filter for minimum duration.
Maximum duration	Set this parameter to filter out records whose call duration is more than or equal to the specified value. Accept the default of 0 to ignore the filter for maximum duration.
Directory number	Set this parameter to query for those calls whose directory number matches the specified value. Wildcard characters are acceptable. If you use multiple expressions, separate each expression with a comma, such as 123,2345, 234. Leave this parameter blank to search for any directory number.
Device name	Set this parameter to query for those calls whose device name matches the specified value. Wildcard characters are acceptable. If you use multiple expressions, separate each expression with a comma, such as 123,2345,234. Leave this parameter blank to search for any device name.
Troubleshooting
Select call disconnect time range	Select a Specific or Sliding date/time range for which the query should search for data. The default time range is fixed at 24 hours. NOTE:This parameter is valid only when you select Run once on the Schedule tab.
Monitor Average Acceptable Listening MOS
Event Notification
Raise event if average MOS falls below threshold?	Select Yes to raise an event if the average MOS value falls below the threshold. The default is Yes.
Threshold - Average MOS	Specify the lowest average MOS value that must occur to prevent an event from being raised. The default is 3.60.
Event severity when average MOS falls below threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the average MOS value falls below the threshold. The default is 5.
Data Collection
Collect data for average MOS?	Select Yes to collect data for charts and reports. If enabled, data collection returns the average MOS value during the monitoring period. The default is unselected.
Monitor Minimum Acceptable Listening MOS
Event Notification
Raise event if minimum MOS falls below threshold?	Select Yes to raise an event if the minimum MOS value falls below the threshold. The default is unselected.
Threshold - Minimum MOS	Specify the lowest MOS value that must occur to prevent an event from being raised. The default is 3.60.
Event severity when minimum MOS falls below threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the minimum MOS value falls below the threshold. The default is 5.
Data Collection
Collect data for minimum MOS?	Select Yes to collect data for charts and reports. If enabled, data collection returns the minimum MOS value during the monitoring period. The default is unselected.
Monitor Jitter
Event Notification
Raise event if jitter exceeds threshold?	Select Yes to raise an event if the jitter value exceeds the threshold. The default is unselected.
Threshold - Maximum jitter	Specify the highest jitter value that can occur before an event is raised. The default is 60 milliseconds.
Event severity when jitter exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the jitter value exceeds the threshold. The default is 15.
Data Collection
Collect data for jitter?	Select Yes to collect data for charts and reports. If enabled, data collection returns the amount of jitter that occurred during the monitoring period. The default is unselected.
Monitor Latency
Event Notification
Raise event if latency exceeds threshold?	Select Yes to raise an event if the latency value exceeds the threshold. The default is unselected.
Threshold - Maximum latency	Specify the highest amount of latency that can occur before an event is raised. The default is 400 milliseconds.
Event severity when latency exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the latency value exceeds the threshold. The default is 15.
Data Collection
Collect data for latency?	Select Yes to collect data for charts and reports. If enabled, data collection returns the amount of latency that occurred during the monitoring period. the default is unselected.
Monitor Packet Loss
Event Notification
Raise event if packet loss exceeds threshold?	Select Yes to raise an event if the packet loss value exceeds the threshold. The default is unselected.
Threshold - Maximum packet loss	Specify the highest amount of packet loss that can occur before an event is raised. The default is 1%.
Event severity when packet loss exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the packet loss value exceeds the threshold. The default is 15.
Data Collection
Collect data for packet loss?	Select Yes to collect data for charts and reports. If enabled, data collection returns the amount of packet loss that occurred during the monitoring period. The default is unselected.