Add_workflow_for_techpubs | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
In this section:
|
Info | ||
---|---|---|
| ||
Related articles: |
Use this profile to configure the the
Spacevars | ||
---|---|---|
|
Excerpt Include SBXDOC121:_SBC_1:1_Scenario_with_RAMP SBXDOC121:_SBC_1:1_Scenario_with_RAMP nopanel true
Info | ||
---|---|---|
| ||
This feature is only applicable when four or more vCPUs are configured. |
Info | ||
---|---|---|
| ||
An active profile cannot be deleted. |
Warning | ||
---|---|---|
| ||
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. |
For SBC SWe cloud-based deployments, the profiles are automatically configured based on the personality. Auto-configuring a profile prevents reboot reboot during instantiation.
The following table represents the SBC SWe automatic configuration:
Personality Type | Profile Name |
---|---|
I-SBC | default |
S-SBC | standard_signaling_profile |
M-SBC | standard_msbc_profile |
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 |
The following table lists and describes the standard profiles.
Profile | Description |
---|---|
default | By 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_profile | This profile utilizes the vCPUs for signaling (direct media) calls, and |
is auto-configured on cloud-based S-SBC instances. | |
standard_transcoding_profile | This profile utilizes the vCPUs for transcoding calls. |
standard_highcps_callmix_profile | This profile is similar to the standard passthrough profile, but with higher CPS. |
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 | ||
---|---|---|
| ||
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. |