In this section:
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:
Command Syntax
% set profiles signaling ipSignalingProfile <profile name> egressIpAttributes sipHeadersAndParameters callForwarding historyInformation includeHistoryInformation <disable | enable> supportRFC7044 <disable | enable>
% set profiles signaling ipSignalingProfile <profile name> egressIpAttributes sipHeadersAndParameters callForwarding historyInformation includeHistoryInformation <disable | enable> applyHistoryInfoPrivacy <disable | enable>
% set profiles signaling ipSignalingProfile <profile name> ingressIpAttributes ingressHistoryInformation supportRFC7044Ingress <disable | enable>
% set profiles signaling ipSignalingProfile <profile name> ingressIpAttributes ingressHistoryInformation applyHistoryInfoPrivacyIngress <disable | enable>
Command Parameters
Parameter | Description | M/O |
---|---|---|
| Enable this flag to set the History-Info header's behavior in accordance with RFC-7044.
| O |
| Enable this flag to anonymize the History-Info header.
| O |
| Enable this flag to set the History-Info header's behavior in accordance with RFC-7044 towards the Ingress leg.
| O |
| Enable this flag to anonymize the History-Info header towards the Ingress leg.
| O |
ingressHistoryInformation | Use this heading to enable the following flags:
| O |
Configuration Examples
set profiles signaling ipSignalingProfile DEFAULT_SIP egressIpAttributes sipHeadersAndParameters callForwarding historyInformation includeHistoryInformation enable supportRFC7044 enable commit
set profiles signaling ipSignalingProfile DEFAULT_SIP egressIpAttributes sipHeadersAndParameters callForwarding historyInformation includeHistoryInformation enable applyHistoryInfoPrivacy enable commit
set profiles signaling ipSignalingProfile DEFAULT_SIP ingressIpAttributes ingressHistoryInformation supportRFC7044Ingress enable commit
set profiles signaling ipSignalingProfile DEFAULT_SIP ingressIpAttributes ingressHistoryInformation applyHistoryInfoPrivacyIngress enable commit
Codec Entry
The codec "l16-16" is added to Codec Entry. Select "l16-16" to enable transcoding for the L16 codec.
% set profiles media codecEntry <name> codec <codec type: l16-16> packetSize <10 | 20> preferredRtpPayloadType <0-127>
Codec | Description | M/O |
---|---|---|
| Select to allow transcoding for the L16 codec. | O |
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.
% set profiles media codecRoutingPriority <codec: L16>
Codec | Description | M/O |
---|---|---|
| Select to enable codec routing priority for the L16 codec. | O |
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
% set profiles media packetServiceProfile <unique_profile_name> packetToPacketControl codecsAllowedForTranscoding otherLeg <l16> thisLeg <l16>
Codec | Description | M/O |
---|---|---|
| Select to allow transcoding for the L16 codec. | O |
set profiles media packetServiceProfile TEST_1 packetToPacketControl codecsAllowedForTranscoding otherLeg l16 set profiles media packetServiceProfile TEST_1 packetToPacketControl codecsAllowedForTranscoding thisLeg l16 commit
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.
% set addressContext <address context name> zone <ZONE> sipTrunkGroup <TG> services storeIdentityHdrtoCdr
Parameter | Length/Range | Default | Description | M/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.
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.
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:
| O |
set addressContext default zone <ZONE_IN> sipTrunkGroup <TG_IN> services storeIdentityHdrtoCdr shaken,rph
For more information, refer to SIP Trunk Group - Services - CLI.
In the CLI to enable FIPS mode, the parameter fips-140-2 is changed to fips-140-3.
% set system admin <SYSTEM NAME> fips-140-3 mode <disabled | enabled>
Parameter | Length/Range | Default | Description |
---|---|---|---|
fips-140-3 mode | N/A | disabled | Use this object to enable FIPS-140-3 mode.
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'. |
set system admin vsbcSystem fips-140-3 mode enabled
For more information, refer to FIPS-140-3 - CLI.