3.15 PhoneConnectivity

Use this Knowledge Script to monitor disconnected registered phones for a Communication Manager and to maintain a history of the monitored phones in the Avaya CM supplemental database. This script raises an event if the number or percentage of disconnected registered phones exceeds the threshold you set. You can group events by cluster, building, floor, or type of phone.

NOTE:If you bypass SNMP to discover a call manager, this script is not available.

3.15.1 Prerequisites

3.15.2 Resource Object

AvayaCM_ActiveSPE

3.15.3 Default Schedule

By default, this script runs every 10 minutes.

3.15.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 PhoneConnectivity job. The default is 5.

Enable use of SNMP GETBulk operations?

By default, this parameter is enabled, allowing the PhoneConnectivity Knowledge Script job to access Communication Manager MIBs using GETNext and GETBulk SNMP requests, as appropriate.

Disable this parameter to allow the 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 GETNext.

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 much faster MIB data is returned.

If CPU usage is too high, you can reduce the number of rows per GETBulk or disable 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 delay can help manage CPU usage and speed of SNMP requests.

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

Event Notification

Raise event if disconnected registered phones in group exceed threshold?

Select Yes to raise an event if the number or percentage of disconnected registered phones in a group exceeds the threshold you set. The default is Yes.

Use Type of threshold to create a “number” or “percentage” event.

Use Select event grouping to select how to group the deregistered phones.

Select event grouping

Select whether to group disconnected registered phones by Cluster, Building, Floor, or Type of phone. AppManager raises an event when the number or percentage of phones in each group exceeds the threshold you set.

For example, suppose the following were true:

  • You set Maximum number of disconnected registered phones in the group to “5”

  • You set Select event grouping to “Building,” and you have three buildings.

If AppManager detects six disconnected registered phones in the first building, two in the second, and seven in the third, it will raise two events: one for the six disconnected registered phones in the first building and another for the seven disconnected registered phones in the third building. Because you set the threshold to “5,” no event is raised for the disconnected registered phones in the second building.

The default is Cluster.

Type of threshold

Select whether you want to raise events based on the Number or Percent of disconnected registered phones. The default is Number.

Threshold - Maximum number of disconnected registered phones

Use this parameter if you selected Number in Type of threshold.

Specify the maximum number of registered phones that can be disconnected before an event is raised. The default is 0 phones.

Threshold - Maximum percent of disconnected registered phones

Use this parameter if you selected Percent in Type of threshold.

Specify the maximum percentage of registered phones that can be disconnected before an event is raised. The default is 0%.

Event severity when disconnected registered phones exceed threshold

Set the event severity, from 1 to 40, to indicate the importance of an event in which the number or percentage of disconnected registered phones in a group exceeds the threshold you set. The default is 15.

Include phone details in event message?

Select Yes to include details of the disconnected registered phones in the event message. Phone details can include station extension, station name, building, floor, station type, room, cable, jack, port, and deregistration time.

The default is Yes.

Maximum number of detail rows to include in event message

Use this parameter if you selected Yes in Include deregistered phone details in event message.

Specify the maximum number of detail rows to include in an event message. Each row contains details for one phone. Rows are sorted by most recently disconnected phone. Specify “0” to include all rows. The default is 20 rows.