Add_workflow_for_techpubs |
---|
AUTH1 | ghoppeUserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
JIRAIDAUTH | SYMCHOR-224844744 |
---|
REV5 | ghoppeUserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | ghoppe |
---|
REV3 | ukabir |
---|
REV1 | neelakab |
---|
|
Warning |
---|
|
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 |
Warning |
---|
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
|
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.
Note |
---|
The performance numbers below depict typical scenarios. Actual performance values may vary depending upon actual configurations and applications used. |
Call Performance
Caption |
---|
0 | Table |
---|
1 | 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 |
|
UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} | REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'} |
---|
REV4 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f9, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca2f03d1, userName='null'} |
---|
|
SBC SWe Lite Call Performance
The table below includes the maximum call performance numbers for the listed call flow.
Note |
---|
Note: For details on calculating DSP Requirements and determination of VM attributes to host the SBC SWe Lite, refer to Calculating DSP Requirements for SBC SWe Lite. |
Multiexcerpt |
---|
MultiExcerptName | Performance |
---|
|
Div |
---|
|
Caption |
---|
0 | Table |
---|
1 | Call Performance - KVM, VMware, Microsoft Hyper-V On-Premises Deployments |
---|
|
SWe Lite Virtual Machine Resources, applicable to all supported hypervisors (KVM, VMware® Microsoft Hyper-V) | Maximum SIP with corresponding RTP Media Sessions1 | SIP Signaling Session Limits | RTP Media Session Limits | Maximum Call Rate Setup (CPS) | Media Manipulation Mode2 (Requires Virtual DSP Intervention) | Proxy Media Mode (No Virtual DSP Intervention) | Audio/Video Streams3 | vCPU # | GB RAM | Maximum TCP/TLS-based SIP↔SIP Signaling Sessions | Maximum SIP Registrations (60 minute refresh rate) | No transcode, with in-band services scenario | Default scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band services | Encryption services: G.711 RTP ↔ G.711 SRTP | No encryption services: RTP ↔ RTP/SRTP ↔ SRTP | 1 | 1 GiB | 100 | 300 | 1000 | 100 | 100 | 3006 | 3006 | 25 | 10 | 2 | 1.5 GiB | 1000 | 1000 | 1000 | 200 | 200 | 10006 | 10006 | 50 | 10 | 4 | 2.5 GiB | 1000 | 10004/6005 | 5000 | 4504/6005 | 4504/6005 | 10006 | 10006 | 100 | 10 | 10 | 2.5 GiB | 1000 | 1200 | 5000 | 1200 | 1200 | 1200 | 1200 | 100 | 10 |
|
|
1Maximum number of concurrent sessions. The number assumes that calls are made using RTP/SRTP Proxy mode, or a mix of RTP/SRTP Proxy, media manipulation and video calls. 3Maximum number of concurrent audio/video sessions. The total system capacity is affected if A/V calls are introduced into the call mix. Maximum number of calls is reduced by the number of video streams used. For example, 1 vCPU instance processing 25 A/V calls has a total capacity of: 300 (max number of calls) - 25 (calls processed with 1 vCPU instance) = 275 calls. 4Maximum number of concurrent sessions (when virtual DSP intervention is applied to 450 sessions) is 1000. 5Maximum number of concurrent sessions (when virtual DSP intervention is applied to 600 sessions) is 600. 6Maximum number of proxy media mode concurrent sessions is reduced by a count equivalent to the active number of concurrent RTP media manipulation sessions. Refer to note 1.
Caption |
---|
0 | Table |
---|
1 | Call Performance - Microsoft Azure Cloud |
---|
|
Azure Virtual Machine (VM) Resources | Maximum SIP with corresponding RTP Media Sessions1 | SIP Signaling Session Limits | RTP Media Session Limits | Media Manipulation Mode2 (Requires Virtual DSP Intervention) | Proxy Media Mode (No Virtual DSP Intervention) | VM Instance | vCPU | Maximum TCP/TLS-based SIP↔SIP Signaling Sessions | Maximum SIP Registrations (60 minute refresh rate) | No transcode, with in-band services scenario | Default scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band services | Encryption services: G.711 RTP ↔ G.711 SRTP | No encryption services: RTP ↔ RTP/SRTP ↔ SRTP | B1MS | 1 | 10 | 10 | 100 | 10 | 10 | 103 | 103 | F1s | 1 | 300 | 300 | 1000 | 100 | 100 | 3003 | 3003 | F2s | 2 | 1000 | 1000 | 1000 | 200 | 200 | 4003 | 10003 | F4s | 4 | 1000 | 1000 | 5000 | 400 | 400 | 4503 | 10003 |
1Maximum number of concurrent sessions. The number assumes that calls are made using RTP/SRTP Proxy mode, or a mix of RTP/SRTP Proxy, media manipulation and video calls. 2Maximum number of concurrent sessions with virtual DSP intervention. See Transcoding Capacity below for details. 3Maximum number of proxy media mode concurrent sessions is reduced by a count equivalent to the active number of concurrent RTP media manipulation sessions. Refer to note 1. |
Note |
---|
title | Number of RTP Port Pairs must be increased above maximum call capacity |
---|
| The number of RTP Port Pairs must be configured slightly larger than the actual number of ports required to support the projected number of calls. We recommend you over-allocate the number of port pairs by approximately 25 - 30% above the number of calls you want to support. For details, see Configuring the Media System. |
Note |
---|
title | Call Capacity Limitations |
---|
| - Call capacity is limited to 4
|
|
Note |
---|
title | Call Capacity Limitation with Additional Logging |
---|
|
call capacity is limited to four (4) - calls per second when Info level logging is enabled. Additional logging verbosity reduces the call capacity.
|
|
note- Although the call setup rate is
| TBD - 10 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). |
System Capacities Gateway Capacity
Transcoding CapacityThe table below indicates the maximum number of concurrent transcoded calls for specific CODEC combinations and system size.
Multiexcerpt |
---|
MultiExcerptName | Transcoding - For KVM, VMWare and Microsoft Hyper-V |
---|
|
Div |
---|
| Caption |
---|
0 | Table |
---|
1 | Transcoding Capacity - KVM, VMware, Microsoft Hyper-V On-premises Deployments (1, 2, 4 vCPU) |
---|
|
Transcoding Scenario | Virtual Machine vCPU Count | CODEC 1 | CODEC 2 | 1 vCPU | 2 vCPU | 4 vCPU |
---|
G.711A-law or G.711u-law | G.711A-law or G.711u-law | 100 | 200 | 600 | G.711A-law or G.711u-law | G.723 | 80 | 160 | 480 | G.711A-law or G.711u-law | G.726 or G.729 | 100 | 200 | 600 | G.711A-law or G.711u-law | AMR WB | 38 | 76 | 225 | G.711A-law or G.711u-law | Opus | 24 | 54 | 165 | G.711A-law or G.711u-law | T.38 | 50 | 100 | 300 |
|
Caption |
---|
0 | Table |
---|
1 | Transcoding Capacity - KVM, VMware, Microsoft Hyper-V On-premises Deployments (10 vCPU) |
---|
|
CODEC 1 | CODEC 2 | 10 vCPU |
---|
G.711A-law or G.711u-law | G.711A-law or G.711u-law | 1200 | G.711A-law or G.711u-law | G.729 | 1200 | Opus | G.711A-law/mu-law | 360 |
|
|
|
Multiexcerpt |
---|
MultiExcerptName | Transcoding - For Azure |
---|
|
Div |
---|
| Caption |
---|
0 | Table |
---|
1 | Transcoding Capacity - Microsoft Azure Cloud Deployments |
---|
|
Transcoding Scenario | Microsoft Azure VM Instance | CODEC 1 | CODEC 2 | B1MS VM | F1s VM | F2s VM | F4s VM |
---|
G.711A-law or G.711u-law | G.711A-law or G.711u-law | 10 | 100 | 200 | 400 | G.711A-law or G.711u-law | G.726 or G.729 | 10 | 100 | 200 | 400 |
|
|
|
SBC SWe Lite Single Instance Capacities
The SBC SWe Lite The
gateway supports the following maximum configuration.
Caption |
---|
0 | Table |
---|
1 | SBC 1000/2000 Gateway SWe Lite Maximum Configuration Values |
---|
|
|
---|
Number of Signaling Groups | 100 | Cumulative number of channels* across all the Signaling Groups |
600 | SIP Servers (all three protocols UDP, TCP, TLS) | 1000 (1 vCPU) 4000 (2 vCPU, 4 vCPU, or 10 vCPU) | Call Route Tables | 100 | 20 | Call Route Entries (all Call Route Tables combined) | 1,0001,0241024 | Registrar Table entries |
600 | 1000 (1 vCPU, 1 GiB) 5000 (2 vCPU, 1.5 GiB) 5000 (4 vCPU or 10 vCPU, 2.5 GiB) | Contact Registrant Table entries | 1000 | Transformation Tables | 60050 | Transformation Table entries | 1,0001000 | Media Profiles entries | 20 |
IP/IP Calls | 160 | Simultaneous Calls | 160 | Callback Number Tables | 80 | Callback Numbers (in Callback Numbers List) | 16 |
|
Sonus Application Solution Module - Simultaneous Call Capacity
The Application Solution Module supports the following call capacities under the following configurations.
Caption |
---|
0 | Table |
---|
1 | 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 |
|
Sonus Application Solution Module - Simultaneous Lync User Capacity
The Application Solution Module supports the following Lync/Skype for Business user capacities under the following configurations.
Caption |
---|
0 | Table |
---|
1 | 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.
SIP Server Table entries | 40 | IP/FQDN or DNS-SRV entries (within each SIP Server Table entry) | 99 | SIP Message Rule Tables | 100 (32 SIP Message Rules per Table) | SIP Profiles | 100 |
*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. |
...
Call Forking
The
supports local call forking
for up to eight separate destinations. Additionally, the
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 not affected.
- Single stream call: the calls per second (CPS) capacity is not affected.
SIP Licensing
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..
Exceptions
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
will make accommodations.SIP Session License Consumption for SBA and CCE Deployments
...
Caption |
---|
0 | Table |
---|
1 | 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 |
|
...
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 or directly between two SIP endpoints.
- 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/tear down 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 licenses available for purchase, and the procedure to apply licenses to a given SBC device, please refer to Working with Licenses.
Burst Behavior
If multiple calls arrive simultaneously, the
will service the calls until it reaches a CPU usage threshold (
~80%configured raise TCA threshold).
Note |
---|
Although TCA can be configured, Ribbon strongly recommends using the default configuration and not changing the default levels. For details on TCA, refer to Working with Historical Data and TCA Thresholds. |
- When the threshold is reached, the will reject calls until it reaches a "safe" level (~60% CPU usageconfigured clear TCA threshold).
- When the "safe" level is reached, the the will will begin addressing accepting new calls in the queue.
Turning on the CAC or logs could exacerbate this issue.
RTP Media Services Supported
For details on supported RTP media services and licensing requirements, please refer to Calculating Virtual Machine Requirements for an SBC SWe Lite.
System Concepts and Terminology
For details on system concepts and terminology, refer to Calculating Virtual Machine Requirements for an SBC SWe Lite.
Pagebreak |
---|
Multiexcerpt include |
---|
MultiExcerptName | ipsec-performance |
---|
nopanel | true |
---|
PageWithExcerpt | Notes and Limitations |
---|