In this section:
Default values are enclosed in square brackets [ ].
This feature adds two new CLI parameters: an option to specify a hash type in TLS profiles, and an option within a PSP to assign a TLS profile for non-RTP streams.
% set profiles security tlsProfile <TLS profile name> hashType <md5 | sha1 | sha224 | sha256 | sha384 | sha512>
% set profiles media packetServiceProfile <PSP name> nonRtpStream nonRtpTlsProfileName <TLS profile name>
For more information, refer to TLS Profile - CLI.
The SBC CLI adds configuration options to assign crankback profiles at the zone and global level. An option to assign crankback profiles to trunk groups already exists, but its default setting is changed. The crankback profile object itself is unchanged.
The CLI syntax for assigning the global crankback profile is shown below. By default, the global option is assigned the "default" crankback profile.
% set global signaling crankBackProfile <profile name>
The CLI syntax for assigning the zone crankback profile is shown below. By default, the zone option is empty (" ") and, if not specifically configured, zones inherit the global-level profile.
% set addressContext <address context> zone <zone> crankBackProfile <profile name>
The CLI syntax for assigning the trunk group crankback profile is shown below. By default, the trunk group option is empty (" ") and, if not specifically configured, trunk groups inherit the profile from their zone, or from the global level if the zone is not configured with a specific profile.
% set addressContext <address context> zone <zone> sipTrunkGroup <TG name> callRouting crankBackProfile <profile name>
Parameter | Length/Range | Default | Description |
---|---|---|---|
(global) crankBackProfile <profile name> | 23 characters | default | Use this option to specify the crankback profile to apply at the global level. By default the "default" profile is assigned, but a different crankback profile can be specified. The contents of the "default" profile can be edited. |
(zone) crankBackProfile <profile name> | 23 characters | " " (empty string) | Use this option to specify the crankback profile to apply at the zone level. No profile is assigned by default. If no profile is specified, the zone inherits the crankback profile assigned at the global level. |
(trunk group) crankBackProfile <profile name> | 23 characters | " " (empty string) | Use this option to specify the crankback profile to apply at the SIP trunk group level. No profile is assigned by default. If no profile is specified, the trunk group inherits the crankback profile assigned at the zone level or from the global level if the zone is not configured with a specific profile. |
The synchronization source (SSRC) identifier uniquely identifies media streams within an RTP session when establishing or modifying media sessions. In its standard processing, the SBC generates an SSRC when it transcodes a media stream and relays the SSRCs in pass-through calls. To provide flexibility in managing SSRC values in SRTP media flows, the SBC provides a configuration option (ssrcRandomizeForSrtp
) to direct the SBC to generate and replace (randomize) the SSRC in both pass-through and transcoded SRTP media flows.
The option for randomizing the SSRC for SRTP occurs as a flag within the Packet Service Profile (PSP). Through the PSP you assign to the ingress and egress trunk group for a call, you can control whether to enable the option on the ingress leg, egress leg, or both legs of a call flow.
Note that the existing PSP flag ssrcRandomize
applies only to controlling whether to generate a new SSRC when a mid-call modification occurs in a transcoded session, and not to pass-through calls.
This feature adds one new flag parameter to the Packet Service profile.
% set profiles media packetServiceProfile <profile name> flags ssrcRandomizeForSrtp <disable | enable>
Parameter | Length/Range | Default | Description |
---|---|---|---|
ssrcRandomizeForSrtp | n/a | disable | Enable this flag to determine how the SBC handles SSRCs in SRTP media flows. When enabled, the SBC:
When disabled, the SBC relays the SSRC for pass-through media flows it receives from the peer. |
For more information, refer to Packet Service Profile - CLI.
The field dfGroupName
is added to sonusLi.yang
under addressContext/intercept/callDataChannel/mediationServer/signaling
. Associating the DF Group name is supported only for PacketCable
2.0 for the I-SBC nodes with interception type set as Signaling.
The field dfGroupName
supports a string size of up to 63 characters and responsible to maintain the mapping between the dfGroupName
and the realmName
that is used for routing X2 traffic on the SBC.
set addressContext default intercept callDataChannel CDC mediationServer MS1 signaling <DF Group Name> df1.stc.com
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
dfGroupName | 63 | N/A. | The name of the DF Group configured against the Intercept Targets for which this Mediation server is to be used for interception. | M |
This feature adds the Domain Controller root certificate to the SBC through the EMA. The new EMA interface imports the DC root certificate and stores the certificate content in the CDB/DB.
In the earlier versions, the user needs to install and apply the Domain Controller root certificate manually. Also, the AD root certificate was not persistent during the SBX upgrade.
set profiles security ldapTlsProfile <Profile Name> ldapCaCerts <PkiRootCertificateFile Name>
delete profiles security ldapTlsProfile defaultLdapTlsProfile ldapCaCerts <Certificate Name>
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
ldapTlsProfile | N/A | defaultLdapTlsProfile | The name of LDAP-TLS profile | M |
ldapCaCerts | N/A | N/A | The name of CA certificate referred by LDAP-TLS profile | M |
Two fields localTimeStamp
and localInitialTimeStamp
are added to the parameter currentStatus
to display the time in the local time zone.
The field localTimeStamp
is added to the parameter historyStatus
to display the time in the local time zone.
% show status alarms currentStatus <alarm Id> <localTimeStamp | localInitialTimeStamp>
% show table alarms currentStatus <alarm Id> <localTimeStamp | localInitialTimeStamp>
% show status alarms historyStatus <alarm Id> <localTimeStamp>
% show table alarms historyStatus <alarm Id> <localTimeStamp>
For more information, refer to Show Table Alarms and Show Status Alarms.
In earlier versions of the SBC, the statistics sipSubCountStatistics
contained counters for sipSubCountAttempts
, sipSubCountCumCompletions
, and sipSubCountStable
. This feature adds an additional counter sipSubCountFailures
to report the SIP subscription failure counts.
> show table addressContext <addressContext_name> sipSubCountStatistics <sipSubCountFailures>
> show status addressContext <addressContext_name> sipSubCountStatistics <sipSubCountFailures>
For more information, refer to Show Table Address Context - SIP Subscription Status and Show Status Address Context - SIP Subscription Status.