In Communication Manager, the processor occupancy or the server occupancy consists of:
As system management functions fluctuate, a fixed portion of the total processing capacity is assigned to system management. For all Communication Manager servers, 27% of the total processing capacity of the system is allocated to system management. If the total processor occupancy exceeds approximately 92%, all system management operations are delayed, and subsequent call attempts are rejected.
Considerations
To ensure that the proposed solution design manages the anticipated traffic load, the Avaya Sales Factory team determines the Communication Manager CPU occupancy. Some of the considerations for calculating the traffic usage are:
Busy Hour Call Completion (BHCC) for inbound calls.
Call vectoring, especially for announcements that Communication Manager plays for calls in queue.
The number of simultaneous active SIP trunks. The active SIP trunks that support calls that are in a queue have a greater impact on the Communication Manager CPU occupancy than the number of active SIP trunks that support calls that agents handle.
The Communication Manager release, CPU clock speed, and server duplication mode.
Computer Telephony Integration (CTI) operations, such as monitoring, adjunct routing, and third-party call control.
Intelligent Customer Routing (ICR) and Best Service Routing (BSR) operations.
For more information about traffic engineering and specifications, see the Avaya Aura® Core Solution Description guide.
