Versions Compared

Key

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

Add_workflow_for_techpubs

AUTH2

AUTH1UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
JIRAIDAUTHSBX-89465
REV5UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9450244, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca1903b3, userName='null'}

 

 

AUTH1REV5REV6REV3REV1REV2
Panel

In this section:

Table of Contents
maxLevel2

Info
titleNote

This object is accessible only in SBC SWe and Cloud environments.

 

This section contains the capacity estimations  Use this window to view the system capacity estimates for the current system for all the standard profiles.

To View Swe Capacity Estimate

SWe traffic profiles.

Info
titleNote:

The capacity estimates calculated for the system are based on the specific system characteristics as well as factors that assume that performance recommendations described in KVM Performance Tuning and VNF Performance Tuning are fully implemented.

To maximize call quality (no packet drops, minimal jitter, etc.), it is recommended to run at a load rate that is 90% of the estimated capacity. 


On the SBC main screen, go to System > Security >Swe AllSystem Swe Capacity Estimate. The Swe The Swe Capacity Estimate window is displayedopens.

Caption
0Figure
1SWe Capacity Estimates


Image Modified
 

 

The parameters displayed are:

Caption
0Table
1SWe Capacity Estimate Parameters
3SWe Capacity Estimate Parameters
Parameter
Description
Name

The SWe Active Profile Name.

 
  • default - By default, non-cloud instances comes up with default profile. This profile retains the SBC SWe behavior of earlier releases (5.0.x and 5.1.x), where signaling and media vCPUs  overlapped.
  • standard_signaling_profile - This profile utilizes the vCPUs for signaling (direct media) calls and it is auto-configured on the Cloud based S-SBC instance.
  • standard_passthrough_profile - This profile utilizes the vCPUs for passthrough calls.
  • standard_transcoding_profile - This profile utilizes the vCPUs for transcoding calls.
  • standard_callmix_profile - This profile supports call mix which contain a combination of 90% pass-through and 10% transcoding.
  • standard_msbc_profile - The purpose of this profile is to utilize the vCPUs primarily for passthrough calls. This profile gets auto-configured on Cloud based M-SBC instance.
  • standard_highcps_callmix_profile - This profile is similar to standard passthrough profile with higher CPS.

traffic profile names.

Estimated Session CapacityEstimated number of sessions supported in the system.
Estimated Num SubcribersEstimated number of subscribers supported in the system.
Estimated CPSCpsEstimated maximum calls per second (cps) supported in this system.
Estimated Registration CapacityEstimated maximum registrations/sec supported in this system.
Estimated RefreshRegister Refresh Register CapacityEstimated maximum refresh registrations/sec supported in this system.
Estimated Protected Link BandwidthPPSEstimated maximum link bandwidth supported protected DOS pps in this system. The unit is million packets per second (Mpps).
Max Passthrough SessionsEstimated maximum passthrough sessions.
Max Crypto SessionsEstimated maximum crypto sessions.
Estimated TX PPSEstimated transmitted PPS for estimated sessions
Estimated RX PPSEstimated received PPS for estimated sessions

Pagebreak