In this section:
SWe Lite Release 7.0.4 is the current GA release; SWe Lite Release 8.0.0 will be available shortly.
SBC SWe Lite Call Performance
The table below includes the maximum call performance numbers for the listed call flow.
Note: For details on calculating DSP Requirements for the SBC SWe Lite, refer to Calculating DSP Requirements for SBC SWe Lite.
SBC SWe Lite Performance Numbers
| SWe Lite Virtual Machine Resources, applicable to all supported hypervisors (KVM, VMware® Microsoft Hyper-V)1 | Maximum SIP with corresponding RTP Sessions | SIP Signaling Sessions | RTP Media Sessions | Maximum Call Rate Setup (CPS) | Maximum SIP↔ SIP Sessions | |||||||
| RTP Media Manipulation Mode (transcode, in-band services, encryption, and other services) | RTP Proxy Media Mode | Video Streams3 | ||||||||||
| vCPU # | GB RAM | Maximum TCP/TLS-based SIP Signaling Sessions | Maximum SIP Registrations (60 minute refresh rate) | No transcode, with in-band services scenario | Default transcode scenario: G.711/G.729ab RTP ↔ G.729ab/G.711 SRTP, with in-band services | Complex transcode scenario: G.7xx RTP ↔ G.7xx SRTP, with in-band services2 | Encryption services: G.711 RTP ↔ G.711 SRTP, with or without RTP/UDP/IP header changes | No encryption services: RTP proxy media mode, including RTP↔RTP, SRTP↔SRTP, with or without RTP/UDP/IP header changes | ||||
| 1 | 1 GiB | 100 | 100 | 1000 | 50 | 50 | 50 | 100 | 100 | 25 | 10 | 100 |
| 2 | 1.5 GiB | 1000 | 1000 | 5000 | 100 | 100 | 100 | 1000 | 1000 | 50 | 10 | 1000 |
| 4 | 2.5 GiB | 1000 | 1000 | 5000 | 300 | 300 | 300 | 1000 | 1000 | 100 | 10 | 1000 |
1 Default configuration is 1 vCPU and 1 GiB RAM (Microsoft Hyper-V supports 1 vCPU only). If additional vCPUs are desired, refer to Adding vCPU and Increasing Memory.
2 G.722 (AMR) reduces values by 30%.
3 SWe Lite supports 25 video streams per vCPU to a maximum of 100 streams. Exceeding 4 vCPUs will not allow more than 100 video streams.
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 Limitation with Additional Logging
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.
SBC SWe Lite Single Instance Capacities
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 | 100 (1 vCPU) 1000 (2 vCPU or 4vCPU) |
Call Route Entries (all Call Route Tables combined) | 1000 |
| Static Routes | 1024 |
Registrar Table entries | 1000 (1 vCPU, 1 GiB) |
Contact Registrant Table entries | 1000 |
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) |
*A SIP Channel is defined as a single call leg between the SBC Edge and one subtended SIP Client.
Call Forking
The
Unable to show "metadata-from": No such page "_space_variables"
supports local call forking for 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.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/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 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.
Burst Behavior
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%).- When the threshold is reached, the Unable to show "metadata-from": No such page "_space_variables"will reject calls until it reaches a "safe" level (~60% CPU usage).
- When the "safe" level is reached, the Unable to show "metadata-from": No such page "_space_variables"will begin accepting new calls.
Media Services Supported
For details on media services supported, refer to Calculating DSP Requirements for SBC SWe Lite.
System Concepts and Terminology
For details on system concepts and terminology, refer to Calculating DSP Requirements for SBC SWe Lite.
For additional details on media modes, refer to:
Configuring SBC Edge and SBC SWe Lite for various Media Modes
Overview
Content Tools