DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.

In this section:

New CLI in 11.0.0R0

SBX-96767 PEM File Format Support for the Remote Type Certificate

Currently, the SBC supports DER encoded files for type "remote" certificates. This feature implementation enhances the SBC to accept the PEM encoded files for "remote" certificates too.

Command Syntax

% set system security pki certificate <certificate name> fileName <1-255 characters> type <local | local-internal | remote> state state <disabled | enabled>

Command Parameters

Parameter

Description

fileName

<filename> – Certificate content filename in the format:

  • Local-Internal: PEM
  • Local: PKCS#12
  • Remote: DER, PEM

Configuration Examples

set system security pki certificate COMPANY_CA filename company_ca.pem type remote state enabled
commit

SBX-103594 MSRP B2BUA Support when a=msrp-cema Present

To support the SBC role as "MSRP B2BUA" (even though the SBC receives msrp-cema attribute in the SDP), the SBC is enhanced with a configuration flag msrpB2BUA in the Trunk Group. By default, this flag is disabled.

Command Syntax

Example
% set addressContext <AC name> zone <Zone name> sipTrunkGroup <TG name> media msrpB2BUA <disabled | enabled>

Command Parameters

ParameterLength/RangeDefaultDescriptionM/O

msrpB2BUA

N/A.

disabled

This parameter ensures the role of SBC as B2BUA irrespective of the End Point role. Enable this parameter in both trunk groups to handle the msrp-cema attribute received in request/response messages.

  • disabled (default)
  • enabled
M

Configuration Examples

set addressContext default zone zoneIngress sipTrunkGroup TG_ingress media msrpB2BUA enabled
commit
set addressContext default zone zoneIngress sipTrunkGroup TG_ingress media msrpB2BUA disabled
commit

SBX-104653 Allow SMM Profile Index Gapping and Rearranging through CLI

A CLI command is introduced to create gap between the SMM rules and allow the user to add new rules in the gap without deleting the rules.

Command Syntax

% request profiles signaling sipAdaptorProfile <profile_name> cmds addGapInRuleList index <0-10000> gap <0-10000>
Note

You can enter the command from both the system-level and configure CLI modes.

Command Parameters

ParameterLength/RangeDefaultDescriptionM/O
addGapInRuleList

N/A

N/A

Use this parameter to create a gap between the SMM rules in order to add new rules in the gap without deleting the rules.

  • Gap -- Represents the number of rule positions to move after the input index. Range: 0-10000. Default = 0
  • Index -- Represents the rule after which the gap is created Range: 0-10000. Default = 0 

Note: The largest value allowed for the gap is determined based on the sum of rule count and gap.

  • The SBC generates an error in the .DBG log if the ruleCount + gap is greater than CPX_MAX_SMM_RULES.
  • The SBC generates an error in the .DBG log if the input index value is greater than or equal to Maximum Rule Index of the existing rules (index >= maxRuleIndex).
M

Configuration Examples

request profiles signaling sipAdaptorProfile SMM_INC cmds addGapInRuleList index 10 gap 5
result success

SBX-90885 Handling of RCD Passport Headers

The SBC is enhanced to pass the "jcard" and the "call-reason" parameters received in the "Call-Info" header of the SIP INVITE to the PSX when STIR/SHAKEN is enabled. To support this functionality, the flexVariable type is added to the SIP Adaptor Profile configuration to store up to 16 flex variables received from the PSX as input to the SBC SMM to modify SIP messages on the Egress leg.

Command Syntax

% set profiles signaling sipAdaptorProfile <Profile Name> rule <#> action <#> from type flexVariable
% set profiles signaling sipAdaptorProfile <Profile Name> rule <#> action <#> from flexVariableValue <flexvar1...flexvar16>

Command Parameters

ParameterLength/RangeDefaultDescriptionM/O

flexVariable

flexvar1 to flexvar16

N/A

The flex variable name of the SIP PDU manipulation entry. Use this parameter to store up to 16 flex variables received from the PSX as input to the SBC SMM to modify SIP messages on the Egress leg.

M

Configuration Examples

set profiles signaling sipAdaptorProfile smm1 rule 1 action 1 from type flexVariable
set profiles signaling sipAdaptorProfile smm1 rule 1 action 1 from flexVariableValue flexVar1
commit


SMM Configuration Examples

Example SMM for REGISTER request, where the username is modified in the Egress register:

set profiles signaling sipAdaptorProfile EBOSMM state enabled
set profiles signaling sipAdaptorProfile EBOSMM advancedSMM enabled
set profiles signaling sipAdaptorProfile EBOSMM profileType messageManipulation
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 1 type message
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 1 message
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 1 message messageTypes request
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 1 message methodTypes [ register ]
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 2 type header
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 2 header
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 2 header name to
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 2 header condition exist
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 2 header hdrInstance all
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 3 type token
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 3 token
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 3 token condition exist
set profiles signaling sipAdaptorProfile EBOSMM rule 1 criterion 3 token tokenType uriusername

set profiles signaling sipAdaptorProfile EBOSMM rule 1 action 1 type token
set profiles signaling sipAdaptorProfile EBOSMM rule 1 action 1 operation modify
set profiles signaling sipAdaptorProfile EBOSMM rule 1 action 1 from
set profiles signaling sipAdaptorProfile EBOSMM rule 1 action 1 from type flexVariable
set profiles signaling sipAdaptorProfile EBOSMM rule 1 action 1 from flexVariableValue flexVar1
set profiles signaling sipAdaptorProfile EBOSMM rule 1 action 1 to
set profiles signaling sipAdaptorProfile EBOSMM rule 1 action 1 to type token
set profiles signaling sipAdaptorProfile EBOSMM rule 1 action 1 to tokenValue uriusername
commit

This example shows the PSX-received LOGO parameter is added as a Call-info header in the Egress INVITE:

set profiles signaling sipAdaptorProfile AddCallinfo state enabled
set profiles signaling sipAdaptorProfile AddCallinfo advancedSMM enabled

set profiles signaling sipAdaptorProfile AddCallinfo rule 1 applyMatchHeader one
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 1 type message
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 1 message
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 1 message messageTypes request
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 1 message methodTypes [ invite ]
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 2 type messageBody
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 2 messageBody
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 2 messageBody condition exist
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 3 type flexVariable
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 3 flexVariable
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 3 flexVariable condition exist
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 criterion 3 flexVariable variableID flexVar4

set profiles signaling sipAdaptorProfile AddCallinfo rule 1 action 1 type header
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 action 1 operation add
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 action 1 headerPosition last
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 action 1 from
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 action 1 from type flexVariable
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 action 1 from flexVariableValue flexVar4
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 action 1 to
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 action 1 to type header
set profiles signaling sipAdaptorProfile AddCallinfo rule 1 action 1 to value Call-Info
commit

Example of a flex variable stored in a dialog scope variable, and used in a Re-Invite:

set profiles signaling sipAdaptorProfile AddCallinfo rule 2 action 2 type variable
set profiles signaling sipAdaptorProfile AddCallinfo rule 2 action 2 operation store
set profiles signaling sipAdaptorProfile AddCallinfo rule 2 action 2 from
set profiles signaling sipAdaptorProfile AddCallinfo rule 2 action 2 from type flexVariable
set profiles signaling sipAdaptorProfile AddCallinfo rule 2 action 2 from flexVariableValue flexVar1
set profiles signaling sipAdaptorProfile AddCallinfo rule 2 action 2 to
set profiles signaling sipAdaptorProfile AddCallinfo rule 2 action 2 to type variable
set profiles signaling sipAdaptorProfile AddCallinfo rule 2 action 2 to variableValue var1
set profiles signaling sipAdaptorProfile AddCallinfo rule 2 action 2 to variableScopeValue dialog
commit

SBX-106619 Voice Analytics to Identify Voice Campaigns

The SBC is enhanced to generate an audio fingerprint file on a sub-set of the calls identified for capture by SIPSG using the SAGE triggering algorithm. For calls where the audio fingerprint is computed, it is computed based on the incoming audio on the Ingress leg of the call. The audio fingerprinting is performed only for the calls where the Ingress leg is encoded using G.711 (A-law or μ-law), G.729AB, G.722, AMR, AMR-WB, EVRC, or EVRCB.

Command Syntax

% set global callTrace sageFingerprint  <disable | enable>

Command Parameters

ParameterLength/RangeDefaultDescriptionM/O
sageFingerprint

N/A

enabled

Enable this flag to generate an audio fingerprint for the incoming calls that can aid in robocalling campaign identification. The back-end systems (such as Identity Hub) use this feature to identify robocalling campaigns and classify individual calls that belong to a robocalling campaign.

Audio fingerprinting is enabled by default. A global configuration option is provided to disable the fingerprinting on the SBC.

  • disable – Disabling audio fingerprinting can free the memory allocated to store the associated captured media.
  • enable (default)
O

Configuration Examples

To enable the sageFingerprint: 

set global callTrace sageFingerprint enable
commit

To enable the sageFingerprint: 

set global callTrace sageFingerprint disable
commit