You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 12
Next »
The table includes the maximum call performance numbers for the listed call flow.
SBC SWe Lite Performance Numbers
SWe Lite Virtual Machine Resources, applicable to all supported hypervisors (KVM, VMware®, Hyper-V®)1 | Maximum SIP with corresponding RTP Sessions | SIP Signaling Sessions | RTP Media Sessions |
RTP Media Manipulation Mode (transcode, in-band services, encryption, and other services) | RTP Proxy Media Mode | Max Call Rate Setup (CPS) |
|
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 | 10 | 100 |
2 | 1.5 GiB | 1000 | 1000 | 5000 | 100 | 100 | 100 | 1000 | 1000 | 10 | 1000 |
4 | 2.5 GiB | 1000 | 1000 | 5000 | 300 | 300 | 300 | 1000 | 1000 | 10 | 1000 |
1 Default configuration is 1 vCPU and 1 GiB RAM. If additional vCPUs are desired, refer to
Adding vCPU and Increasing Memory.
2 G.722 (AMR) reduces values by 30%.
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 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 SBC SWe Lite supports the following maximum configuration.
SBC SWe Lite Maximum Configuration Values
Feature | Maximum supported |
---|
Number of Groups | |
Cumulative number of channels across all the Signaling Groups | 1000 |
Call Route Entries (all Call Route Tables combined) | 1000 |
| 1024 |
Registrar Table entries | 1000 (1 vCPU) 5000 (2 vCPU and 4 vCPU) |
Registrant Table entries | 600 |
Transformation Table entries | 1000 |
Media Profiles entries | 20 |
Callback Number Tables | 80 |
Callback Numbers (in Callback Numbers List) | 16 |
SIP Server Table entries | |
IP/FQDN or DNS-SRV entries (within each SIP Server Table entry) | 99 |
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.
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..
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 (~%).
For details on system concepts and terminology, refer to Calculating DSP Requirements for SBC SWe Lite.