Capacity and scalability specification

Last Updated : Dec 16, 2024 |
Prolog information
Metadata
Keywords:

High-capacity servers

Solutions
Server Type
Dell™ PowerEdge™ R640 Avaya Solutions Platform 110 Appliance - Profile 5
Dell™ PowerEdge™ R640 Avaya Solutions Platform 110 Appliance - Profile 3
Dell R660 Avaya Solutions Platform 110 Appliance server - Profile A3
Dell R660 Avaya Solutions Platform 110 Appliance server - Profile A2
Non-encrypted Sessions
25,000
14,000
25,000
14,000
Encrypted Sessions
20,000
9,000
20,000
9,000
Remote Worker Users
(Sessions)
20,000
(10,000)
20,000
(8,000)
20,000
(10,000)
20,000
(8,000)
Avaya Meetings ServerVideo Sessions
800
800
800
800
Transcoding Sessions
1000
1000
1000
1000
TURN/STUN Audio-only Sessions
10,000
6,000
10,000
6,000
TURN/STUN Audio and Video Sessions
1,000
1,000
1,000
1,000
TURN/STUN Tunneling Audio-only Sessions
600
600
600
600
TURN/STUN Tunneling Audio and Video Sessions
300
300
300
300
HTTP Media Audio-only Tunneling Sessions
220
220
220
220
HTTP Media Audio and Video Tunneling Sessions
110
110
110
110

Mid-capacity servers

Solutions
Server Type
Dell™ PowerEdge™ R340 Avaya Solutions Platform 110 Appliance
VMware ESXi (4 Vcpu)
Nutanix AHV on Nutanix virtualized environment
Dell R360
Non-encrypted Sessions
6,000
5,000
5,000
6,000
Encrypted Sessions
4,000
3,000
3,000
4,000
Remote Worker Users
(Sessions)
5,000
(2,000)
6,000
(3,000)
6,000
(3,000)
5,000
(2,000)
Avaya Meetings Server Video Sessions
200
200
200
200
Transcoding Sessions
150
100
100
150
TURN/STUN Audio-only Sessions
2,200
2,200
1,200
2,200
TURN/STUN Audio and Video Sessions
300
300
300
300
TURN/STUN Tunneling Audio-only Sessions
220
220
220
220
TURN/STUN Tunneling Audio and Video Sessions
110
110
110
110
HTTP Media Audio-only Tunneling Sessions
220
220
220
220
HTTP Media Audio and Video Tunneling Sessions
110
110
110
110

Additional capacity values for high-capacity and mid-capacity servers

Avaya SBC supports up to 250 Internet telephony service providers (ITSPs) per system.
Note:
Total Number of Non-Encrypted / Encrypted sessions with the configured ITSPs cannot exceed the numbers quoted in the table above.
Avaya SBC supports up to 250 tenants per system.
Note:
Total Number of Remote Worker sessions with the configured tenants cannot exceed the numbers quoted in the table above.
Avaya SBC supports the following reverse proxy capacities per system:
  • 500 HTTP requests per second
  • 50 TLS connections per second
  • 2,000 concurrent webSockets

Low-capacity servers

Solutions
Server Type
KVM Virtualized Environment
VMware ESXi (2 Vcpu)
Dell 3240
Dell VEP1425N
Non-encrypted Sessions
1,500
1000
1000
1000
Encrypted Sessions
500
600
700
700
Remote Worker Users
(Sessions)
500
(500)
1000
(500)
2000
(700)
2000
(700)
SIPREC
NA
NA
NA
NA
Transcoding Sessions
100
NA
NA
NA

Additional capacity values for for low-capacity servers

Avaya SBC supports up to 25 Internet telephony service providers (ITSPs) per system.
Note:
Total Number of Non-Encrypted / Encrypted sessions with the configured ITSPs cannot exceed the numbers quoted in the table above.
Avaya SBC supports up to 25 tenants per system.
Note:
Total Number of Remote Worker sessions with the configured tenants cannot exceed the numbers quoted in the table above.
Avaya SBC supports the following reverse proxy capacities per system:
  • 50 HTTP requests per second
  • 5 TLS connections per second
  • 200 concurrent webSockets

General capacity considerations

Each value in the tables represent the maximum capacity supported by Avaya SBC for that solution and cannot be combined for overall capacity calculations.
The capacity specifications are based on:
  • Codec specification: the G729 and G711 codecs are used for measuring transcoded capacities. Different codecs will have varying results.
  • Call model: the SIP RFC call model in trunk mode is used to establish these capacity specifications.
  • IPv4 vs. IPv6: IPv4 as the transport protocol for calculating non-encrypted sessions with trunking for the Avaya Solutions Platform 100 series server - Profile 5 (Dell™ PowerEdge™ R640). With IPv6, the value may decrease by 20%.
  • All the audio and video session counts are calculated by assuming Avaya SBC anchors media. For all other platforms except Dell 3240, the performance metrics are calculated by testing with the dedicated SBC device managed by a separate EMS.

SIPREC capacities

Each SIPREC stream is equivalent to a one session. For example, a call with single-stream SIPREC is equal to two sessions; an encrypted call with two encrypted sessions is equal to three encrypted sessions.
Note:
For the encrypted session type, both the recorder and contact center line side are encrypted using the same SRTP cryptosuite.
Number of recording streams
Session type
Server Type
Dell™ PowerEdge™ R640 Avaya Solutions Platform 110 Appliance server - Profile 5
Dell™ PowerEdge™ R640 Avaya Solutions Platform 110 Appliance server - Profile 3
Dell™ PowerEdge™ R340 Avaya Solutions Platform 110 Appliance server, and VMware ESXi 7.0/8.0-based server
One
Non-encrypted
15,000
7,000
3,000
Encrypted
10,000
4,500
2,000
Two
Non-encrypted
10,000
4,666
2,000
Encrypted
6,666
3,000
1,666
Three
Non-encrypted
7,500
3,500
1,500
Encrypted
5,000
2,225
1,000
Four
Non-encrypted
6,000
2,800
1,200
Encrypted
4,000
1,800
800
Five
Non-encrypted
5,000
2,333
1,000
Encrypted
3,333
1,500
666

Remote Worker capacity considerations

One exception to the standard capacity values is for remote users and Remote Worker call capacity because registration is required for Remote Worker functionality. Mixed usage of the traffic capacities for solutions will vary and must be determined based on these requirements.
While implementing Remote Worker at maximum capacity limits, set registration expiry timers in Session Manager and in every client at a minimum of 3,600 seconds or one hour.
While implementing Remote Worker at maximum capacity limits in one Avaya SBC or HA pair, under worst-case failover conditions, re-registration for 10,000 users can take up to 20 minutes. During re-registration, all ongoing calls continue uninterrupted. However, under worst-case conditions, a user cannot receive or make new calls during this re-registration time period. Distributing users across multiple Avaya SBC systems significantly reduces this re-registration time.

Presence capacity considerations

The stated session capacities in high-capacity servers is achieved without Presence. For every 5,000 users with Presence there is 10% decrement of supported concurrent sessions due to the high resource utilization of Presence traffic. Mid-capacity and low-capacity values are measured with Presence, having an increment of 25 contacts per user.

VMware ESXi capacity considerations

For VMware ESXi 7.0 and 8.0, it is recommended that capacities are measured with 4 CPU and 8 GB RAM. For more information, see Deploying Avaya Session Border Controller on a Virtualized Environment Platform.

Avaya Meetings Server considerations

For specific Avaya Meetings Server capacities, see Deploying Avaya Meetings Server.