High-capacity servers

Mid-capacity servers

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

Avaya SBC supports up to 250 Internet telephony service providers (ITSPs) per system.

Avaya SBC supports up to 250 tenants per system.

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

Additional capacity values for for low-capacity servers

Avaya SBC supports up to 25 Internet telephony service providers (ITSPs) per system.

Avaya SBC supports up to 25 tenants per system.

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.

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.