3.3 Announcements

Use this Knowledge Script to monitor announcements for queued calls, calls that dropped while in queue, and peak usage of announcement ports.

Choose whether to monitor specific announcements or the top n announcements. This script raises an event if a threshold is exceeded. In addition, this script generates data streams for calls queued, calls dropped, and peak port usage.

NOTE:If you bypass SNMP to discover a call manager (by selecting the Discover using manual configuration parameter), this script is not available.

3.3.1 Resource Object

AvayaCM Announcement object

3.3.2 Default Schedule

By default, this script runs every hour.

3.3.3 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 Announcements job. The default is 5.

Select monitor type

Select one of the following monitoring options:

  • Top-N — select to monitor n announcements with the highest values for queued calls, dropped calls, or peak port usage. If you select this option, provide the value for n in the Number of announcements to monitor parameter.

  • Comma-separated  — select to monitor specific announcements. If you select this option, provide a list of announcement extensions in the Comma-separated list of announcements to monitor parameter.

Number of announcements to monitor

Specify the number of announcements you want to monitor. The default is 5.

Comma-separated list of announcement extensions

Provide a list of the announcement extensions you want to monitor. You can provide individual extension numbers, a range of extension numbers, or a combination of both. For example: 20001-20020,20055,20100-20200

Separate each number or range with a comma.

Enable use of SNMP GETBulk operations?

Select Yes to allow this Knowledge Script to access Communication Manager MIBs using GETNext and GETBulk SNMP requests, as appropriate. The default is Yes.

Deselect the check box to allow the Knowledge Script to use only GETNext requests.

Not all MIB tables are extensive enough to need a GETBulk request. A GETBulk request is faster, but more CPU-intensive than a GETNext request.

Number of rows to request for each GETBulk operation

Specify the number of rows from the MIB table to return in a GETBulk request. The default is 10 rows.

The number of rows determines how fast the MIB data is returned.

If the CPU usage is too high, you can reduce the number of rows per GETBulk request or deselect the Enable use of SNMP GETBulk requests? parameter.

Interval to pause between GETBulk operations

Specify the number of milliseconds to wait between GETBulk requests. The default is 100 milliseconds.

The length of the delay can help manage CPU usage and the speed of SNMP requests.

For example, a one-row GETBUlk with a 100-millisecond delay between requests executes more slowly and uses less CPU than a GETNext request.

Monitor Calls Queued

Event Notification

Raise event if number of calls queued exceeds threshold?

Select Yes to raise an event if the number of calls in queue for an announcement exceeds the threshold you set. The default is Yes.

Threshold - Maximum calls queued

Specify the highest number of calls that can be in queue for an announcement before an event is raised. The default is 0 calls.

Event severity when number of calls queued exceeds threshold

Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of calls in queue for an announcement exceeds the threshold. The default is 15.

Data Collection

Collect data for calls queued?

Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls in queue for an announcement during the monitoring period. The default is Yes.

Monitor Calls Dropped

Event Notification

Raise event if number of calls dropped exceeds threshold?

Select Yes to raise an event if the number of calls dropped while in queue exceeds the threshold you set. The default is Yes.

Threshold - Maximum calls dropped

Specify the highest number of calls that can be dropped while in queue before an event is raised. The default is 0 calls.

Event severity when number of calls dropped exceeds threshold

Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of calls dropped while in queue exceeds the threshold. The default is 15.

Data Collection

Collect data for calls dropped?

Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls dropped while in queue during the monitoring period. The default is unselected.

Monitor Peak Ports Used

Event Notification

Raise event if peak number of ports used exceeds threshold?

Select Yes to raise an event if the number of ports in use simultaneously exceeds the threshold you set. The default is Yes.

Threshold - Maximum peak ports used

Specify the highest number of ports that can be in use simultaneously before an event is raised. The default is 12 ports.

Event severity when peak number of ports used exceeds threshold

Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of ports in use simultaneously exceeds the threshold. The default is 15.

Data Collection

Collect data for peak ports used?

Select Yes to collect data for charts and reports. If enabled, data collection returns the highest number of ports in use simultaneously during the monitoring period. The default is Yes.