Page History

New CLI in

6.

2.

2R0

SBX-

The SBC is enhanced in this release to configure up to three RADIUS servers per SBC with the addition of radiusServer and retryCriteria parameters to radiusAuthentication configuration object.

58171 DISA (Federal Govt) requires stronger radius authentication like CHAP or EAP

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:

% set oam radiusAuthentication 
    radiusServer <server<serverName> name>
authenticationMethod <pap | peapmschapv2>

SBX-68514 Duplicated autoIndex is Generated

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.

% set system admin <system mgmtInterfaceGroupname> <string>
verifyAutoIndex <false | true>

New CLI in 6.2.1R0

SBX-25205 SRTP to RTP Fallback on Receipt of 488

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.

% set profiles services retryProfile priority<retryProfile <#>name>
  attemptRecordGeneration <[disabled]     radiusNasIp <default=0.0.0.0>| enabled>
  state <[disabled]     radiusServerIp <x.x.x.x>| enabled>
        radiusServerPort <#>triggerActionRule <1-16>
       sipResponseCode radiusSharedSecret <8<300-128>699>
        state <[disabled] | enabled>sipWarningCode <300-399>
    retryCriteria
        oosDuration <# minutes>action <1-16>
        retryCount <1-[3]>
     actionType <fallBackSrtpToRtp | retryTimerfallBackToIPV4 <500-3000 milliseconds, default=1000> | fallBackToIPV6>

SBX-

The flag allowPassthru is added to secureRtpRtcp of Packet Service Profile.

% set profiles media packetServiceProfile <packetServiceProfile_name> secureRtpRtcp flags allowPassthru <[disable] | enable> 

SBX-4552 DNS SRV pathCheck Enhancement

 The default value of hostPort configuration under ipPeer pathCheck is updated to 5060.

% set addressContext <addressContext name> zone <zone name> ipPeer <IP peer name> pathCheck hostPort <0-65535, default=5060>

SBX-23345 Transcoder Free Transparency Support for JITC

The following new flags are introduced in Packet Service Profile to configure this feature:

• audioTransparency
  • unknownCodecBitRate

  • unknownCodecPacketSize

• reserveBwForPreferredAudioCommonCodec

% set profiles media packetServiceProfile <packetServiceProfile_name> audioTransparency
	unknownCodecBitRate <1-1000 KB/s, default=124>
	unknownCodecPacketSize <5-100 ms, default=10> 
   
% set profiles media packetServiceProfile <packetServiceProfile_name> flags reserveBwForPreferredAudioCommonCodec <[disable] | enable>

SBX-25296: SBC5K SIP Response Enhancement When IPTG is OOS

The flag processSGConfigWhenTGOOS is added to SIP Trunk Group object to support this feature. 

% set addressContext default zone <zonename> sipTrunkGroup <Trunkgroup name> processSGConfigWhenTGOOS <[disabled] | enabled> 

SBX-26140: Video Bandwidth SDP Handling Improvements and Enhanced Statistics

The following CLI changes made to implement this feature:

The description of Packet Service Profile's maxVideoBandwith and videoBandwidthReductionFactor are modified to:

• maxVideoBandwith: Specifies the maximum session bandwidth that can be used for a call with video streams. It Includes the bandwidth for all streams in the call (audio, video, BFCP, and so on). If "0" is the value, video calls are not allowed and only audio calls can be set up which follows the normal allocation process. The value ranges from 0 to 50000 kbps and the default value is 10 kbps.
• videoBandwidthReductionFactor: Specifies the amount to reduce the session bandwidth allocation for the calls that include video streams. This does not affect the signaling, but affects only the internal allocation of bandwidth used for the calls. The value of this flag is on percentage reduction factor. For example: If the value of this flag is 20, the allocation of bandwidth for the calls is reduced by 20%. So, if the normal bandwidth allocation for calls is 1000 kbps, it gets reduced to 800 kbps.

Two new statistics, ingressSessionBandwidthkbps and egressSessionBandwidthkbps, are added to callDetailStatus object to display the allocated session bandwidth on each leg.

54065 and SBX-35444 SWe Capacity Improvement and Estimation

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:

% set system sweTrafficProfiles <profile name> accessScenario true callHoldTime 125 passthroughCodecProfile cmix1 transcodePercent 30 transcodingCodecProfile G711_G729_20ms

SBX-67540 Change the flag name for lastProvResponse to lastReceivedSdp for the forking scenarios

% 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

SBX-61136 Add 1:1 HA option support for AWS and non D-SBC Cloud

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:

• The parameter mgmtMode is added to system. This parameter specifies whether the instances are managed either manually, or through EMS/VNFM. There are two supported modes:
  • centralized (default)
  • distributed
• The 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.

> show table system admin <system name> mgmtMode

New CLI in 6.2.0R0

SBX-30086 SBC7K/5K sharedCacLimitsPool Enhancement to Encompass Gateway Trunk Group

The SBC in enhanced with the following CLI to support Gateway CAC functionality. 

% 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

SBX-43651 SBC Supports Pushing Audit Records to Remote Server Using rsyslog.conf File

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.

% 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

SBX-44333 SIPREC Forking to two Recorders

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:

The parameter recorderAddress is added to stopRecord.

> request global siprec
    startRecord
        callLeg
 

> show status global callDetailStatus
callDetailStatus 524288 {
    mediaStreams                        audio,video;
    state                               Stable;
    callingNumber           egress
            6033317777;ingress
    calledNumber    gcid <0-2147483647>
        numOfStreams
        srsIpAddress <SRS IP 9811587876;ADDRESS>
    addressTransPerformed    srsIpAddress2
        srsPort <IP port none;
    origCalledNumnumber>
        srsPort2 <Ip port number>
        transport <tcp | udp>
        transport2  <tcp | "";udp>
    scenarioType    trunkGroup <TRUNK GROUP NAME>
        trunkGroup2
    stopRecord
         SIP_TO_SIP;gcid <0-2147483647>
    callDuration    recorderAddress
        recorderPort

Additionally, the srsGroupProfile is added to the global servers object.

% 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> 

SBX-45806 Pathcheck Ping using ICMP

The SBC is enhanced with the following configurations in support of Pathcheck ping enhancements:

• The Path Check Path configuration is added to the System object.
• The parameter, replyTimeout, is added to the pathCheckProfile configuration.

% set system pathCheckPath <Path Check Path 524288;name>
    associatedGcid2addressContext <addressContext name>
    ipInterface <IP Interface name>
    ipInterfaceGroup <IPIG name>
    pathCheckProfile <Patch Check Profile 524288;name>
    associatedGcidLegId1   reportSignalIpAddress <IP address>
    reportSignalIpPort <Port Id>
    sourceIpAddress <Ip address>
    state <[disabled] | 1;enabled>
    associatedGcidLegId2targetIpAddress <IP address>
    zone <Zone name>
 
% set profiles services pathCheckProfile <profile name>
    0;
    ingressSessionBandwidthkbps  failureResponseCodes <400-699 | all |all4xx | all5xx | all6xx>
    protocol <icmp | 525;sipOptions>
    recoveryCount egressSessionBandwidthkbps<1-10>
    replyTimeoutCount <1-10>
    sendInterval 525;
    ...

SBX-28540: TCP Connection Cleanup When Registration Becomes Inactive

The SIP trunk group flag clearTcpConnectionsforRegistration is added to allow the SBC to clear the TCP connection between UE and SBC once the registration becomes inactive.

<1-600>
    transportPreference <preference1 | preference2 | preference3 | preference4>

SBX-46173 CLI Implementations Improvements

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 

% 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]>

% set system policyServer globalConfig dnsGroup <dnsGroupServer_name>

SBX-54065 and SBX-35444 SWe Capacity Improvement and Estimation - Phase 1

The SBC is enhanced with the addition of the following  configuration and status commands in support of SBC SWe capacity improvements.

% 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

SBX-54575 Remove Direct Log Access from sftproot

The SBC is enhanced with the addition of the following flag sftpadminLoginEnabled to the Account Management object to enable or disable the sftpadmin user.

% set system admin <admin-name> accountManagement sftpadminLoginEnabled <false | [true]>

SBX-56559 Alert-Info and P-Early Media Headers Interworking

The SBC is enhanced with the addition of the following SIP Trunk Group flags:

% set addressContext <addressContext name> zone <zone name> sipTrunkGroup sipTrunkGroup name> signaling
      aiToPemInterworking <[disabled] | enabled>
      convertAlertToProgress

The flag gr317ChargeNumberCompliance is added to the ISUP Signaling Profile configuration to check the charge number digit length is in compliance with GR317 which specifies a maximum of 10 digits in IAM message.

% set profiles signaling isupSignalingProfile <profile name> gr317ChargeNumberCompliance <supported | [unsupported]>

SBX-29116 Supported/Require/Allow Transparency Profile

The SIP Param Filter Profile is added in this release to allow the operator to create a profile defining a set of SIP header tags and methods to transparently pass or block, and then assign that profile to a trunk group. The SIP headers configured in this profile for pass-through are transparently passed to the Egress trunk group if received in the Ingress SIP message.

% set profiles services sipParamFilterProfile <profile name>
    action 
        block <all, or comma-separated list of tags/methods to include>
        passthru <all, or comma-separated list of tags/methods to include>
        rejectRequest <[disabled] | enabled>  (flag is applicable to sipHeader 'require' only)
    sipHeader <[allow] | require | supported>
    state <[disabled] | enabled>

Deprecated CLI

No CLI objects or statistics were deprecated in this release.

SBX-58385 SMM Switch Semantics

The SBC is enhanced with the addition of the switch parameter  to the sipAdaptorProfile. 

% set profiles signaling sipAdaptorProfile <name> rule <Index> criterion <Index> switch <Index>
	switchAction <1-128>
	switchValue <value>
	switchRegexpString <regular expression>

Deprecated CLI

revertSoftwareUpgrade

commitSoftwareUpgrade

The Service Capacity License, referred as the "SBC-CAPACITY" license, allows the count-based features to use the full capacity of the SBC.