In this section:
For SWe Lite performance and capacity, refer to SBC SWe Lite Performance and Capacity.
Performance Criteria
Silence suppression on test equipment is set to 62%. Average call length is set to 2 minutes. Call setup rate is 4 calls per second.
The performance numbers below depict typical scenarios. Actual performance values may vary depending upon actual configurations and applications used.
A DSP calculator provides information for calculating DSP resource requirements. See Creating and Modifying Voice Codec Profiles for the list of supported codecs.
When ICE-Lite is activated and calls are established, a performance degradation related to call establishment may occur.
SBC Edge Call Performance
A SIP Channel is a Signaling Group (SG) logical attribute used to represent a potential path for a SIP session (call) leg between the SBC and the remote peer associated with the SG. The SIP channel is not synonymous with a SIP session; the number of SIP channels may equal or exceed the number of supported maximum SIP sessions.
Version 1 (v1) refers to hardware for releases up to and including Release 6.0. Version 2 (v2) refers to hardware for Release 6.1 and later.
SBC 1000 v1/v2 and SBC 2000 v1/v2 Performance Numbers
Setup |
|
|
| ||
|---|---|---|---|---|---|
Side 1 Protocol | Side 2 Protocol | SBC Edge 1000 v1 Max Sessions/Channels | SBC Edge 1000 v2 Max Sessions/Channels | SBC Edge 2000 Max Sessions/Channels | Call Rate |
ISDN/T1 | SIP | 48 Sessions (48 ISDN/T1 channels, each associated with a single SIP channel) | 96 Sessions (96 ISDN/T1 channels, each associated with a single SIP channel) | 384 Sessions (384 ISDN/T1 channels, each associated with a single SIP channel) | 4 cps |
ISDN/E1 | SIP | 60 Sessions (60 ISDN/T1 channels, each associated with a single SIP channel) | 120 Sessions (120 ISDN/T1 channels, each associated with a single SIP channel) | 480 Sessions (480 ISDN/T1 channels, each associated with a single SIP channel) | 4 cps |
| FXS | SIP | 24 Sessions (24 FXS channels, each associated with a single SIP channel) | 24 Sessions (24 FXS channels, each associated with a single SIP channel) | 48 Sessions (48 FXS channels, each associated with a single SIP channel) | 4 cps |
| FXS | PRI | 24 Sessions (24 FXS ports, each associated with a single PRI channel) | 24 Sessions (24 FXS ports, each associated with a single PRI channel) | 24 Sessions (24 FXS ports, each associated with a single PRI channel) | 1 cps |
| FXS | BRI | 8 Sessions (8 FXS ports, each associated with a single BRI channel) | 8 Sessions (8 FXS ports, each associated with a single BRI channel) | N/A | 1 cps |
| FXO | SIP | 24 Sessions (24 FXO ports, each associated with a single SIP channel) | 24 Sessions (24 FXO ports, each associated with a single SIP channel) | N/A | 4 cps |
| BRI | SIP | 24 Sessions (24 BRI channels, each associated with a single SIP channel) | 24 Sessions (24 BRI channels, each associated with a single SIP channel) | N/A | 4 cps |
SIP | SIP | 160 Sessions (160 SIP calls, each with two SIP channels), 25 video sessions | 192 Sessions (192 SIP calls, each with two SIP channels), 25 video sessions | 600 Sessions (600 SIP calls, each with two SIP channels), 100 video sessions | 3 cps |
Call Capacity Limitation with Additional Logging
SBC Edge call capacity is limited to four calls per second when Warn level logging is enabled. Additional logging verbosity reduces the call capacity.
SBC Edge 2000 v1/v2 Maximum Concurrent Calls with TLS
The SBC Edge 2000 v1/v2 is capable of 600 channels (maximum) while using TLS when connection reuse is enabled in the SIP Server Table.
Although the call setup rate is 4 calls per second for the SBC Edge 2000 v1/v2 , and 3 calls per second for the SBC Edge 1000 v1, if Call Admission Control (CAC) is enabled, calls over the rate limit will be rejected with the message 480 Temporary Not Available. Call Admission Control is implemented for SIP calls only (one leg of the call must be SIP for call admission control to be used).
SBC Edge System Capacities
SBC Edge Gateway Capacity
The SBC Edge gateway supports the following maximum configuration.
SBC 1000/2000 Gateway Maximum Configuration Values
Feature | Maximum Supported | ||
|---|---|---|---|
SBC Edge 1000 v1 | SBC Edge 1000 v2 | SBC Edge 2000 | |
Number of Signaling Groups | 100 | 100 | 100 |
Cumulative number of channels across all the Signaling Groups | 600 | 600 | 4,000 |
SIP Servers (all three protocols UDP, TCP, TLS) | 20 | 20 | 100 |
Call Route Entries (all Call Route Tables combined) | 1,000 | 1,000 | 15,000 |
| Static Routes | 1,024 | 1,024 | 1,024 |
Registrar Table entries | 600 | 600 | 1,000 |
Contact Registrant Table entries | 600 | 600 | 1,000 |
Transformation Table entries | 1,000 | 1,000 | 1,000 |
Media Profiles entries | 20 | 20 | 20 |
| TDM/Analog Calls | 84 | 144 | 480 |
| IP/IP Calls | 160 | 192 | 600 |
| Simultaneous Calls | 160 | 192 | 600 |
| Callback Number Tables | 80 | 80 | 80 |
| Callback Numbers (in Callback Numbers List) | 16 | 16 | 16 |
| SIP Message Rule Tables | 100 | 100 (32 SIP Message Rules per Table) | 100 |
Ribbon Application Solution Module – Simultaneous Call Capacity
The SBC Edge Application Solution Module supports the following call capacities under the following configurations. This is the number of simultaneous calls you can make on a single ASM.
Microsoft Lync SBA Call Capacities
ASM Application | SBC Edge 1000 v1 AMN | SBC Edge 1000 v1 AME | SBC Edge 1000 v2 | SBC Edge 2000 |
|---|---|---|---|---|
Office Communications Server 2007 R2 Mediation Server | 40 | 100 | 240 | 240 |
Lync 2010 Survivable Branch Appliance | 40 | 100 | 240 | 240 |
| Lync 2013 Survivable Branch Appliance | 40 | 100 | 240 | 240 |
| Skype for Business Survivable Branch Appliance | 40 | 100 | 240 | 240 |
Ribbon Application Solution Module – Simultaneous Lync User Capacity
The SBC Edge Application Solution Module supports the following Lync/Skype for Business user capacities under the following configurations. This is the number of users you can assign to an ASM pool.
ASM Lync User Capacities
| ASM Lync Users | SBC Edge 1000 v1 AMN | SBC Edge 1000 v1 AME | SBC Edge 1000 v2 | SBC Edge 2000 |
|---|---|---|---|---|
| Simultaneous User Max | 25 | 400 | 1000 | 1000 |
*One user can have more than one endpoint connected to the SBA.
Ribbon SBC 1000 DSP Capacities
SBC 1000 DSP Capacities
SBC Edge 1000 v1 DSP Location | Maximum |
|---|---|
Main Board M823x6 DSP | 32 |
M823x9 Module #1 | 64 |
M823x9 Module #2 | 64 |
Maximum Density | 160 |
SBC Edge 1000 v2 DSP Location | Maximum |
|---|---|
Main Board M823x9 DSP | 64 |
M823x9 Module #1 | 64 |
M823x9 Module #2 | 64 |
Maximum Density | 192 |
Advanced Call Flow Limitations
The following limitations pertain to the ability of Ribbon SBC 1000 v1/v2 to attain the maximum DSP call capacity figures presented above.
- Maximum simultaneous SIP to SIP call capacity (licensed by a customer) is not assured when the Ribbon SBC 1000 v1/v2 is supporting active TDM/analog to SIP calls.
- Maximum simultaneous TDM/analog to SIP call capacity is not assured when the Ribbon SBC 1000 v1/v2 is supporting active SIP to SIP calls.
- Enabling encryption (i.e. SRTP) on SIP call legs may reduce maximum simultaneous call capacity.
- Selection of codec on SIP call legs may reduce maximum simultaneous call capacity. For example, maximum call capacity may not be realized with a complex codec (e.g. G.729a with 10ms packet interval, etc.) as opposed to a less complex encoding scheme (e.g. G.711 with 20ms packet interval).
- Maximum simultaneous call capacity may be reduced by:
- Any IP call that is first routed to another IP endpoint, but fails, and is then re-routed to FXS or ISDN endpoint.
- Any calls where local call forking (call forking performed by the Ribbon SBC 1000/2000) is involved.
- Maximum simultaneous call capacity may be reduced by any call involving a blind transfer initiated from an IP endpoint.
Call Forking
The SBC 1000/2000 v1/v2 supports local call forking up to eight separate destinations. Additionally, the SBC 1000/2000 v1/v2 supports up to 20 early dialog responses and 20 calls forked downstream.
Impact of Additional Media Streams (due to Video Call Pass-through) on Call Performance/Capacity
Video calls in Hybrid/Proxy Mode
- Multiple stream for call rate: the calls per second (CPS) capacity does not change when each call contains multiple streams.
- Multiple stream for simultaneous calls: the maximum channels capacity is limited by the total bandwidth available for video streams. The maximum channel capacity will not be affected with low to medium video resolution using up to 500 kbps per stream.
- Single stream call: the calls per second (CPS) capacity is not affected.
Impact of ICE Lite, DTLS, and RTP/RTCP Multiplexing
- When activating ICE Lite, DTLS or RTP/RTCP Multiplexing, the calls per second (CPS) capacity may change to 3 CPS.
SIP Session Licensing
A SIP session for licensing purposes ("SIP session license") is a call (audio/audio+video) under SBC direction. Details are as follows:
- A SIP session is a SIP transaction that establishes a bi-directional audio/video media exchange (RTP media stream) between two ports on the SBC.
- SIP sessions are established by the SBC when the system has recognized the availability of SIP session license "tokens" in the SIP session license token pool.
- SIP session license tokens are added to the pool when a SIP session license has been successfully applied to the SBC. For example, the SBC-1K-LIC25SIP license adds 25 SIP session license tokens to the SBC SIP session license pool.
- To set up the call, the SBC grabs a license token from the purchased SIP session license pool, sets up the call for the bi-directional RTP media stream, and then releases the license token after the call is taken down.
- The media does not have to actually flow through the SBC; the license token is still grabbed to set up the media flow, whether or not the media physically transits the SBC.
- It is possible to consume more than one SIP session license during a single call between two SIP clients. For example, a call that "hairpins" (i.e. one pair of ports supports one RTP media stream through the SBC, and another pair supports a second media stream through the SBC) will consume two SIP session licenses.
SIP transactions that are not directly related to a call setup/teardown are not licensed through the SIP session licenses. Generally, these transactions are free (e.g. SUBSCRIBE, etc.) except when they fall under a chargeable feature. For example, the SBC supports SUBSCRIBE method pass through related transactions (For example, one SIP client to inform another that a message is waiting, etc.) in a way that is limited by available CPU resources, and not by licenses.
For more information on available SIP session license available for purchase, and the procedure to apply licenses to a given SBC device, please refer to Working with Licenses.
Exceptions
A SIP session license is not consumed from the pool of licensed SIP sessions when a SIP↔SIP call has, on all legs (ingress and egress), any one of the following devices identified as the subtended peer:
- SBC Edge (SBC 1000, SBC 2000, and SBC SWe Lite)
- VX
- Tenor
As a result, you do not need to purchase and apply a SIP session license for these calls.
For clarity, please note a SIP session license is consumed when a single leg (ingress or egress, not both) of a SIP↔SIP call has an SBC Edge, VX or Tenor product identified as the subtended peer.
SIP Session License Consumption for SBA and CCE Deployments
SIP Session License Consumption
Configuration | Call Flows | SIP Session Tokens Consumed by Call Flow |
|---|---|---|
( [ SBA ↔ SBC ] represents the physical SBC with onboard SBA application) | Skype for Business/Lync client number 1 ↔ [ SBA ↔ SBC ] ↔ SIP client number 1 | 1 |
| Skype for Business/Lync client number 1 ↔ [ SBA ↔ SBC ] ↔ SIP-based PBX client number 1 | 1 | |
| Skype for Business/Lync client number 1 ↔ [ SBA ↔ SBC ] ↔ FXS/FXO port | 0 | |
| Skype for Business/Lync client number 1 ↔ [ SBA ↔ SBC ] ↔ TDM (BRI/PRI) DS0 channel | 0 | |
| Skype for Business/Lync client number 1 ↔ [ SBA ] ↔ Skype for Business/Lync client number 2 | 0 | |
| SIP client number 1/SIP-based PBX client number 1 ↔ [ SBC ] ↔ SIP client number 2/SIP-based PBX client number 2 | 1 | |
SBC Edge With Onboard CCE Application ( [ CCE ↔ SBC ] represents the physical SBC with onboard CCE application) | Skype for Business/Lync client number 1 ↔ [ CCE ↔ SBC ] ↔ SIP client number 1 | 1 |
| Skype for Business/Lync client number 1 ↔ [ CCE ↔ SBC ] ↔ SIP-based PBX client number 1 | 1 | |
| Skype for Business/Lync client number 1 ↔ [ CCE ↔ SBC ] ↔ FXS/FXO port | 0 | |
| Skype for Business/Lync client number 1 ↔ [ CCE ↔ SBC ] ↔ TDM (BRI/PRI) DS0 channel | 0 | |
| Skype for Business/Lync client number 1 ↔ [ CCE ] ↔ Skype for Business/Lync client number 2 | 0 | |
| SIP client number 1/SIP-based PBX client number 1 ↔ [ SBC ] ↔ SIP client number 2/SIP-based PBX client number 2 | 1 |
Burst Behavior
If multiple calls arrive simultaneously, the SBC Edge will service the calls until it reaches a CPU usage threshold (configured raise TCA threshold).
Although TCA can be configured, Ribbon strongly recommends using the default configuration and not changing the levels. For details on TCA, refer to Working with Historical Data and TCA Thresholds.
- When the threshold is reached the SBC Edge will reject calls until it reaches a "safe" level (configured clear TCA threshold).
- When the "safe" level is reached, the SBC Edge will begin addressing calls in the queue.
Turning on the CAC or logs could exacerbate this issue.
IPsec Performance
The SBC 2000 supports a maximum of 300 simultaneous when the calls are placed over an IPsec tunnel. The SBC 1000 can handle full call capacity over an IPsec tunnel.
Overview
Content Tools