Versions Compared

Old Version 6

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 7

changes.mady.by.user Ribbon Communications

Saved on

Key

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

 

Panel

In this section:

Table of Contents
maxLevel4

Info
iconfalse

Related articles:

Overview

The performance of the SBC VM can be optimized if the call mix is provided while configuring the SBC SWe instance. A set of predefined call mixes are provided, these are called standard traffic profiles. Additionally, a user can create custom traffic profiles, with a call mix that is more appropriate for the SBC SWe.

The supported standard profiles are:

Caption
0Table
1Supported Standard Profiles
3Supported Standard Profiles
Profile NameDescriptionMinimum vCPU supportedMaximum vCPU supported
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.

424
standard_signaling_profileThis profile utilizes the vCPUs for signaling (direct media) calls and it is auto-configured on the cloud-based S-SBC instance.440
standard_passthrough_profileThis profile utilizes the vCPUs for passthrough calls.440
standard_transcoding_profileThis profile utilizes the vCPUs for transcoding calls.440
standard_callmix_profileThis profile supports callmix which contain a combination of 90% pass-through and 10% transcoding.440
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.

440
standard_highcps_callmix_profileThis profile is similar to standard passthrough profile with higher CPS and the corresponding CHT is 25.440
 

Once the distribution of vCPUs is set, the SBC SWe overload behavior functions the same way as the hardware SBC (5000/7000 series).

Note
titleCaution

This feature is applicable only when the vcpu is more than or equal to four. 

Profiles

Standard Profiles

When any standard profile is activated, the application automatically optimizes the vCPU usage of the SBC SWe VM for the activated profile.

Note
titleCaution
  • SBC SWe instances reboots automatically to activate the profile. All active calls are lost during this process, it is recommended to activate the profile during maintenance.
  • A trap is generated when a new traffic profile is activated.

Appropriate profiles are auto-configured on the D-SBC (microservices) based on the personality as follows:

Caption
0Table
1Personality Types per Profile Name
3Personality Types per Profile Name
Personality TypeProfile Name
I-SBCdefault
S-SBCstandard_signaling_profile
M-SBCstandard_msbc_profile

Info
titleNote

On the D-SBC, the auto-configured profiles prevent reboot during instantiation.

Caption
0Table
1Configuration Tables
3Configuration Tables
Table NameDescription
sweTrafficProfilesContains all the standard profiles and their fixed call-mix.
sweActiveProfileContains the name of active profile and time-stamp of activation.
sweCodecMixProfile

Contains the standard codec_mix profiles.

  1. G711_20ms with 100% G711 (20 ms) calls.
  2. G711_G729_20ms which is initialized with 50% of G729AB (20 ms) and 50% G711 (20ms).
Caption
0Table
1Operational Tables
3Operational Tables
Table NameDescription
sweProcessorCapacityThis table contains the real processor capacity indices relative to a 2690v2 processor with the recommended BIOS/ESXi setting.
sweCapacityEstimateThis table contains the capacity estimations for all the standard profiles.

Custom Profiles

If the call mix is different from one of those corresponding to the standard profiles, a custom profile can be created. You can create custom profiles based on the call mix requirements. While creating a custom profile, you must provide the call mix through CLI.

Note
titleCaution

The estimated calls per second (cps) numbers may vary are calculated based on certain conditions. The actual traffic may have a different number of signalling signaling messages per call and size of the messages. , message size, or call features for which the estimate could be inaccurate.


Pagebreak