Noprint | |
---|---|
Panel | |
borderColor | green | bgColor | transparent
borderWidth | 2 |
In this section:
|
Noprint | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
Default values are enclosed in square brackets [ ]. |
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.
Code Block | ||
---|---|---|
| ||
% set oam radiusAuthentication
radiusServer <server name>
mgmtInterfaceGroup <string>
priority <#>
radiusNasIp <default=0.0.0.0>
radiusServerIp <x.x.x.x>
radiusServerPort <#>
radiusSharedSecret <8-128>
state <[disabled] | enabled>
retryCriteria
oosDuration <# minutes>
retryCount <1-[3]>
retryTimer <500-3000 milliseconds, default=1000> |
The flag allowPassthru
is added to secureRtpRtcp
of Packet Service Profile.
Code Block | ||
---|---|---|
| ||
% set profiles media packetServiceProfile <packetServiceProfile_name> secureRtpRtcp flags allowPassthru <[disable] | enable> |
The default value of hostPort
configuration under ipPeer pathCheck
is updated to 5060.
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext name> zone <zone name> ipPeer <IP peer name> pathCheck hostPort <0-65535, default=5060> |
The following new flags are introduced in Packet Service Profile to configure this feature:
audioTransparency
unknownCodecBitRate
unknownCodecPacketSize
reserveBwForPreferredAudioCommonCodec
Code Block | ||
---|---|---|
| ||
% 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> |
The flag processSGConfigWhenTGOOS
is added to SIP Trunk Group object to support this feature.
Code Block | ||
---|---|---|
| ||
% set addressContext default zone <zonename> sipTrunkGroup <Trunkgroup name> processSGConfigWhenTGOOS <[disabled] | enabled> |
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.
Code Block | ||
---|---|---|
| ||
> show status global callDetailStatus
callDetailStatus 524288 {
mediaStreams audio,video;
state Stable;
callingNumber 6033317777;
calledNumber 9811587876;
addressTransPerformed none;
origCalledNum "";
scenarioType SIP_TO_SIP;
callDuration 7;
mediaType passthru;
associatedGcid1 524288;
associatedGcid2 524288;
associatedGcidLegId1 1;
associatedGcidLegId2 0;
ingressSessionBandwidthkbps 525;
egressSessionBandwidthkbps 525;
... |
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.
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext name> zone <zone Name> sipTrunkGroup <TG name> signaling clearTcpConnectionsforRegistration <[disabled] | enabled> |
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.
Code Block | ||
---|---|---|
| ||
% set profiles signaling isupSignalingProfile <profile name> gr317ChargeNumberCompliance <supported | [unsupported]> |
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.
Code Block | ||
---|---|---|
| ||
% 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> |
The parameter iceKeepaliveTimer
is added to NAT Traversal of SIP Trunk Group to extend the existing implementation of full-ICE. This enhancement allows the SBC to inter-operate with other ICE peers which require the connecting peer to act as a full-ICE agent.
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext name> zone <zone name> sipTrunkGroup <sipTrunkGroup name> services natTraversal iceSupport iceFull iceKeepaliveTimer <0 to 60 secs, default=15> |
The following flags and attribute are added are added to enhance DTLS-SRTP support and allow a relay mechanism that transparently passes the DTLS, SRTP and SRTCP packets end-to-end without DTLS certification or SRTP cryptographic encryption and decryption taking place at SBC.
New DTLS flags:
dtlsSrtpRelay
dtlsSctpRelay
New QOS Values attribute:
dtlsSctpDscp
Code Block | ||
---|---|---|
| ||
% set profiles media packetServiceProfile <profile_name> dtls dtlsFlags dtlsSrtpRelay <[disable] | enable>
% set profiles media packetServiceProfile <profile_name> dtls dtlsFlags dtlsSctpRelay <[disable] | enable>
% set profiles media packetServiceProfile <profile_name> qosValues dtlsSctpDscp <[0]-255> |
The flag, ednsSupport
, is added to dnsGroup
object to support Extension mechanisms for Domain Name Systems (EDNS) for statically configured and dynamically learned DNS servers.
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext_Name> dnsGroup <dnsGroup_Name> ednsSupport <[disabled] | enabled> |
Additionally, two statistics, ednsStatus
and ednsFailures,
are added to dnsServerStatistics
object to display the current status of DNS server and the number of EDNS failed queries.
Code Block | ||
---|---|---|
| ||
> show table addressContext addr_1 dnsGroup DNSGrp1 dnsServerStatistics
TCP TCP
TOTAL TCP CONNECTION CONNECTION TCP TCP EDNS EDNS
INDEX IP ADDRESS QUERIES TIMEOUTS ERRORS REFERRALS CONNECTION FAILED SUCCESS CONNECTIONTORNDOWN FALLBACK STATUS FAILURES
-------------------------------------------------------------------------------------------------------------------------------------------------
1 10.11.12.13 2 0 0 0 0 0 0 0 0 supported 0 |
Several SMM enhancements are included in this release.
The following IPSP parameters are added in support of quick re-registration on an alternate SIP server when the primary server is down :
The registrarRecovery parameter is added to IPSP commonIpAttributes object, and includes following flags:
The SIP Trunk Group queryPsxOnNextRefreshRegister request command is added with the following options:
Code Block | ||
---|---|---|
| ||
% set profiles signaling ipSignalingProfile <IpSignalingProfile Name> commonIpAttributes registrarRecovery
Possible completions:
registerToAlternateOnPrimaryDown - Register to Alternate on Primary Down.
overrideInternalExpiresTimer - Override Internal Expires Timers.
revertToPrimaryOnRecovery - Revert to Primary Registrar on Recovery.
deRegisterAlternateOnPrimaryRecovery - Deregister Alternate On Primary Registrar Recovery. |
Code Block | ||
---|---|---|
| ||
% request addressContext <addressContextName> zone <zoneName> sipTrunkGroup <sipTrunkGroupName> cmds queryPsxOnNextRefreshRegister
Possible completions:
newRegistrarIndex - Route index to attempt after force PSX query.
overRideInternalExpires - Over-ride SBX intenal expires timer.
registrarFqdn - Command applies only for registrations towards this REGISTRAR: FQDN.
registrarIpAddress - Command applies only for registrations towards this REGISTRAR: IP Address. |
The SBC is enhanced to support various flavors of LI and a generic Call Data Channel (CDC) model to support any new flavors of LI.
The following parameters are added under CDC object:
interceptStandard
vendorId
mediationServer
media
tcp
udp
signaling
dscpValue
ipAddress
portNumber
state
mode
protocolType
rtcpInterception
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext name> intercept callDataChannel (CDC name)
interceptStandard < etsi | [packetcable] | threeGpp>
vendorId <[none] | ss8 | utimaco | verint>
mediationServer <mediationServer name, 1-8 characters>
media <tcp | udp>
signaling
dscpValue <0-63, default=16>
ipAddress <IPv4/IPv6 address>
mode <inService | [outOfService]>
portNumber <[0]-65535>
protocolType <[tcp] | udp>
state <[disabled] | enabled>
rtcpInterception <[disabled] | enabled> |
The SBC is enhanced to allow a percentage of sessions beyond the purchased session license capacity to measure the maximum amount of simultaneously active and stable sessions over a configurable time interval.
Two statistics, callCountCurrentStatistics
and callCountIntervalStatistics
are added to the Global object.
Code Block | ||
---|---|---|
| ||
> show table global callCountCurrentStatistics
CALL
NAME COUNT
--------------
entry 0
> show table global callCountIntervalStatistics
INTERVAL CALL
NUMBER NAME VALID TIME COUNT
--------------------------------------
2 entry true 1548 0
3 entry true 2448 0
4 entry true 3348 0
5 entry true 4248 0 |
A new configuration flag, callCountTimeInterval
, is added to intervalStatistics
object.
Code Block | ||
---|---|---|
| ||
% set system intervalStatistics callCountTimeInterval <5-60 minutes, default=15> |
The following parameters are added to the sipTrunkGroup
to allow the SBC to support MS Lync/Skype remote desktop sharing.
lyncShare
iceTcpRole
Code Block | ||
---|---|---|
| ||
% set addressContext <addressCnotext_name> zone <zone_name> sipTrunkGroup <sipTrunkGroup_name> media lyncShare <disabled | [enabled]>
% set addressContext <addressCnotext_name> zone <zone_name> sipTrunkGroup <sipTrunkGroup_name> services natTraversal iceSupport iceLync iceTcpRole <active| [passive]> |
The 'request alarms' command is enhanced with the following options.
The parameter generateRtcpForT140IfNotReceivedFromOtherLeg
is added to packetServiceProfile rtcpOptions rtcp
. When the parameter is set to enable
, the SBC generates RTCP for T140 media streams if RTCP is not received from peer.
For more information, refer to the following pages:
Info | ||||
---|---|---|---|---|
| ||||
To configure this feature, ensure that the
|
To configure the parameter generateRtcpForT140IfNotReceivedFromOtherLeg
, use the following syntax:
Code Block |
---|
set profiles media packetServiceProfile <packetServiceProfile_name: INGRESS>
rtcpOptions
rtcp <disable | enable>
generateRtcpForT140IfNotReceivedFromOtherLeg <disable | enable> |
Caption | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
The SBC is enhanced to support a Public Key-based peer authentication method for IPSec on SBC. In past releases, the SBC used a Preshared key-based authentication method for Peer authentication during IKE negotiation for establishing IKE and IPSec Security associations. To meet Common Criteria certification requirements, the SBC is now capable of using x.509 digital certificates for Peer authentication. Note: Not currently supported on SBC Cloud and D-SBC platforms.
For more information, refer to IPsec Peer - CLI.
Code Block |
---|
% set addressContext default ipsec peer <peerName> authType <psk | rsaSig>
% set addressContext default ipsec peer <peerName> localCertificate <sbcCertName>
% set addressContext default ipsec peer <peerName> remoteCertificate <peerCertName>
% set addressContext default ipsec peer <peerName> remoteCaCertificate <caCertName1> |
Parameter | Default | Description | M/O |
---|---|---|---|
authType | psk | The authentication method – preshared key (psk) or rsa signature (rsaSig). | M |
localCertificate | n/a | The name of local (SBC) Certificate. | M |
remoteCertificate | n/a | The name of remote (IPSec Peer) Certificate. | M |
remoteCaCertificate | n/a | The name of remote CA Certificate referred by the IPSec peer entry. | O |
The SBC is enhanced with the parameter maxNumTransfers
under the object global signaling
.
For more information, refer to Signaling - Global - CLI and Show Table Global.
To configure maxNumTransfers
, use the following syntax:
Code Block |
---|
% set global signaling maxNumTransfers <10-100> |
Caption | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
To configure maxNumTransfers
, use the following example:
Code Block |
---|
% set global signaling maxNumTransfers 30 |
To display the maxNumTransfers
, use the following example:
In the "configure" mode:
Code Block |
---|
% show global signaling maxNumTransfers
maxNumTransfers 30 |
In the "display" mode (when you exit the "configure" mode):
Code Block |
---|
> show table global signaling
maxNumTransfers 30;
messageManipulation {
inputAdapterProfile DD1;
outputAdapterProfile DD1;
}
sipPeerOverloadControl {
samplingPeriod 2;
discardPeriod 2;
stepDownGain 100;
rejectThreshold 1;
}
sipSigControls {
registrarSupportContactParam enabled;
maxPduSizeValue pdusize15kb;
}
|
The SBC is enhanced to support a new parameter "Generate Recording CDR" to the OAM > Accounting > Admin. When the "Generate Recording CDR" parameter is enabled, the SBC generates a Recording-CDR. The selected CDR is placed in the .ACT files along with the other call and Event CDRs. All the file size and CDR count rules of the existing CDRs apply to the Recording CDRs.
For more information, refer to Packet Service Profile - CLI.
Code Block |
---|
% set oam accounting admin generateSipRecordingCdr <disabled | enabled> |
Parameter Name | Default Value | Optional or Required? | Parameter Description |
---|---|---|---|
| disabled | Optional | Enables or disables generation of CDRs for recording SIP calls. |
The ATIS specification defines an optional capability to signal verification failures in backward provisional responses. If a terminating carrier B fails verification for an originating carrier A subscribers, but continues to deliver the call to the carrier B called party, carrier A will have no way to know. The terminating carrier can use failed verification to indicate robocalling status to the called party. In this case, carrier A has no way to know that their subscribers' calls are being flagged as robocalls to the terminating party.
The capability described in the ATIS specification solves this issue if carrier A has tools in place to find these indications in the SIP messaging.
Trunk-group-level SIP cause value reporting should include counts for each unique case value transmitted. These statistics already exist for the Reason header transmitted at the end of the call; however, this would additionally count the cause values send in the 18x/200 for STIR/SHAKEN.
New STI Profile flag overWriteReasonCodeIn4xxto6xx
added regarding 4xx-6xx handling.
For more information, refer to STI Profile - CLI.
Code Block | ||
---|---|---|
| ||
% set profiles services stiProfile <profile_name> overWriteReasonCodeIn4xxto6xx <disabled | enabled> |
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
overWriteReasonCodeIn4xxto6xx | 1 | disabled | This parameter controls whether to Insert Reason Code from PSX or not in case of 4XX/5XX/6XX responses
| O |
A parameter, t140RtcpMonitorInterval
, is added under mediaRTCPControl to define the RTCP monitoring interval. This enables the SBC to wait for an RTCP packet from peer before starting RTCP towards T.140 endpoint with the following PSP flag enabled.
A flag, generateRTCPForT140IfNotReceivedFromOtherLeg,
is added under RTCP Options in the Packet Service Profile so that the SBC is able to configure specific trunk groups to generate RTCP on T.140 to T.140 passthrough media streams. The SBC will start generating RTCP for T.140 stream if RTCP is NOT received from the endpoint.
For more information, refer to Packet Service Profile - CLI and Media System - CLI.
Code Block |
---|
% set system media mediaRtcpControl t140RtcpMonitorInterval 6
% set profiles media packetServiceProfile DEFAULT rtcpOptions generateRtcpForT140IfNotReceivedFromOtherLeg enable |
Div | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
|
Div | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
|
The synchronization source (SSRC) identifier uniquely identifies media streams within an RTP session and is included in SDP signaling when establishing or modifying media sessions. The WebRTC specification requires that the SSRC value in an RTP stream match the SSRC sent in the SDP. However some endpoints, such as PSTN gateways, are not capable of generating SSRC values so they are not present in the SDP. Other endpoints change the SSRC during call hold/resume scenarios. The SBC provides two flag parameters to the Packet Service profile to determine whether the SBC generates and updates the SSRC and related attributes.
For more information, refer to Packet Service Profile - CLI.
The SBC adds the following two flags to the Packet Service profile.
Code Block |
---|
% set profiles media packetServiceProfile <profile name> flags
generateAndSignalSSRCAndCname <disabled | enabled>
allowMidCallSSRCModification <disabled | enabled> |
The SBC only allows mid-call modifications to the SSRC if it is generating the SSRC. Therefore, the first parameter, generateAndSignalSSRCAndCname
, must be enabled for the second parameter, allowMidCallSSRCModification,
to become available.
Parameter | Description |
---|---|
| Enable this flag to generate an SSRC value and associated attributes and include them in SDP signaling and RTP/RTCP streams. Options are:
Note: This flag takes precedence over the Packet Service Profile |
| Enable this flag so that in call hold/resume scenarios the SBC modifies the SSRC and associated attributes after the call resumes. The SBC sends both the previous and updated SSRC in SDP signaling and includes the new SSRC iin RTP/RTCP streams. Options are:
Note: You must enable the Note: If you enable the IP Signaling profile common IP attributes flag |
The rcodeErrorMonitorTimer
parameter is added to the DNSGroup
configuration to support monitoring timer interval which the SBC Core uses to monitor RCODE errors.
For more information, refer to DNS Group - CLI
Code Block |
---|
% set addressContext <address_context_name> dnsGroup <dnsgroup> rcodeErrorMonitorTimer <rcode_error_monitor_timer> |
Caption | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
The SBC is enhanced to allow writing accounting files containing CDRs into a compressed format. The compressed files are retained for a user-specified time period; thereafter, they are automatically deleted after a specified number of days. The compressed files are stored in the evlog
directory or another directory that you specify.
For more information, refer to Event Log - CLI
Code Block | ||
---|---|---|
| ||
% set oam eventLog typeAdmin acct
compressionSupport <both | none | only>
compressionDaysToKeep <1 .. 7>
compressionCleanupDirectory
|
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
compressionSupport | N/A | Type of compression.
| ||
compressionDaysToKeep | 1-7 | 5 | The number of days to keep compressed files before deleting. | |
compressionCleanupDirectory | N/A | N/A | Alternate directory name (containing no slashes) under the log file directory from which compressed files are removed after compressionDaysToKeep days elapse. |
The following is the full syntax to create a SIP ARS profile, including the new recoveryAlgForTimeouts
and recoveryAlgForNoRetryAfter
options and their parameters for selecting the ARS recovery algorithm for each blacklist algorithm.
For more information, refer to SIP ARS Profile - CLI.
Info | ||
---|---|---|
| ||
Ensure the ARS profile is configured with the recovery algorithms specified in the recovery flags. |
Code Block |
---|
set profiles services sipArsProfile <Profile Name> recoveryAlgForTimeouts < probe | timer | none > |
Code Block |
---|
set profiles services sipArsProfile <Profile Name> recoveryAlgForNoRetryAfter < probe | timer | none > |
Code Block | ||
---|---|---|
| ||
% set profiles services sipArsProfile <profile name>
blkListAlgRetryAfterType sip-503
blkListAlgTimeoutsDuration <1-3600>
blkListAlgTimeoutsNumTimeouts <1-3600>
blkListAlgTimeoutsType sip-invite
blkListAlgorithms <retryafter | timeouts | noRetryAfer>
blkListAlgNoRetryAfterNum503 <1-3600>
blkListAlgNoRetryAfterDuration <1-3600>
failureResponseCodes <400-699 | all |all4xx | all5xx | all6xx>
midDialogArsScreenLevel <always | never | onlyIfNotBlackListDueto503>
recoveryAlgProbeDuration <1-3600>
recoveryAlgProbeInterval <1-600>
recoveryAlgProbeMethod sip-options
recoveryAlgProbeNumResponses <1-32>
recoveryAlgTimerDuration <1-3600>
recoveryAlgorithm <probe|timer>
recoveryAlgForTimeouts <probe|timer|none>
recoveryAlgForNoRetryAfter <probe|timer|none>
|
Caption | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
|
Two new parameters are added to SIP trunk group signaling and are shown in the context of the complete command syntax.
performPrecondtionRenegotiation:
to re-initiate precondition procedure when the Spacevars | ||
---|---|---|
|
preferUPDATEOverReINVITE:
to use UPDATE instead of Re-INVITE on the ingress to communicate SDP, when the call goes to the confirmed state.For more information, refer to:
Code Block | ||
---|---|---|
| ||
% set addressContext default zone <zone_name> sipTrunkGroup <siptrunkgroup_name> signaling preferUPDATEOverReINVITE <enabled | disabled>
|
Code Block |
---|
% set addressContext default zone <zone_name> sipTrunkGroup <siptrunkgroup_ingress_name> signaling performPrecondtionRenegotiation
<enabled | disabled>
|
Caption | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
|
Packets that cause a direct SBC fault can lead to a catastrophic failure of an SBC service, which is known as a packet-stimulated fault avalanche. These packets appear for various reasons, such as: the SBC adds a new Session Initiation Protocol (SIP) endpoint, upgrades or replaces a peering endpoint or gateway (GW), changes a configuration on a peer, or introduces a new call scenario. The SBC does not currently check for double faults, which is when the SBC has a failover and then another failover. Double faults cause call loss.
For more information, refer to CLI Configure Mode.
Use the following command to set and configure the faultAvalancheControl
parameter.
Code Block |
---|
% set system faultAvalancheControl callIdThreshold <0-999> calledPartyThreshold <0-999> callingNCalledPartyThreshold <0-999> callingPartyThreshold <0-999> sourceIpThreshold <0-999> faultRecAgeingTimeOut <15-60> |
Use the following command to enable or disable the faultAvalancheControl
parameter.
Code Block |
---|
% set system faultAvalancheControl facState <disabled | enabled> |
Caption | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||
|
In specific call scenarios, the SBC treats the Offer-Answer (OA) as a MODIFY Offer-Answer cycle, but the peer treats it as an INITIAL Offer-Answer cycle. According to RFC 3261, the response from the peer is expected within 300 seconds. The SBC, however, assumes a 20-second response, and therefore any delay in the response from the peer which exceeds of 20 seconds causes call failure.
Currently, the internal Offer-Answer (OA) timer value is fixed and cannot be configured. To overcome this limitation, the SBC is enhanced with a new parameter offerAnswerTimer
to configure this OA timer.
For more information, refer to Signaling - Global - CLI
Code Block |
---|
% set global signaling sipSigControls offerAnswerTimer
Possible completions:
<Enter offer answer timer value in range of (10..300) in seconds.> (20): |
Caption | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
|
The SBC provides the following new SIP trunk group parameter to specify whether to use the Contact header information instead of the source IP address when routing a call to an access user over TLS transport.
For more information, refer to SIP Trunk Group - Signaling - CLI
% set addressContext <address context> zone <zone> sipTrunkGroup <trunk group name> signaling honorContactInRegisterForTLSCalls <disabled | enabled> |
Parameter | Description |
---|---|
| Use this flag to specify where the SBC directs access calls from the internal network to users in the access network when the call is over TLS transport. The options are:
|
When the SBC fails a DNS query, it generates a 503 or 500 error response. These error codes are now mapped to a configurable response code. A new enum - DnsRcodeError - has been added to internalCause
in sonusSipInternalCauseMapProfile
.yang to provide mapping entry in existing InternalSipCauseMapProfile
profile.
For more information, refer to Show Table Global. and Internal SIP Cause Map Profile - CLI.
Code Block |
---|
% set profiles signaling sipCauseCodeMapping internalSipCauseMapProfile <profile_name> causeMap <CPC cause value> DnsRcodeError |
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
dnsRcodeError | 300-606 | N/A | Allows 500 and 503 error code mapping to a configurable response code. | Mandatory |
The SBC adds support for using SIP Message Manipulation (SMM) to enable secondary selection of an ingress trunk group. This processing requires two new SMM operations and SIP Param Based Action profiles.
For more information, refer to SIP Adaptor Profile - CLI.
The following new operations are supported in SMM sipAdaptorProfiles
.
Code Block |
---|
% set profiles signaling sipAdaptorProfile <profileName> rule <rule index> action <action index> operation
storeSipParam
storeProfileName |
The SIP Param Based Action profile is supported.
Code Block | ||
---|---|---|
% set profiles signaling sipParamBasedActionProfile <profileName>
action <none | selectTG>
entry <0 to 2056> | ||
Code Block | ||
| ||
> request alarms current comment alarm trunkGroupName <trunk idgroup <integer>name> matchType text <operator comment> statefull alarm acknowledgeState <acknowledgeparam |<parameter unAcknowledge>value> id <integer> |
The following statistics are added to addressContext sipActiveRegisterNameStatus
table to allow the SBC to search the registration name status based on part of the Address of Record (AOR), plus provides the ability to search the entries which are not in the statistics table but registered in the SBC application using a part of the AOR name or the entire AOR name. :
externalExpirationTimeLeft
internalExpirationTimeLeft
regId
transportProtocolToAS
transportProtocolToEndpoint
In this example, userPart is used as first parameter to retrieve the entry status that is not in the table but registered in the SBC application.
Code Block | ||
---|---|---|
| ||
> show status addressContext default sipActiveRegisterNameStatus 67891 0
state completed;
contactURI sip:67891@10.54.80.101:7070;
nextHopIpAddress 10.54.80.101;
nextHopPortNum 7070;
registrarIpAddress 10.54.19.168;
registrarPortNum 7080;
externalExpirationTime 1800;
internalExpirationTime 3600;
creationTime 2016-01-28T06:39:34+00:00;
registrarDomainName "";
endPointBehindNapt 0;
natPinholeLearningStatus none;
securityMechanismType none;
registrationType normal;
e2aeMediaSecurity none;
isRoaming 0;
transportProtocolToEndpoint udp;
transportProtocolToAS udp;
externalExpirationTimeLeft 1602;
internalExpirationTimeLeft 3052;
regId 9996; |
The SBC is enhanced to support Dialog Stateful variables for Out-of-Dialog SUBSCRIBE messages when advancedSMM is enabled, in addition to INVITE and REGISTER.
Code Block | ||
---|---|---|
| ||
% set profiles signaling sipAdaptorProfile SMM_Test advancedSMM <[disabled] | enabled> |
The SBC is enhanced to provide bandwidth Call Admission Control (CAC) per supported media type by limiting video streams to specified bandwidth limits in order to provide a level of protection from video calls consuming call bandwidth otherwise needed for audio calls. This protection is implemented on SBC Core by setting video thresholds (bandwidthVideoThreshold
) to specific limits at the zone, trunk group, endpoint and shared CAC levels. The thresholds are a percentage of the total bandwidth limit such that any traffic above this level is reserved for audio-only calls. This video threshold limit behaves the same for emergency as well as non-emergency calls. Any video calls above the video threshold limit are dropped to allow audio calls to use this bandwidth.
NOTE: Bandwidth CAC is not available for MSRP, data channels, FECC and BFCP streams.
Code Block | ||
---|---|---|
| ||
set addressContext <addressContext name> zone <zone name> cac bandwidthVideoThreshold <0-100>
set addressContext <addressContext name> zone <zone name> sipTrunkGroup <sip tg name> cac bandwidthVideoThreshold <0-100>
set global cac sharedCacLimitsPool <pool name> bandwidthVideoThreshold <0-100>
set profiles sipCacProfile <profile name> bandwidthVideoThreshold <0-100> |
The following status and statistics commands are added in support of this feature:
Code Block | ||
---|---|---|
| ||
show status addressContext default zone ZONE_AS callFailureCurrentStatistics videoThresholdLimit
show status addressContext default zone ZONE_AS callFailureIntervalStatistics videoThresholdLimit
show status global cac sharedCacFailureCurStats videoThresholdLimit
show status global cac sharedCacFailureIntervalStats videoThresholdLimit
show status addressContext zoneCurrentStatistics videoThresholdLimit
show status addressContext zoneIntervalStatistics videoThresholdLimit
show status addressContext default zone ZONE_IAD sipPeerCacStatus videoThresholdLimit |
The storeICID
flag is added to SIP Trunk Group signaling object to allow the SBC to retain the same ICID value generated during the first egressed INVITE in the P-Charging-Vector header in an egressed INVITE. This flag is configured on the egress trunk group.
Code Block | ||
---|---|---|
| ||
% set addressContext <addressContext_Name> zone <zone_Name> sipTrunkGroup <sipTrunkGroup_Name> signaling storeICID <[disabled] | enabled> |
A new system status command, softwareUpgradeDetailedStatus
, is added to view the detailed upgrade log of the LSWU upgrade process including the number of steps involved, the time taken to complete the upgrade and the results of the upgrade process.
Code Block | ||
---|---|---|
| ||
> show table system softwareUpgradeDetailedStatus <SYSTEM_NAME> detailedStatus |
The following attributes are added to rtcpOptions
of packetServiceProfile
object:
enableRTCPForHeldCalls
rrBandwidth
rsBandwidth
Code Block | ||
---|---|---|
| ||
% set profiles media packetServiceProfile <profile name> rtcpOptions rtcp enable enableRTCPForHeldCalls <[disable] | enable>
% set profiles media packetServiceProfile <profile name> rtcpOptions rtcp enable enableRTCPForHeldCalls enable rrBandwidth <100-4000, default=250>
% set profiles media packetServiceProfile <profile name> rtcpOptions rtcp enable enableRTCPForHeldCalls enable rsBandwidth <100-3000, default=250> |
The flag, initialCodecMode
, is added to the codec
of codecEntry
object. This flag is applicable for AMR and AMR-WB codecs.
Code Block | ||
---|---|---|
| ||
% set profiles media codecEntry <codecEntry object> codec <AMR, AMRWB codec> initialCodecMode <[disable] | enable> |
The flag, sendRTCPBandwidthInfo
, is added to Common Flags
of IP Signaling Profile
object.
Code Block | ||
---|---|---|
| ||
% set profiles signaling ipSignalingProfile <profile name> commonIpAttributes flags sendRTCPBandwidthInfo <[disable] | enable> |
The default value of localAuth user m2mAccess
flag is changed to "enabled
" for Administrator and Calea users (only) to enable SBC REST M2M access by default for these.
Code Block | ||
---|---|---|
| ||
% set oam localAuth user <user name> m2mAccess <disabled | [enabled]> |
The advertiseAudioOnly
is added to SIP trunk group object to allow the SBC to send only the main audio/image stream in the SDP offer for the following LSWU scenarios:
advertiseAudioOnly
flag by default is enabled.advertiseAudioOnly
flag is disabled. You must manually enable the flag if required.advertiseAudioOnly
flag value is retained.
Code Block | ||
---|---|---|
| ||
> set addressContext default <zone_name> sipTrunkGroup <SIP_trunk_group_name> media advertiseAudioOnly <disabled | enabled> |
By default, the SBC reserves the worst case common audio codec bandwidth on trunk groups and IP interfaces for pass-through calls, and polices for the same bandwidth. To facilitate asymmetric pass-through calls scenarios/cases and to police on the heaviest codec in the offer or answer, the PSP flag policeOnHeaviestAudioCodec
is added in this release.
Code Block | ||
---|---|---|
| ||
% set profiles media packetServiceProfile <packet ServiceProfile name> flags policeOnHeaviestAudioCodec <[disable] | enable> |
The setHaConfig
configuration is included in this release to configure SBC for Geographical Redundancy High Availability (GRHA) mode when active and standby servers are located in two different data centers to protect SBCs against data center and network failures. To configure/change just one setting, use currentValue
option for the other setting.
Code Block | ||
---|---|---|
| ||
> request system admin <system name> setHaConfig
bondMonitoring <currentValue | direct-connect | network-connect>
leaderElection <currentValue | enhanced | standard> |
Note |
---|
Bond monitoring is only applicable to SBC 5000/7000 series platforms. This feature is not configurable during software installation nor is it changeable during an upgrade. |
A new object, bruteForceAttackOS
is added to Account Management to configure the number of consecutive failed login attempts to Linux OS, and includes the following parameters:
OSstate
allowOSAutoUnlock
consecutiveFailedOSAttemptAllowed
unlockOSTime
Code Block | ||
---|---|---|
| ||
% set system admin <System_Name> accountManagement bruteForceAttackOS
allowOSAutoUnlock <[disabled] | enabled>
consecutiveFailedOSAttemptAllowed <1-10, default=3>
OSstate <[disabled] | enabled>
unlockOSTime <[30]-5400 seconds> |
The sipCauseMapping
object is added to Egress IP Attributes of the IP Signaling Profile to create Cause Mapping profile names using the following parameters.
sipToInternalCauseMappingProfileName
internalToSipCauseMappingProfileName
Code Block | ||
---|---|---|
| ||
% set profiles signaling ipSignalingProfile <ipSignalingProfile_Name> egressIpAttributes sipCauseMapping sipToInternalCauseMappingProfileName <sipToInternalProfile_Name>
% set profiles signaling ipSignalingProfile <ipSignalingProfile_Name> egressIpAttributes sipCauseMapping internalToSipCauseMappingProfileName <internalToSIPProfile_Name> |
The causeMap object is added to signaling profiles to create profile to map CPC and SIP using the following parameters:
Code Block | ||
---|---|---|
| ||
% set profiles signaling sipCauseCodeMapping sipToCpcCauseMapProfile <sipToCpcCauseMapProfile_Name> baseProfile defaultSipCpc causeMap <causeMap_Value> cpcCause <cpcCause_Value>
% set profiles signaling sipCauseCodeMapping cpcToSipCauseMapProfile <cpcToSipCauseMapProfile_Name> baseProfile defaultCpcSip causeMap <causeMap_Value> sipCause <sipCause_Value> |
No CLI objects or statistics were deprecated in this release.
Hide |
---|
The following CLI objects and statistics are deprecated in this release. |
Historical List of deprecated CLI:
Caption | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
none
range
rangeEnd <end of parameter range>
rangeStart <start of parameter range>
regexp
paramRegexp <regular expression> |
The following table describes the new SMM operations.
Parameter | Description |
---|---|
| SMM operation that extracts a specified value (header, parameter, token) from the incoming SIP message to compare to mapping defined in a |
| SMM operation that stores the name of a sipParamBasedActionProfile to use in selecting a new ingress trunk group. |
The following table describes the parameters in the sipParamBasedActionProfile
.
Parameter | Length/Range | Description |
---|---|---|
| up to 23 characters | Name for the |
| n/a | Action to be performed by the
|
| 0 to 2056 | Index value for the entry. A sipParamBasedActionProfile can contain a maximum of 2056 entries. |
| up to 23 characters | The name of the trunk group to set as the new ingress trunk group if the corresponding entry matches the value extracted with the SMM storeSipParam operation. |
| n/a | Type of matching to use when comparing the value extracted with the SMM
|
| up to 128 characters | Parameter value to compare against when matchType is full . More than one param value can be defined for an entry when matchType is full . |
| up to 128 characters | Ending value for a range to compare against when matchType is range . |
| up to 128 characters | Starting value for a range to compare against when matchType is range . |
| up to 128 characters | Regular expression to compare against when the matchType is regexp . |
The SBC adds support for applying SIP message manipulation (SMM) profiles (SIP adaptor profiles) at both the global and address context levels and options that control how to execute profiles when they are specified at more than one level.
For more information, refer to Signaling - Global - CLI.
The following new options specify the names of SIP adaptor profiles to apply at the global level.
Code Block |
---|
% set global signaling messageManipulation
inputAdapterProfile <profile name>
outputAdapterProfile <profile name> |
The following new options specify the names of SIP adaptor profiles to apply to sessions within a specified address context..
Code Block |
---|
% set addressContext <address context> signaling messageManipulation
inputAdapterProfile <profile name>
outputAdapterProfile <profile name> |
The following new options specify whether or not to use fixed order execution when multiple SMM profiles apply to a session. When fixed order execution is enabled, you can also specify which of the four profile types to enable and therefore include in SMM processing.
Code Block |
---|
% set addressContext <address context> zone <zone> sipTrunkGroup <trunk group name> signaling messageManipulation smmProfileExecution
none
fixedOrder
addressContext acState <disable | enable>
global globalState <disable | enable>
iptg iptgState <disable | enable>
zone zoneState <disable | enable> |
Parameter | Length/Range | Description |
---|---|---|
| 0-23 characters |
|
| 0-23 characters | <profile name> – Enter the name of a SIP adaptor profile to use globally on outbound messages. |
Parameter | Length/Range | Description |
---|---|---|
| 0-23 characters |
|
| 0-23 characters | <profile name> – Enter the name of a SIP adaptor profile to use for the address context on outbound messages. |
Parameter | Description |
---|---|
| Specifies whether or not to use fixed order processing when more than one SIP adaptor profile applies to messages in sessions associated with the specified SIP trunk group. The options are:
|
| Specifies whether the SBC executes the rules in the SIP adaptor profiles assigned at the address context level on messages in sessions associated with the specified SIP trunk group. The options are:
This option is only available after you set |
| Specifies whether the SBC executes the rules in the SIP adaptor profiles assigned at the global level on messages in sessions associated with the specified SIP trunk group. The options are:
This option is only available after you set |
| Specifies whether the SBC executes the rules in the SIP adaptor profiles assigned at the SIP trunk group level on messages in sessions associated with the specified SIP trunk group. The options are:
This option is only available after you set |
| Specifies whether the SBC executes the rules in the SIP adaptor profiles assigned at the zone level on messages in sessions associated with the specified SIP trunk group. The options are:
This option is only available after you set |
A new Services profile, sipAdaptiveTransparencyProfile
, is added to configure SIP header transparency for P-ASSERTED-IDENTITY.
For more information, refer to SIP Adaptive Transparency Profile - CLI.
Under sipAdaptiveTransparencyProfile
, the following parameters are added:
sipMethod
sipResponse
state
triggerHeader
action
trigger
Code Block |
---|
% set profiles services
sipAdaptiveTransparencyProfile <profile_name>
sipMethod <UPDATE | INVITE>
sipResponse <180 | 183 | 200>
state <disabled | enabled>
triggerHeader <P-ASSERTED-ID>
action new-value
trigger value-change |
Info | ||||
---|---|---|---|---|
| ||||
The SIP Method |
Caption | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
The CLI changes are as follows:
profiles signaling
:calledPrefixMatchProfile
carrierCodeToIoiMappingProfile
ioiToCarrierCodeMappingProfile
sipJJ9030InterworkingProfile
profiles signaling NNIProfile
:contractorNumInterworking
addressContext zone sipTrunkGroup signaling
:calledPrefixMatchProfile
sipJJ9030InterworkingProfile
For more information, refer to the following pages:
To configure the signaling profile calledPrefixMatchProfile
, use the following syntax:
Code Block |
---|
% set profiles signaling
calledPrefixMatchProfile <called_prefix_match_profile_name: 1-23 characters>
prefixMatch
<stringPattern: 1-12 digits, 'X' or 'x' characters>
<startPosition: 0-11>
<digitLength: 1-30> |
To configure the signaling profile carrierCodeToIoiMappingProfile
, use the following syntax:
Code Block |
---|
% set profiles signaling
carrierCodeToIoiMappingProfile <carrier_code: 4 digits [0-9]>
accessParam <class | type>
accessValue <access_value_string: 1-64 characters>
ioi <inter_operator_identifier_string: 1-128 characters> |
To configure the signaling profile ioiToCarrierCodeMappingProfile
, use the following syntax:
Code Block |
---|
% set profiles signaling
ioiToCarrierCodeMappingProfile <inter_operator_identifier_string: 1-128 characters>
carrierCode <carrier_code: 4 digits [0-9]> |
To configure the signaling profile sipJJ9030InterworkingProfile
, use the following syntax:
Code Block |
---|
% set profiles signaling
sipJJ9030InterworkingProfile <sip_JJ9030_Interworking_Profile_name: 1-23 characters>
addUserEqualPhoneforDivHiInterworking <disabled | enabled>
bciCalledPartyCategory <noIndication | ordinary | payphone | spare>
bciChargeIndicator <charge | noCharge | noIndication | spare>
bciTerminatingIsdnAccess <isdn | nonIsdn>
chargeAreaInformation <charge_area: 5 digits [0-9]>
origIoi <originating_inter_operator_identifier_string: 1-128 characters>
originatingCarrierCode <originating_carrier_code: 4 digits [0-9]>
setHiPresentationRestricted <disabled | enabled>
sipFlavor
JJ9030
SIP-T
SIP-ttc-charging-params
termIoi <terminating_inter_operator_identifier_string: 1-128 characters> |
To configure the parameter contractorNumInterworking
under the profile NNIProfile
, use the following syntax:
Code Block |
---|
% set profiles signaling NNIProfile <nni_profile_name>
contractorNumInterworking <disabled | enabled> |
To attach the signaling profiles calledPrefixMatchProfile
and sipJJ9030InterworkingProfile
with sipTrunkGroup
, use the following syntax:
Code Block |
---|
% set addressContext <address_context_name> zone <zone_name> sipTrunkGroup <SIP_TG_name> signaling
calledPrefixMatchProfile <called_prefix_match_profile_name>
sipJJ9030InterworkingProfile <sip_JJ9030_interworking_profile_name> |
Tip | ||
---|---|---|
| ||
Create the profiles |
The parameter descriptions for profiles signaling
calledPrefixMatchProfile
are as follows:
Caption | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
The parameter descriptions for profiles signaling carrierCodeToIoiMappingProfile
are as follows:
Caption | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||
|
The parameter descriptions for profiles signaling
are as follows:ioiToCarrierCodeMappingProfile
Caption | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
The parameter descriptions for profiles signaling
are as follows:sipJJ9030InterworkingProfile
Div | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The descriptions for new parameters under profiles signaling NNIProfile
are as follows:
Caption | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
The descriptions for new parameters under addressContext zone sipTrunkGroup signaling
are as follows:
Caption | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|