Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
JIRAIDAUTHSBX-60968
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd230966, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca1903b3, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbfc06de, userName='null'}

Panel

In this section:

Table of Contents
maxLevel4

 

Use this profile to configure the

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

 

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 the I-SBC. Please create a custom traffic profile that matches the actual traffic offered to the I-SBC to get the maximum capacity.

 

For 

Spacevars
0product3
 (D-SBC), the profiles are automatically configured based on the personality. These profiles prevent reboot during instantiation.
Caption
0Table
1SBC SWe Cloud Automatic Configuration
3SBC SWe Cloud 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

Info
titleNote

Once the distribution of vCPUs is set,

Spacevars
0product2
overload behavior functions the same way as the
Spacevars
0series5
hardware platforms.

Caption
0Table
1SBC SWe Active Profile Parameters Profiles
3SBC SWe Active Profile Profiles
Profile
Description
defaultBy default, non-cloud instances use the default profile. This profile retains the SBC SWe behavior of earlier release (5.0.x and 5.1.x releases), where signaling and media vCPUs overlap.
standard_callmix_profile

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

standard_msbc_profile

This profile gets auto-configured on the cloud-based M-SBC instance.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 the cloud-based S-SBC instance.
standard_transcoding_profileThis profile utilizes the vCPUs for transcoding calls.
standard_highcps_callmix_profile

This profile is similar to standard passthrough profile with higher CPS.

Available_since
TypeAvailable Since
Release6.2.1

Command Example

Activate a traffic profile using the SWe Active 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

 

Pagebreak