3.13 HuntGroupUsage

Use this Knowledge Script to monitor the status of hunt groups. This script raises an event if a monitored value exceeds the threshold you set. In addition, this script generates data streams for the following statistics:

Number of answered calls
Number of queued calls
Number of abandoned calls
Average call wait time

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

3.13.1 Resource Object

AvayaCM Hunt Group object

3.13.2 Default Schedule

By default, this script runs every hour because the SNMP data it monitors is updated only once an hour. If you change the schedule to a shorter interval, you may receive SNMP request errors until the SNMP data is repopulated.

3.13.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 HuntGroupUsage job. The default is 5.
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 Answered Calls
Event Notification
Raise event if number of answered calls exceeds threshold?	Select Yes to raise an event if the number of calls answered in the hunt group exceeds the threshold you set. The default is Yes.
Threshold - Maximum number of answered calls	Specify the highest number of calls that can be answered in the hunt group before an event is raised. The default is 100 calls.
Event severity when number of answered calls exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of calls answered in the hunt group exceeds the threshold. The default is 15.
Data Collection
Collect data for number of answered calls?	Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls answered in the hunt group during the monitoring period. The default is Yes.
Monitor Abandoned Calls
Event Notification
Raise event if number of abandoned calls exceeds threshold?	Select Yes to raise an event if the number of calls abandoned in the hunt group exceeds the threshold you set. The default is Yes. A call is considered abandoned when the caller hangs up before the call is answered.
Threshold - Maximum number of abandoned calls	Specify the highest number of calls that can be abandoned before an event is raised. The default is 5 calls.
Event severity when number of abandoned calls exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of abandoned calls exceeds the threshold. The default is 15.
Data Collection
Collect data for number of abandoned calls?	Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls that were abandoned during the monitoring period. The default is unselected.
Monitor Queued Calls
Event Notification
Raise event if number of queued calls exceeds threshold?	Select Yes to raise an event if the number of calls in queue exceeds the threshold you set. The default is Yes.
Threshold - Maximum number of queued calls	Specify the highest number of calls that can be in queue before an event is raised. The default is 100 calls.
Event severity when number of queued calls 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 exceeds the threshold. The default is 15.
Data Collection
Collect data for number queued calls?	Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls that were in queue during the monitoring period. The default is Yes.
Monitor Average Call Wait Time
Event Notification
Raise event if average call wait time exceeds threshold?	Select Yes to raise an event if the average amount of call wait time exceeds the threshold you set. The default is Yes. Call wait time is the amount of time a call waits before being answered.
Threshold - Maximum average call wait time	Specify the highest amount of average wait time that calls can experience before an event is raised. The default is 1 minute.
Event severity when average call wait time exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the average amount of call wait time exceeds the threshold. The default is 15.
Data Collection
Collect data for average call wait time?	Select Yes to collect data for charts and reports. If enabled, data collection returns the average amount of wait time that calls experienced during the monitoring period. The default is unselected.