Use this Knowledge Script to monitor call activity on a Communications Manager server. This script raises an event if a threshold is exceeded. In addition, this script generates data streams for the following metrics:
Attempted calls
Completed calls
Active calls
In-progress calls
Incomplete calls (%)
Attempted system calls
Completed video calls
This script is a member of the CiscoCM recommended Knowledge Script Group. For more information, see Section 4.57, Recommended Knowledge Script Group.
CiscoCM_CMServer
By default, this script runs every five minutes.
If you are running this script as part of the recommended KSG, do not change the schedule. The schedules for the recommended scripts are staggered so as to lessen the impact on CPU utilization when you run the KSG.
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 CCM_CallActivity job. The default is 5. |
Monitor Active Calls |
|
Data Collection |
|
Collect data for active calls? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls that are active at each script iteration. The default is Yes. A call is considered “active” once a connection is made. |
Monitor Attempted Calls |
|
Event Notification |
|
Raise event if attempted calls exceed threshold? |
Select Yes to raise an event if the number of attempted calls exceeds the threshold you set. The default is Yes. |
Threshold - Maximum attempted calls |
Specify the maximum number of calls that must be attempted before an event is raised. The default is 0 calls. |
Event severity when attempted calls exceed threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of attempted calls exceeds the threshold. The default is 25. |
Data Collection |
|
Collect data for attempted calls? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls that were attempted during the monitoring period. The default is Yes. |
Monitor Completed Calls |
|
Data Collection |
|
Collect data for completed calls? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls that were completed during the monitoring period. The default is Yes. |
Monitor Calls in Progress |
|
Event Notification |
|
Raise event if calls in progress exceed threshold? |
Select Yes to raise an event if the number of in-progress calls exceeds the threshold you set. The default is Yes. A call is considered “in-progress” as soon as the receiver is lifted. |
Threshold - Maximum calls in progress |
Specify the maximum number of calls that must be in progress before an event is raised. The default is 100 calls. |
Event severity when calls in progress exceed threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of in-progress calls exceeds the threshold. The default is 25. |
Data Collection |
|
Collect data for calls in progress? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls in progress at each script iteration. The default is Yes. |
Monitor Incomplete Calls |
|
Event Notification |
|
Raise event if incomplete calls exceeds threshold? |
Select Yes to raise an event if the percentage of incomplete calls exceeds the threshold you set. The default is Yes. |
Threshold - Maximum incomplete calls |
Specify the highest percentage of incomplete calls that must be detected before an event is raised. The default is 0%. |
Event severity when incomplete calls exceed threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the percentage of incomplete calls exceeds the threshold. The default is 25. |
Data Collection |
|
Collect data for incomplete calls? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the percentage of incomplete calls during the monitoring period. The default is Yes. |
Monitor Attempted System Calls |
|
Event Notification |
|
Raise event if attempted system calls exceed threshold? |
Select Yes to raise an event if the number of attempted system calls exceeds the threshold you set. The default is Yes. System calls are signals sent to phones to turn on/off the Message Waiting indicator. A system call is sent to illuminate the indicator when a message is left, and another one is sent to turn off the indicator when the user listens to that message. |
Threshold - Maximum attempted system calls |
Specify the highest number of system calls that must be attempted before an event is raised. The default is 0 calls. |
Event severity when attempted system calls calls exceed threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of attempted system calls exceeds the threshold. The default is 25. |
Data Collection |
|
Collect data for attempted system calls? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of system calls attempted during the monitoring period. The default is unselected. |
Monitor Completed Video Calls |
|
Data Collection |
|
Collect data for completed video calls? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of video calls that were completed during the monitoring period. The default is unselected. |