Occupancy Summary Measurements field descriptions

Last Updated : Dec 01, 2021 |

Name

Description

Meas Hour

Measurement hour. The starting time, using 24-hour clock of the hour, during which the data is recorded. Data is listed beginning with the most recently completed hour in the preceding 24-hour interval. For additional details, see the Avaya Aura® Communication Manager Hardware Description and Reference.

Meas Minute

Measured minute. (Last-Hour Report) The end-time of the 3-minute interval for which the measurement is taken. The data takes the form hh:mm, where hh is the hour and mm is the end-time for the 3-minute interval.

Date of Occurrence

Busiest-Interval report. The date and end-time of the 3-minute interval for which the data is collected. The data takes the form MM/dd/mm:hh, where MM is the month, dd is the day, hh is the hour, and mm is end of the 3-minute interval.

Stat Occ

Static occupancy. The percentage of occupancy used by high priority background processes in support of call processing, maintenance, and administration functions. Examples of this activity are high level sanity checks, system timing, polling of adjuncts, and operating system support. This also includes some call processing occupancy for BX.25 and ISDN-PRI traffic.
Note:

Static occupancy remains fairly consistent in an idle configuration. However, it increases as traffic is introduced into the system.

CP Occ

Call Processing occupancy. The percentage of occupancy used by call processing-level processes. The processing of CDR, DCS, ISDN, and other adjunct interfaces is also included in this level. Note that some occupancy due to BX.25 and ISDN-PRI call traffic is counted as static occupancy instead of CP Occ.
Note:

It is not desirable for any system to function at 100 percent processor occupancy. Rather, the CP Occ and Stat Occ fields should total no more than a maximum of 75 percent. By maintaining this 75 percent maximum limit, other system functions can be performed and bursts of caller activity can also be accommodated.

Suggested actions: If the 75 percent maximum limit is exceeded, take one or more of the following steps to lower call processing occupancy:

  • If the users do not get a dial tone immediately, users must wait 10 to 15 seconds before going on-hook and off-hook again.

  • If the system is part of a private network and receives a large amount of traffic from another system in the private network, consider reconfiguring the network.

  • Check the administration translation and verify all digital sets, administered with display modules, actually have display modules. For sets without display modules, change the administration translations to indicate that the digital sets are without a display module.

  • Check the hardware error log for high levels of maintenance activity.

Sm Occ

System Management occupancy. The time taken by lower priority activities, such as administration and maintenance command processing, maintenance activity, error logging, and Light-Emitting Diode (LED) audits. For additional details, see the Avaya Aura® Communication Manager Hardware Description and Reference.

Idle Occ

Idle occupancy. The amount of time the processor is unused. Several factors drive down this number including the following:

  • A large offered load increases CP occupancy.

  • A switch with many stations and trunks requires a high level of background maintenance and increases SM occupancy.

  • Frequent demand testing or administration increases SM occupancy.

These factors may reduce the idle occupancy to almost 0 percent during several 3-minute intervals. On a heavily loaded configuration with frequent demand testing, the idle occupancy may drop to low levels for longer periods (perhaps 1–2 hours). These situations are normal and do not indicate a problem with the configuration.

However, a lightly-loaded configuration with few stations translated and little demand maintenance or administration should not experience long periods of low idle occupancy (less than 15 percent). If this is the case, a problem is likely.

Total Calls

Total calls. The total number of calls connected during the listed hour. Calls are counted in the time interval the calls are answered and not in the time interval the calls are dropped. Therefore, a call that starts in one time interval and ends in another is counted only in the time interval where it originates.

Tandem Calls

Tandem calls. The number of trunk-to-trunk calls connected during the last hour.

Total Conn

Total connections. The number of call attempts made during the measurement interval. The following occurrences count as an attempt:

  • A user lifts the station handset and hangs up before dialing any digits (off-hooks).

  • A user lifts the station handset, dials the destination number, but the far end is busy, and the user hangs up (no answer).

  • A user lifts the station handset, dials the destination number, the far end is busy.

  • A user places a call, and the dialed number answers.

  • A user adds a second party onto the call.

  • An incoming trunk seizure.

  • Maintenance requests an outgoing trunk be seized.

  • Tandem calls (either pnet or public network) result in 2 attempts, but only one total call.

  • AUDIX audits of message waiting lamps.

  • AUDIX Leave Word Calling activations.

Note:

Mathematically, the Total Conn field is the total of the Intcom Atmpts, Inc Atmpts, Out Atmpts, and Pnet Atmpts fields.

Intcom Atmpts

Intercom attempts. This field includes the sum of two types of calls. The first type is extension-to-extension calls on the same configuration. The second type is partially completed calls where a local extension goes off-hook and then hangs up before the call is answered. The second type of call includes includes both busy and unanswered calls.

Inc Atmpts

Incoming attempts. The number of incoming trunk seizures from public network facilities.

Out Atmpts

Outgoing attempts. The number of outgoing trunk seizures made from public network facilities.

Pnet Atmpts

Private network attempts. The number of incoming and outgoing seizures made over private network facilities. Note that a tandem call is counted as two private network attempts, since tandem includes both incoming and outgoing trunk seizures.
Note:

The determination of whether a call is over public network or over private network facilities depends on the trunk type. For ISDN-PRI facilities, the type of call also depends on the service type.