NOTE TO REVIEWERS
Please review of this page and let me know if we need to revise particular sections for SWe Lite performance vs. SBC Edge.
If you have values to add at this point please do so, but the goal of this review is to add/change structure where needed. Thanks.
-Greg
FROM SBC SWe Lite - Functional Specification:
The requirements are from CHOR-2
- 10 cps
- 25 simultaneous transcoding sessions
- 25 simultaneous sessions that uses DSP
- 100 simultaneous sessions with maximum of 25 using DSP and rest using RTP Proxy or Direct media mode
- 1,000 SIP endpoint registrations
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.
SBC 1000 and SBC 2000 Performance Numbers
Setup | | |
---|
Side 1 Protocol | Max Sessions/Channels | Call Rate |
---|
ISDN/T1 | 384 Sessions (384 ISDN/T1 channels, each associated with a single SIP channel) | 4 cps |
ISDN/E1 | 480 Sessions (480 ISDN/T1 channels, each associated with a single SIP channel) | 4 cps |
FXS | 48 Sessions (48 FXS channels, each associated with a single SIP channel) | 4 cps |
FXO | N/A | 4 cps |
BRI | N/A | 4 cps |
SIP | 600 Sessions (600 SIP calls, each with two SIP channels) | 3 cps |
Call Capacity Limitation with Additional Logging
Unable to show "metadata-from": No such page "_space_variables"
call capacity is limited to four (4) calls per second when Info level logging is enabled. Additional logging verbosity reduces the call capacity.
Although the call setup rate is TBD calls per second, 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).
The
Unable to show "metadata-from": No such page "_space_variables"
gateway supports the following maximum configuration.
SBC 1000/2000 Gateway Maximum Configuration Values
Feature | Maximum supported |
---|
|
---|
Number of Signaling Groups | 100 |
Cumulative number of channels across all the Signaling Groups | 600 |
SIP Servers (all three protocols UDP, TCP, TLS) | 20 |
Call Route Entries (all Call Route Tables combined) | 1,000 |
| 1,024 |
Registrar Table entries | 600 |
Registrant Table entries | 600 |
Transformation Table entries | 1,000 |
Media Profiles entries | 20 |
IP/IP Calls | 160 |
Simultaneous Calls | 160 |
Callback Number Tables | 80 |
Callback Numbers (in Callback Numbers List) | 16 |
The
Unable to show "metadata-from": No such page "_space_variables"
Application Solution Module supports the following call capacities under the following .
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 |
The
Unable to show "metadata-from": No such page "_space_variables"
Application Solution Module supports the following Lync/Skype for Business user capacities under the following .
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.
The
Unable to show "metadata-from": No such page "_space_variables"
supports local call forking up to eight separate destinations. Additionally, the
Unable to show "metadata-from": No such page "_space_variables"
supports up to 20 early dialog responses and 20 calls forked downstream.
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 not affected.
- Single stream call: the calls per second (CPS) capacity is not affected.
Any SIP <-> SIP call consumes a single SIP session, for the life of the call, within the pool of SIP sessions that have been activated through a license submission..
No SIP session is consumed from the pool of licensed SIP sessions when a SIP<-> SIP call has on any one leg any one of the following devices:
You do not need to purchase a license for these SIP <-> SIP calls because the
Unable to show "metadata-from": No such page "_space_variables"
will make accommodations.
SIP Session License Consumption
Session Type (Lync Client <-> SBA <-> SBC <-> SIP Non-Lync Client) | License Consumption |
---|
Lync Client to SBA | Does not use SIP license |
SBC to non-Lync client | Consumes SBC SIP license |
SBC | Consumes SIP-to-SIP license |
Session Type ( Lync Client <-> SBA <-> Lync Client) | License Consumption |
---|
Lync Client to SBA | SIP SBA license is not consumed |
If multiple calls arrive simultaneously, the
Unable to show "metadata-from": No such page "_space_variables"
will service the calls until it reaches a CPU usage threshold (~80%).
on the CAC or logs could exacerbate this issue.
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.