Core Avaya Aura® Session Manager instances

28

Total Number of Dial Patterns

300,000

Number of Dial Patterns per Routing Policy

120,000

Origination Dial Pattern Sets

1,000

100,000 Origination Dial Patterns per Origination Dial Pattern Set

SIP Domains

1,000

SIP Entities

25,000

SIP Entity Links/System Manager

75,000

1. Assuming 3 links for each SIP entity, such as, UDP, TCP, and TLS links.

2. Assuming that each SIP Entity is linked to two Session Managers (for redundancy) with only one transport protocol used. Here, 50,000 links are needed.

In both cases, the inter-Session Manager entity links need to be counted towards the limit.

SIP Entity Links/Session Manager

10,000

Adaptations

25,000

Assuming one Adaptation for each SIP Entity. There can be multiple Adaptation for each SIP Entity and some SIP Entities may not require any Adaptation. SIP Adaptations are applied only on the non-Session Manager entities.

Adaptation Entries

250,000

Full system limit. Includes ingress and egress entries.

Conditions

25,000

Regular Expression Adaptations

25,000

Maximum of 25k regex adaptations

Regular Expressions

1,000

Routing Policies

25,000

Assuming one routing policy for each SIP Entity.

Time Ranges

1,000

Locations

25,000

Considers the use of locations to control bandwidth.

Location IP Address Patterns

50,000

Used to identify if a given SIP endpoint is associated with the location. Based on the assumption that on an average, two patterns are used to define a location.

Local Host Name Resolution Entries

25,000

Based on an average of one for each SIP Entity.

SIP Users

300,000

Total number of users.

Handles/User

3

Total number of SIP handles

1,050,000

Average number of handles/user is 3 (total handles = 350,000 X 3)

Total SIP devices

1,000,000

Total number of devices.

Registered Devices/User

10

A SIP user/station can have multiple registered SIP devices per user, such as an Avaya one-X® Communicator in Shared Control. Session Manager capacities are based on the number of active SIP devices. The number of registered devices per user is important to know to adequately distribute users and devices across Session Manager instances.

Average Buddy List/Contacts for each User

25

Assuming an average of 25 per user (maximum number of 250 per user).

Active (Primary) SIP Devices/Session Manager

23,300 (normal conditions)

25,000 (temporarily under failure conditions)

If a user has multiple registered SIP devices, be careful when distributing users across Session Managers to avoid exceeding the SIP device capacities of an individual Session Manager. For example, 15,000 users each have two registered SIP devices, but 30,000 devices exceed the capacity of a single Session Manager. Instead, assign only 10,750 users to the individual Session Manager to not exceed the 23,300 device capacity limit.

CC Agents/Session Manager

21,600 (normal conditions)

25,200 (failure conditions)

Call Center (CC) Agent SIP devices consume more resources per Session Manager. 21,600 is the maximum for CC Agent SIP devices, assuming all devices are CC agents. When configuring for systems that may support fewer CC Agents, assume that five CC Agent devices are the equivalent of six regular SIP devices.

Presence users

21,600 (normal conditions)

25,200 (temporarily during failure conditions)

Digit Conversion Patterns (ingress)

45,000

Digit Conversion Patterns (egress)

45,000

Users/Session Manager on VMware or KVM on RHEL 8.10

See Deploying Avaya Aura® Session Manager and Avaya Aura® Branch Session Manager in Virtualized Environment on the Avaya support website.

Branch Session Manager instances

5,000

Devices per Branch Session Manager on S8300D (Survivable Embedded)

700

The introduction of Spectre and Meltdown fixes with the Avaya Aura® Release 7.1.3 impacts S8300D scalability performances. A Survivable Remote configuration for Communication Manager SRS and Branch Session Manager with the Spectre and Meltdown fixes enabled can only support 200 users with up to 500 BHCC traffic.

Since the Spectre and Meltdown fixes are enabled by default, consider configuration changes to upgrade to Release 7.1.3.

Consider the following options if the higher capacity is required from the S8300D:

• Disable Spectre and Meltdown fixes on S8300D. This allows the S8300D to deliver the same level of capacity as in the Avaya Aura® Release 7.1.2 and before.

• Upgrade the embedded server to the latest S8300E model if disabling fixes on the S8300D is not viable.

For more information about Spectre and Meltdown fixes included in Avaya Aura® Release 7.1.3, see PSN020346u on the Avaya Support site at: https://downloads.avaya.com/css/P8/documents/101048606.

Devices per Branch Session Manager on ASP S8300E (Survivable Embedded)/VE/KVM on RHEL 8.10

1,000

Devices per Branch Session Manager on Application Services Platform/VE/KVM on RHEL 8.10

5,000

Busy Hour Sessions/Session Manager

648,000

The type of call determines the number of SIP sessions. An SRE call is a single session, so a Busy-Hour Session is equivalent to BHCC. Conversely, a SIP station-to-SIP station call creates three sessions, and the BHCC is calculated accordingly.

Session creations/second/Session Manager

180

Session creations/second/Branch Session Manager

10

Session creations/second /survivable embedded Session Manager

3