Page History

...

SBC SWe Lite Call Performance

...

0	Table
1	SBC SWe Lite Performance Numbers

The table below includes the maximum call performance numbers for the listed call flow.

Note
Note: To identify the required resource configuration for a given deployment of an SBC SWe Lite refer to Calculating DSP Requirements for SBC SWe Lite.

Caption
0 Table 1 SBC SWe Lite Performance Numbers
RAM Total Number of vCPUs* Required Memory Number of Registrants Number of Allowed Calls Number of RTP/SRTP Proxy Calls Only Maximum Number of DSP Calls**Calls: Number of RTP/SRTP Proxy Calls (G.711 a/u law RTP/SRTP <==> G.729 A/B/AB RTP/SRTP) Max Call Setup Rate (CPS) Max Number of SIP <-> SIP Session 1 1 GiB (1024 MiB) 1,000 100 100 50 : 50 10 cps 1,000 22 GiB 1.5 GiB (1536 MiB) 5,000 1,000 1,000 100 : 900 10 cps 1,000 44 GiB 2.5 GiB (2560 MiB) 5,000 1,000 1,000 300 : 700 10 cps 1,000   * Default configuration is 1 vCPU and 1 GiB RAM. If additional CPUs vCPUs are desired, refer to Adding vCPU and Increasing Memory. ** In addition to DSP calls, the SWe Lite supports RTP/SRTP Proxy and/or Direct Calls up to the Total Number of Allowed Calls specified for deployment.

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.

...

 

Caption
0 Table 1 SBC SWe Lite Maximum Configuration Values
1,000600600 Feature Maximum supported   Number of Signaling Groups 100 Cumulative number of channels across all the Signaling Groups 1,000 Call Route Entries (all Call Route Tables combined) 1,000 Static Routes 1,024 Registrar Table entries 1000 (1 vCPU) 5000 (2 vCPU and 4 vCPU) Registrant Table entries 600 Transformation Table entries 1,000 Media Profiles entries 20 Callback Number Tables 80 Callback Numbers (in Callback Numbers List) 16 SIP Server Table entries 500 IP/FQDN or DNS-SRV entries (within each SIP Server Table entry) 99

Call Forking

The 

Spacevars
0 series3

supports local call forking for up to eight separate destinations. Additionally, the 

Spacevars
0 series3

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.. 

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:

• SBC Edge
• VX
• Tenor

You do not need to purchase a license for these SIP ↔ SIP calls because the 

Spacevars
0 series3

will make accommodations.

Burst Behavior

If multiple calls arrive simultaneously, the 

Spacevars
0 series3

will service the calls until it reaches a CPU usage threshold (~80%).

• When the threshold is reached,  the 

  Spacevars
  0 series3

  will reject calls until it reaches a "safe" level (~60% CPU usage).
• When the "safe" level is reached, the

  Spacevars
  0 series3

   will begin accepting new calls.

Media Services

...

Supported

• Supported codecs (including for transcode operations): G.711, G.722, G.722.2 (AMR-WB), G.723.1 (5.3 kbps, 6.3 kbps), G.726 (32 kbps), G.729A/B (8 kbps)
• DTMF/RFC4733; Inband DTMF; SIP INFO/RFC-2833
• Voice Activity Detection (VAD)
  

Definitions

...

Spacevars
0 product

...

Spacevars
0 product

...

Spacevars
0 product

...

• 
  

System Concepts and Terminology

For details on system concepts and terminology, refer to SBC SWe Lite Performance and Capacity

Info
For additional details on media modes, refer to: Working with RTP Proxies Configuring SBC Edge and SBC SWe Lite for various Media Modes Creating and Modifying SIP Signaling Groups

 

...

Pagebreak