The table below includes the maximum call performance numbers for the listed call flow.
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 | | | 5000 | | | | | 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.
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 | | 10003 |
F4s | 4 | 1000 | 1000 | 5000 | 400 | 400 | | 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.
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.
Call Capacity Limitations
- Call capacity is limited to 4 calls per second when Info level logging is enabled. Additional logging verbosity reduces the call capacity.
- Although the call setup rate is 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.
The table below indicates the maximum number of concurrent transcoded calls for specific CODEC combinations and system size.
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 |
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 |
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 |
The SBC SWe Lite supports the following maximum configuration.
SBC SWe Lite Maximum Configuration Values
Feature | Maximum supported |
---|
Number of Signaling Groups | 100 |
Cumulative number of channels* across all the Signaling Groups | 1000 (1 vCPU) 4000 (2 vCPU, 4 vCPU, or 10 vCPU) |
Call Route Tables | 100 |
Call Route Entries (all Call Route Tables combined) | 1000 |
Static Routes | 1024 |
Registrar Table entries | 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 | 50 |
Transformation Table entries | 1000 |
Media Profiles entries | 20 |
Callback Number Tables | 80 |
Callback Numbers (in Callback Numbers List) | 16 |
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.
The SBC SWe Lite supports local call forking for up to eight separate destinations. Additionally, the SBC SWe Lite supports up to 20 early dialog responses and 20 calls forked downstream.
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.
If multiple calls arrive simultaneously, the SBC SWe Lite will service the calls until it reaches a CPU usage threshold (configured raise TCA threshold).
- When the threshold is reached, the SBC SWe Lite will reject calls until it reaches a "safe" level clear TCA threshold).
- When the "safe" level is reached, the SBC SWe Lite will begin accepting new calls.
For details on supported RTP media services and licensing requirements, please refer to Calculating Virtual Machine Requirements for an SBC SWe Lite.
For details on system concepts and terminology, refer to Calculating Virtual Machine Requirements for an SBC SWe Lite.