In this section:

New CLI in 12.0.0R0

SBX-75851 Support RFC 7044 for SIP History-Info

Four flags and an Ingress IP heading are added to the IP Signaling Profile.

Two flags are set at Egress:

  • supportRFC7044
  • applyHistoryInfoPrivacy

Two flags are set at Ingress:

  • supportRFC7044Ingress
  • applyHistoryInfoPrivacyIngress

Lastly, an Ingress IP heading is added to support the above two Ingress flags:

  • ingressHistoryInformation

Command Syntax

supportRFC7044
% set profiles signaling ipSignalingProfile <profile name> egressIpAttributes sipHeadersAndParameters callForwarding historyInformation includeHistoryInformation <disable | enable> supportRFC7044 <disable | enable>


applyHistoryInfoPrivacy
% set profiles signaling ipSignalingProfile <profile name> egressIpAttributes sipHeadersAndParameters callForwarding historyInformation includeHistoryInformation <disable | enable> applyHistoryInfoPrivacy <disable | enable>


supportRFC7044Ingress
% set profiles signaling ipSignalingProfile <profile name> ingressIpAttributes ingressHistoryInformation supportRFC7044Ingress <disable | enable>


applyHistoryInfoPrivacyIngress
% set profiles signaling ipSignalingProfile <profile name> ingressIpAttributes ingressHistoryInformation applyHistoryInfoPrivacyIngress <disable | enable>

Command Parameters

ParameterDescriptionM/O

supportRFC7044

Enable this flag to set the History-Info header's behavior in accordance with RFC-7044.

  • disable (default)
  • enable
O

applyHistoryInfoPrivacy

Enable this flag to anonymize the History-Info header.

  • disable (default)
  • enable
O

supportRFC7044Ingress

Enable this flag to set the History-Info header's behavior in accordance with RFC-7044 towards the Ingress leg.

  • disable (default)
  • enable
O

applyHistoryInfoPrivacyIngress

Enable this flag to anonymize the History-Info header towards the Ingress leg.

  • disable (default)
  • enable
O
ingressHistoryInformation

Use this heading to enable the following flags:

  • supportRFC7044Ingress
  • applyHistoryInfoPrivacyIngress
O

Configuration Examples

Example: supportRFC7044
set profiles signaling ipSignalingProfile DEFAULT_SIP egressIpAttributes sipHeadersAndParameters callForwarding historyInformation includeHistoryInformation enable supportRFC7044 enable
commit
Example: applyHistoryInfoPrivacy
set profiles signaling ipSignalingProfile DEFAULT_SIP egressIpAttributes sipHeadersAndParameters callForwarding historyInformation includeHistoryInformation enable applyHistoryInfoPrivacy enable
commit
Example: supportRFC7044Ingress
set profiles signaling ipSignalingProfile DEFAULT_SIP ingressIpAttributes ingressHistoryInformation supportRFC7044Ingress enable
commit
Example: applyHistoryInfoPrivacyIngress
set profiles signaling ipSignalingProfile DEFAULT_SIP ingressIpAttributes ingressHistoryInformation applyHistoryInfoPrivacyIngress enable
commit

SBX-116105 Support for Linear 16 (L16) on SBC

Codec Entry

The codec "l16-16" is added to Codec Entry. Select "l16-16" to enable transcoding for the L16 codec.

Command Syntax

Example
% set profiles media codecEntry <name> 
    codec <codec type: l16-16>
    packetSize <10 | 20>
    preferredRtpPayloadType <0-127>

Command Parameters

Codec

Description

M/O

l16-16

Select to allow transcoding for the L16 codec.

O

Configuration Examples

set profiles media codecEntry NewCodec codec l16-16 packetSize 20 preferredRtpPayloadType 96
commit

Codec Routing Priority

The codec "L16" is added to Codec Routing Priority. Select "L16" to enable codec routing priority for the L16 codec.

Command Syntax

Example
% set profiles media codecRoutingPriority <codec: L16>

Command Parameters

Codec

Description

M/O

L16

Select to enable codec routing priority for the L16 codec.

O

Configuration Examples

set profiles media codecRoutingPriority L16 entry L16
commit

Packet Service Profile Entity

The codec "l16" is added to the Codec list for Packet Service Profile Entity. Select "l16" at "This Leg" and/or "Other Leg" to enable transcoding for the L16 codec.

Command Syntax

Example
% set profiles media packetServiceProfile <unique_profile_name> packetToPacketControl
	codecsAllowedForTranscoding
        otherLeg <l16>
        thisLeg <l16>

Command Parameters

Codec

Description

M/O

l16

Select to allow transcoding for the L16 codec.

O

Configuration Examples

set profiles media packetServiceProfile TEST_1 packetToPacketControl codecsAllowedForTranscoding otherLeg l16
set profiles media packetServiceProfile TEST_1 packetToPacketControl codecsAllowedForTranscoding thisLeg l16
commit

SBX-118127 SHAKEN Fields in CDR for Identity Header Passthrough

This feature adds the CLI parameter storeIdentityHdrtoCdr to the SIP Trunk Group > Services CLI. This CLI configuration is used to decide which identity headers are captured in the CDR.

Command Syntax

storeIdentityHdrtoCdr - CLI
% set addressContext <address context name> zone <ZONE> sipTrunkGroup <TG> services storeIdentityHdrtoCdr

Command Parameters

ParameterLength/RangeDefaultDescriptionM/O
storeIdentityHdrtoCdr

N/A

none

The SBC stores the base64 decoded Identity headers received and sent in the SIP INVITE message. Use this flag to specify the Identity headers to store in the CDR record.

  • all
  • div
  • none (default)
  • other
  • rcd
  • rph
  • shaken
Note

You can specify all the identity headers in the list to store them in the CDR, or choose the ones you require. However, if you select 'none' and another option, for example 'shaken', 'none' takes precedence and no identity headers are stored in the CDR. 

Similarly, if you select 'all' and another identity header, for example 'shaken'. The choice 'all' takes precedence and all the identity headers in the list are stored in the CDR.


The values are a comma-separated list of categories. The priority order for writing in the CDR from the highest to the lowest is, SHAKEN, RPH, RCD, DIVs and OTHER. A maximum of nine identity headers are logged in the CDR for ingress and egress. If the higher priority headers take up all the space, then the lower priority headers are not written in the CDR.

When more than one SHAKEN header arrives in the Ingress INVITE, then the following is the order of precedence in which the Identity header is picked: 

  1. SHAKEN header with Attestation Level 'A is picked.
  2. If more than one SHAKEN header with Attestation 'A' level is present, the top-most A level SHAKEN header is picked.
  3. If no Attestation Level 'A' SHAKEN header is present, then Attestation level 'B' SHAKEN header is picked.
  4. If more than one SHAKEN header with 'B' level is present, the top most 'B' level SHAKEN header is picked.
  5. If no Attestation Level 'B' SHAKEN header is present, then Attestation level 'C' SHAKEN header is picked.
  6. If more than one SHAKEN header with Attestation 'C' level is present, the top-most 'C' level SHAKEN header is picked.
O

Configuration Example

storeIdentityHdrtoCdr - CLI Example
set addressContext default zone <ZONE_IN> sipTrunkGroup <TG_IN> services storeIdentityHdrtoCdr shaken,rph

For more information, refer to SIP Trunk Group - Services - CLI.

SBX-122231 FIPS 140-3 Support in SBC

In the CLI to enable FIPS mode, the parameter fips-140-2 is changed to fips-140-3. 

Command Syntax

% set system admin <SYSTEM NAME> fips-140-3 mode <disabled | enabled>

Command Parameters

ParameterLength/RangeDefaultDescription
fips-140-3 mode

N/A

disabled

Use this object to enable FIPS-140-3 mode.

  • disabled (default)
  • enabled

NOTE: Once you enable fips-140-3 mode, you cannot manually disable it. A fresh software installation is required to set the FIPS-140-3 mode back to 'disabled'.

Configuration Example

set system admin vsbcSystem fips-140-3 mode enabled

For more information, refer to FIPS-140-3 - CLI.