Panel | ||||
---|---|---|---|---|
In this section:
|
Noprint | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
Default values are enclosed in square brackets [ ]. |
PEAP/MSCHAPv2 is a new method of authentication added to the RadiusAuthentication functionality. This allows a more secure authentication where the radius password is sent using encryption (PEAP) and authenticated via the Microsoft Challenge Handshake Authentication Protocol (MSHAPv2). A CLI command has been added to set the Radius authentication method:
Code Block |
---|
% set oam radiusAuthentication radiusServer <serverName> authenticationMethod <pap | peapmschapv2> |
This feature adds the verifyAutoIndex
configuration parameter. The verifyAutoIndex
configuration parameter checks new entries added to an SBX configuration table that has an Auto Index column to make sure that the newly assigned Auto Index value does not already exist in that table. This configuration parameter is in the admin object of the system-level configuration.
Code Block |
---|
% set system admin <system name> verifyAutoIndex <false | true> |
A new profile retryProfile
is added to the profiles object to configure a trigger/action rule to specify that when a particular response code (and optional warning code) is received (the trigger), the SBC performs a fallback action (fallback SRTP to RTP, fallback to IPV4 or fallback to IPV6). The SBC then reattempts an INVITE with the updated Session Description Protocol (SDP) offer based on the action configured for the received error response and warning code.
Code Block |
---|
% set profiles services retryProfile <retryProfile name>
attemptRecordGeneration <[disabled] | enabled>
state <[disabled] | enabled>
triggerActionRule <1-16>
sipResponseCode <300-699>
sipWarningCode <300-399>
action <1-16>
actionType <fallBackSrtpToRtp | fallBackToIPV4 | fallBackToIPV6> |
The performance of the SBC VM can be optimized by providing the call mix while configuring the SBC SWe instance. The SBC includes a set of predefined call mixes also known as standard traffic profiles. Additionally, a user can create custom traffic profiles containing a call mix that is more appropriate for the SBC SWe.
The following system profiles are added/updated in this release:
SWe Profile | Description | Change |
---|---|---|
sweTrafficProfiles | Profile configuration of all the standard and custom profiles and their respective call mix. | New SWe profile. |
sweActiveProfile | Profile configuration of the name of active profile and time-stamp of activation. | New standard profile added to the existing configuration at SWe Active Profile - CLI:
|
sweCodecMixProfile | The standard and custom codec mix profile configuration. | New SWe profile. |
Code Block |
---|
% set system sweTrafficProfiles <profile name> accessScenario true callHoldTime 125 passthroughCodecProfile cmix1 transcodePercent 30 transcodingCodecProfile G711_G729_20ms |
Code Block |
---|
% set addressContext <name> zone <name> sipTrunkGroup <name> media earlyMedia
forkingBehaviour <firstProvResponse | firstRtp | lastReceivedSdp | pemPriority>
method
pEarlyMedia
defaultGatingMethod <inactive | recvonly | sendonly | sendrecv>
egressSupport <disabled | enabled>
rtpServerTable rtpServerTableName
sessionAnswer |
Hide | |||
---|---|---|---|
Removed feature based on feedback from Shambhu: SBX-60738 Capacity License for Network Wide LicensesSeveral licenses of the SBC are "count-based;" the features dependent on those licenses (known as count-based features) can scale only up to the count permitted by the available number of corresponding licenses. The Service Capacity License, referred as the "SBC-CAPACITY" license, allows the count-based features to use the full capacity of the SBC. The following changes are made to the SBC CLI:
To configure
To display the table for
To display the table for
|
The parameter mgmtMode
is added to the system admin status
command in this release, and specifies whether SBC SWe instances are managed manually or through EMS/VNFM.
Two modes for managing the HA/Redundancy of SBC SWe Cloud Network Functions Virtualization (NFV) are supported:
Centralized (default) - Use this mode for traditional HA/redundancy model (1:1 scenario) where one active instance is backed up by one standby instance. In Centralized mode, the SBC configuration is synchronized between active and standby SBCs. The Centralized mode is preferred for deployments where the scale/sessions requirements are low.
Distributed - Use this mode for SBC SWe Cloud deployments where up to N active SBC instances are backed up by a single standby SBC instance (N:1). In this mode, each node is configured separately, and the configuration on active and standby instances are not synchronized.
The changes in CLI are:
mgmtMode
is added to system. This parameter specifies whether the instances are managed either manually, or through EMS/VNFM. There are two supported modes:rgstatus, serverStatus
, and serverAdmin
commands are supported on AWS for 1:1 redundancy group. For centralized mode, the commands display details of both active and standby volumes.
Code Block |
---|
> show table system admin <system name> mgmtMode |
The SBC in enhanced with the following CLI to support Gateway CAC functionality.
Code Block |
---|
% set addressContext <address_context_name> zone <zone_name> gwTrunkGroup <gateway_trunk_group_name> parentSharedCacLimitsPoolName <shared_Cac_limits_pool_name>
% set addressContext <name> zone <name> gwTrunkGroup <name> cac
bandwidthLimit <0-2147483647>
callLimit <0-2147483647>
egress
emergencyOversubscription <0-1000>
hpcOversubscription <0-100>
ingress |
The SBC is enhanced with the following CLI in support of configuring a remote server IP address, port, and protocol type to push the audit logs to the remote server.
Code Block |
---|
% set oam eventLog platformAuditLogs auditLogRemoteHost <IPv4/IPv6 address>
% set oam eventLog platformAuditLogs auditLogPort <1 to 65535>
% set oam eventLog platformAuditLogs auditLogProtocolType <relp | [tcp] | udp>
> show table oam eventLog platformAuditLogs |
The SBC is enhanced with the following CLI in support of SIPREC on multiple recorders.
The following parameters are added to startRecord
of SIPREC object:
numOfStreams
srsIpAddress2
srsPort2
trunkGroup2
transport2
The parameter recorderAddress
is added to stopRecord
.
Code Block |
---|
> request global siprec
startRecord
callLeg
egress
ingress
gcid <0-2147483647>
numOfStreams
srsIpAddress <SRS IP ADDRESS>
srsIpAddress2
srsPort <IP port number>
srsPort2 <Ip port number>
transport <tcp | udp>
transport2 <tcp | udp>
trunkGroup <TRUNK GROUP NAME>
trunkGroup2
stopRecord
gcid <0-2147483647>
recorderAddress
recorderPort |
Additionally, the srsGroupProfile
is added to the global servers object.
Code Block |
---|
% set global servers srsGroupProfile <profile name>
description <0-199 characters>
loadDistribution <roundRobin | sequence>
numSimultaneousStream <1-2>
srsGroupData <0-7>
ipAddress <IP address>
ipPort <IP port>
ipTGId <IP TG Id>
transport <tcp | udp> |
The SBC is enhanced with the following configurations in support of Pathcheck ping enhancements:
replyTimeout
, is added to the pathCheckProfile configuration.Code Block |
---|
% set system pathCheckPath <Path Check Path name>
addressContext <addressContext name>
ipInterface <IP Interface name>
ipInterfaceGroup <IPIG name>
pathCheckProfile <Patch Check Profile name>
reportSignalIpAddress <IP address>
reportSignalIpPort <Port Id>
sourceIpAddress <Ip address>
state <[disabled] | enabled>
targetIpAddress <IP address>
zone <Zone name>
% set profiles services pathCheckProfile <profile name>
failureResponseCodes <400-699 | all |all4xx | all5xx | all6xx>
protocol <icmp | sipOptions>
recoveryCount <1-10>
replyTimeoutCount <1-10>
sendInterval <1-600>
transportPreference <preference1 | preference2 | preference3 | preference4> |
The SBC is enhanced to populate the encapsulated Integrated Service Digital Network User Part (ISUP) calling party even when it is not mapped to P-Asserted_ID in the INPUT DATA that is sent to the PSX. In support of this, the following flags are added to the SIP Trunk Group Signaling object.
mapFromHeaderToIsupGap
mapIsupCgpnToPAI
Code Block |
---|
% set addressContext <name> zone <name> sipTrunkGroup <name> signaling callingParty
cpcParamFromHeader <[default] | fromheader | paitel>
fromHdrForCallingParty <disabled | [enabled]>
mapFromHeaderToIsupGAP <[disabled] | enabled>
mapIsupCgpnToPAI <[disabled] | enabled>
paiForCallingParty <disabled | [enabled]>
ppiForCallingParty <disabled | [enabled]>
rpiForCallingParty <disabled | [enabled]>
trustedSourceForIsup <disabled | [enabled]> |
The parameter dnsGroup
is added under System > Policy Server > Global Config to allow a DNS Group associate with the global configuration of the policy server. This allows the PSX FQDN resolution with a particular DNS Group.
Code Block |
---|
% set system policyServer globalConfig dnsGroup <dnsGroupServer_name> |
The SBC is enhanced with the addition of the following configuration and status commands in support of SBC SWe capacity improvements.
Code Block |
---|
% set system sweActiveProfile name <profile name>
default
standard_callmix_profile
standard_msbc_profile
standard_passthrough_profile
standard_signaling_profile
standard_transcoding_profile
> show table system sweTrafficProfiles
> show table system sweActiveProfile
> show table system sweCodecMixProfile
> show table system sweProcessorCapacity
> show table system sweCapacityEstimate |
The SBC is enhanced with the addition of the following flag sftpadminLoginEnabled
to the Account Management object to enable or disable the sftpadmin
user.
Code Block |
---|
% set system admin <admin-name> accountManagement sftpadminLoginEnabled <false | [true]> |
The SBC is enhanced with the addition of the following SIP Trunk Group flags:
Code Block |
---|
% set addressContext <addressContext name> zone <zone name> sipTrunkGroup sipTrunkGroup name> signaling
aiToPemInterworking <[disabled] | enabled>
convertAlertToProgress <[disabled] | enabled> |
The SBC is enhanced with the addition of the switch
parameter to the sipAdaptorProfile
.
Code Block |
---|
% set profiles signaling sipAdaptorProfile <name> rule <Index> criterion <Index> switch <Index>
switchAction <1-128>
switchValue <value>
switchRegexpString <regular expression> |
The following command is enhanced to include Metavar Data and Call/Registration data.
Code Block |
---|
> show status/table system standbySyncStatus |
This feature pertains to providing the existing
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
This feature includes the following additions.
Added toneCodecEntry to Media profile to define the unique identifier for the codec entry for this profile.
Code Block |
---|
% set profiles media toneCodecEntry <toneCodecEntry name>
codec <amrwbBandwidthEfficient | evrc | evrc0 | evrcb | evrcb0 | g711>
law <ALaw | ULaw>
codingRate <AMR-0-6.6 | AMR-1-8.85 | AMR-2-12.65 | AMR-3-14.25 | AMR-4-15.85 | AMR-5-18.25 | AMR-6-19.85 | AMR-7-23.05 | AMR-8-23.85> |
A Tones as Announcements profile is added to configure the announcement file to play Local Ringback Tone (LRBT) for each codec entry:
Code Block |
---|
% set profiles media toneAsAnnouncementProfile
toneType <defBusy | defCallWaiting1 | defCallWaiting2 | defCallWaiting3 | defCallWaiting4 | defCpeAlerting | defDial | defReorder | defRing | defSit1 | defSit2 | defSit3 | fccBusy | fccDial | fccRingback>
codecType <The name of the codec entry>
segmentId <unsignedShort> |
The flag announcementBasedTones flag is added to Tones and Announcements profile to generate ringback tones without using DSP resources.
Code Block |
---|
% set profiles media toneAndAnnouncementProfile <toneAndAnnouncementProfile name> localRingBackTone signalingTonePackageState enable flags announcementBasedTones <disable | enable> |
The IP Interface Group parameter, ipVar, is added to the Policy Server globalConfig to specify a metavarible name (from the PSX’s metavariable table) used to provide an IP address for the SBC SWe Cloud for connecting to the PSX.
Code Block |
---|
% set system policyServer globalConfig type <ip | mgmt> addressContext <addressContext> ipInterfaceGroup <ipInterfaceGroup_name> ipVar <IP Variable Name> |
The SBC is enhanced to support configuring intra-cluster VNFC communication interfaces for the Load Balancing Service using the clusterAdmin configuration.The CLI syntax for non-Cloud and Cloud configurations is shown below. The parameters that display are dependent upon the clusterComm type
setting: ip
or mgmt
.
Code Block | ||
---|---|---|
| ||
% set system clusterAdmin clusterComm
addressContext <addressContext name>
pktIpAddress
type <ip |mgmt> |
Code Block | ||
---|---|---|
| ||
% set system clusterAdmin clusterComm
mgmtInterfaceGroup mgmtGroup
mgmtIpAddress <IP address>
type <ip | mgmt> |
Code Block | ||
---|---|---|
| ||
% set system clusterAdmin clusterComm
addressContext <addressContext name>
ipInterfaceGroup <IPIG name>
pktIpVar <metaVariable>
type <ip |mgmt> |
Code Block | ||
---|---|---|
| ||
% set system clusterAdmin clusterComm
mgmtInterfaceGroup mgmtGroup
mgmtIpVar <metaVariable>
type <ip | mgmt> |
The SBC is enhanced to use different IP interface groups for signaling and media interception with the LI CDC configuration field mediaIpInterfaceGroupName
. Additionally, the SBC is enhanced to support the following TCP parameters to configure IMS LI:
kaTime
kaInterval
kaProbe
Code Block |
---|
% set addressContext <default> intercept callDataChannel <callDataChannel_name> mediaIpInterfaceGroupName <IP interface group name>
% set addressContext <addressContext name> intercept callDataChannel <CDC name> mediationServer <mediationServer name> media tcp
kaInterval <5-60 seconds>
kaProbe <4-8 seconds>
kaTime <60-7200 seconds> |
This feature implements several CLI changes in support of
Spacevars | ||
---|---|---|
|
To configure the license mode:
Code Block |
---|
% set system licenseMode mode < legacy | local | network> |
To specify the licenses the
application requests when network licensing mode is active: Spacevars 0 product3
Code Block |
---|
% set system licenseRequired
Possible completions:
DSP-AMRNB DSP-AMRWB DSP-EVRC DSP-G722 ENCRYPT POL-BASE SBC-1X10GMP SBC-4X1GMP SBC-LI SBC-MRF-RTU
SBC-MSRP SBC-NICEREC SBC-POL-E911 SBC-POL-ENUM SBC-POL-RTU SBC-PSX-RTU SBC-RTU SBC-SIP-I SBC-SIP323 SBC-SIPREC
SBC-VIDEO SRTP SWE-INSTANCE VDSP-RTU |
To load the license file:
Code Block |
---|
> request system admin vsbcSystem license loadLicenseFile fileName sonus.xml bundleName b2
This command will load the license file kept in /opt/sonus/external path. Do you want to continue? [yes,no] yes
result success
reason Successfully loaded license file |
To view License Local Bundle Information:
Code Block |
---|
> show table system licenseLocalBundleInfo
ACTIVE
BUNDLE LICENSE PURCHASE LINE EXPIRATION USAGE FINGER LICENSE
NAME FEATURE NAME ID ORDER ID ID GENERATION DATE INSTALL DATE DATE LIMIT FINGER PRINT1 PRINT2 MODE
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
b2 SBC-PSX-RTU 53780 723780 15013476549240 2017-07-29T12:00:54.0+0000 2017-08-07T04:37:38-00:00 2018-01-25Z 100 2000-*1XH6J753HC8RUL8 Local |
To view License Server details:
Code Block |
---|
> show table system licenseServer
SERVER
NAME PRIORITY SERVER ADDRESS
---------------------------------------------------------
SLS 1 fd00:0010:6b50:4d20:0000:0000:0000:0079 |
To view License Server statistics details:
Code Block |
---|
> show table system licenseServerStatus
LICENSE
LICENSE PARTIAL LICENSE
IS REQUEST GRANT GRANT REJECT
SERVER CURRENT MESSAGES MESSAGES MESSAGES MESSAGES LICENSE
NAME ACTIVE SENT RECEIVED RECEIVED RECEIVED ERRORS
------------------------------------------------------------------
SLS y 2177 18 0 0 4318 |
To view license details:
Code Block |
---|
> show table system licenseInfo
LICENSE USAGE IN
FEATURE NAME ID EXPIRATION DATE LIMIT SOURCE USE
--------------------------------------------------------------
SBC-PSX-RTU 0000 2017-12-12-05:00 10 Network 0 |
Caption | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||
|
Pagebreak |
---|
The Service Capacity License, referred as the "SBC-CAPACITY" license, allows the count-based features to use the full capacity of the SBC.