Versions Compared

Old Version 21

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 22

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ce5f0b8d, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHCHOR-1899, CHOR-3622397
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e98a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99e02c0, userName='null'}
REV4UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f9, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7f3007b8a00a02355cd1c2f0155cd26c9d6032b, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cabc04c3, userName='null'}

Panel

In this section:

Table of Contents
maxLevel4

 

Note

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

...

Note

Note: For details on calculating DSP Requirements for and determination of VM attributes to host the SBC SWe Lite, refer to Calculating DSP Requirements for SBC SWe Lite.

Multiexcerpt
MultiExcerptNamePerformance
 
Div
classpdf6pttext
Caption
0Table
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 LimitsRTP Media

...

Session LimitsMaximum Call Rate Setup (CPS)

...

...

Media Manipulation Mode

...

2 (Requires Virtual DSP Intervention) 

Proxy Media Mode

...

 (No Virtual DSP Intervention)Audio/Video Streams3
vCPU #GB RAMMaximum TCP/TLS-based

...

SIP↔SIP Signaling SessionsMaximum SIP Registrations (60 minute refresh rate)No transcode, with in-band services scenarioDefault

...

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
11 GiB100

...

3001000

...

100

...

100

...

30063006

...

2510

...

21.5 GiB10001000

...

1000

...

200

...

200

...

10006100065010

...

42.5 GiB100010004/60055000

...

4504/60054504/60051000610006

...

 

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.

 

10010

...

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 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
0Table
1Call Performance - Microsoft Azure Cloud


Azure Virtual Machine (VM) ResourcesMaximum SIP
with corresponding 
RTP Media Sessions1		SIP Signaling Session LimitsRTP Media Session Limits
Media Manipulation Mode2 (Requires Virtual DSP Intervention) Proxy Media Mode (No Virtual DSP Intervention)
VM InstancevCPUMaximum TCP/TLS-based SIP↔SIP Signaling SessionsMaximum SIP Registrations (60 minute refresh rate)No transcode, with in-band services scenarioDefault scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band servicesEncryption services: G.711 RTP ↔ G.711 SRTPNo encryption services: RTP ↔ RTP/SRTP ↔ SRTP
B1MS110101001010103103
F1s1300300100010010030033003
F2s2100010001000200200400310003
F4s4100010005000400400450310003

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

Anchor
Transcoding
Transcoding
Transcoding Capacity

The table below indicates the maximum number of concurrent transcoded calls for specific CODEC combinations and system size.

Multiexcerpt
MultiExcerptNameTranscoding - For KVM, VMWare and Microsoft Hyper-V
Div
classpdf6pttext
Caption
0Table
1Transcoding Capacity - KVM, VMware, Microsoft Hyper-V On-premises Deployments

Transcoding Capacity - KVM, VMware, Microsoft Hyper-V On-premises Deployments

Transcoding ScenarioVirtual Machine vCPU Count
CODEC 1CODEC 21 vCPU2 vCPU4 vCPU
G.711A-law or G.711u-lawG.711A-law or G.711u-law100200600
G.711A-law or G.711u-lawG.72380160480
G.711A-law or G.711u-lawG.726 or G.729100200600
G.711A-law or G.711u-lawAMR WB3876225
G.711A-law or G.711u-lawOpus2454165
G.711A-law or G.711u-lawT.3850100300


Multiexcerpt
MultiExcerptNameTranscoding - For Azure
Div
classpdf6pttext
Caption
0Table
1Transcoding Capacity - Microsoft Azure Cloud Deployments

Transcoding Capacity - Microsoft Azure Cloud Deployments

Transcoding ScenarioMicrosoft Azure VM Instance
CODEC 1CODEC 2B1MS VMF1s VMF2s VMF4s VM
G.711A-law or G.711u-lawG.711A-law or G.711u-law10100200400
G.711A-law or G.711u-lawG.726 or G.72910100200400

SBC SWe Lite Single Instance Capacities

...

Caption
0Table
1SBC 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 or 4 vCPU)

Call Route Tables100

Call Route Entries (all Call Route Tables combined)

1000

Static Routes1024

Registrar Table entries

1000 (1 vCPU, 1 GiB)
5000 (2 vCPU, 1.5 GiB)
5000 (4 vCPU, 2.5 GiB)

Contact Registrant Table entries

1000

Transformation Tables50

Transformation Table entries

1000

Media Profiles entries

20

Callback Number Tables80
Callback Numbers (in Callback Numbers List)16
SIP Server Table entries40
IP/FQDN or DNS-SRV entries (within each SIP Server Table entry)99
SIP Message Rule Tables100
(32 SIP Message Rules per Table)
SIP Profiles100

*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 

Spacevars
0series3
supports local call forking for up to eight separate destinations. Additionally, the 
Spacevars
0series3
supports up to 20 early dialog responses and 20 calls forked downstream.

SIP Session Licensing

A SIP session for licensing purposes ("for licensing purposes ('SIP session license") is  is a call (audio/audio+video) under SBC SBC direction. Details are as follows:

  • A SIP session is a SIP transaction that establishes establishes a bi-directional audio/video media exchange (RTP media stream)  between 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 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 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 

Spacevars
0series3
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 
    Spacevars
    0series3
    will reject calls until it reaches a "safe" level (~60% CPU usageconfigured clear TCA threshold).
  • When the "safe" level is reached, the
    Spacevars
    0series3
     will begin accepting new calls.

 

RTP Media Services Supported

 For details on supported RTP media services supportedand licensing requirements, please refer to Calculating DSP Virtual Machine Requirements for an SBC SWe Lite.

System Concepts and Terminology

For details on system concepts and terminology, refer to Calculating DSP Virtual Machine Requirements for an SBC SWe Lite.

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