Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a, userName='null'}
JIRAIDAUTHSBX-121431
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c86fbb89c0016ff0804098000f, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbfd06fb, userName='null'}


Panel

In this section:

Table of Contents
maxLevel4


Use this profile to configure the the 

Spacevars
0product2
 active profile name using the built-in standard profiles.

Excerpt Include
SBXDOC121:_SBC_1:1_Scenario_with_RAMP
SBXDOC121:_SBC_1:1_Scenario_with_RAMP
nopaneltrue

Info
titleNote

This feature is only applicable when four or more vCPUs are configured. 


Info
titleNote

An active profile cannot be deleted.


Warning
titleService Impacting:

The active system (and standby system in HA configuration) system is rebooted. All active calls are lost during this process.


Info

Standard profiles make some assumptions regarding the traffic model and, hence, may not be the optimal profile for the deployment of an I-SBC. To get the maximum capacity, create a custom traffic profile that matches the actual traffic input to the I-SBC. Refer to SWe Traffic Profiles - CLI.


0Table1SBC SWe Automatic Configuration3SBC SWe Personality-Based Configuration

For SBC SWe cloud-based deployments, the profiles are automatically configured based on the personality. Auto-configuring a profile prevents reboot reboot during instantiation.

Caption

The following table represents the SBC SWe automatic configuration:

Personality Type

Profile Name

I-SBCdefault
S-SBCstandard_signaling_profile
M-SBCstandard_msbc_profile
 


Command Syntax

The system sweActiveProfile CLI syntax is shown below.

Code Block
% set system sweActiveProfile name <profile name>
	default 
	standard_callmix_profile 
	standard_msbc_profile 
	standard_passthrough_profile 
	standard_signaling_profile 
	standard_transcoding_profile
	standard_highcps_callmix_profile


Command Parameters

The following table lists and describes the standard profiles. 

Caption0Table1SBC SWe Active Profile Parameters Profiles3SBC SWe Active Profile Profiles

Profile

Description

defaultBy default, non-cloud I-SBC instances use the default profile. This profile supports a call mix containing a combination of 98% pass-through and 2% transcoding.
standard_callmix_profile

This profile supports a call mix containing a combination of 90% pass-through and 10% transcoding calls.

standard_msbc_profile

This profile is auto-configured on cloud-based M-SBC instances.This profile utilizes the vCPUs for pass-through calls.

standard_passthrough_profile

This profile utilizes the vCPUs primarily for pass-through calls.

standard_signaling_profileThis profile utilizes the vCPUs for signaling (direct media) calls, and
it
is auto-configured on cloud-based S-SBC instances.
standard_transcoding_profileThis profile utilizes the vCPUs for transcoding calls.
standard_highcps_callmix_profile

This profile is similar to the standard passthrough profile, but with higher CPS.


Command Example

Activate the standard_transcoding_profile as the active traffic profile. 

Code Block
set system sweActiveProfile name standard_transcoding_profile 
commit

The following warnings were generated:
'system sweActiveProfile': To Activate the Profile system will be rebooted.All active calls will be lost during this process. Do you wish to continue?
Proceed? [yes,no]yes


Info
titleNote

For information on the procedure how to activate a custom GPU profile, refer to the section "Configure GPU I-SBC on Openstack" section of the page Configuring SBC SWe in OpenStack Cloud Environment for GPU Transcoding.

pagebreak