In this section:

Related articles:

 

IMPORTANT

Ribbon recommends using the Transparency Profile to configure transparency on the SBC Core Core for new deployments, as well as applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases.

Refer to the SBC SIP Transparency Implementation Guide for additional information.

This section specifies the Privacy parameters for Egress Ip Attributes.

To View and Edit Privacy

On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Ip Signaling Profile > Egress Ip Attributes > Privacy. The Privacy window is displayed.

DEFAULT_H323

On the Privacy window, choose the Ip Signaling Profile as DEFAULT_H323 to view the Privacy parameters for H323 Trunk Group.

Trunk Provisioning - Egress Ip Attributes H323 Privacy

 

There are no Privacy parameters for DEFAULT_H323 type of Egress Ip Attributes.

DEFAULT_SIP

Scenario 1: Transparency is disabled

On the Privacy window, choose the Ip Signaling Profile as DEFAULT_SIP to view the Privacy parameters for SIP Trunk Group.

Trunk Provisioning - Egress Ip Attributes SIP Privacy

 

The following fields are displayed:

Egress Ip Attributes SIP Privacy Parameters

 

Parameter

Description

Transparency

Enable flag to allow ingress Privacy information to pass through unchanged.

  • Disable (default)
  • Enable
Privacy Information

NOTE: This parameter is visible only when the Transparency parameter is set to Disable.

Use this object to specify which of the following headers the SBC uses when sending privacy information in outgoing SIP INVITE messages:

  • P Asserted Id – Used among trusted SIP entities (typically intermediaries) to carry the identity of the caller as it was verified by authentication.
  • P Preferred Id – Used by a User Agent (UA) to carry the identity the caller wishes to be used, and sent to a trusted proxy to be inserted in the P-Asserted-Identity field.
  • Remote Party Id – Used among trusted SIP entities (typically intermediaries) to carry the identity of the caller as it was verified by authentication. This header is specified in an earlier RFC that continues to be supported.

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.

Scenario 2: Transparency is enabled

When the Transparency flag is set to Enable. The appearance of the Edit Privacy window changes, and the Anonymize Host IP Portion flag appears.

Edit Privacy - Anonymize Host IP Portion

 

By default, the flags Transparency and Anonymize Host IP Address are set to Disable for the Egress IP Attributes of all IP Signaling Profiles.

 

The flag Anonymize Host IP Portion is described in the table below:

ParameterDescription
Anonymize Host IP Portion

When the flag is set to enable, the SBC anonymizes the incoming host IP portion of the private headers (P-AID, P-PID, RPID) by replacing it with the IP address of the SBC, before sending it to the egress leg of a call.

To activate this feature, set the flag Anonymize Host Ip Portion to enable.

  • Disable (default)
  • Enable


To enhance privacy transparency, set the Anonymize Host IP Portion flag to Enable.

To save the changes, click Save. To cancel all changes made since the last saved state, click Undo Edits.

  • Anonymization of the host IP address is currently supported only for in-dialog messages, and not out-of-dialog messages.
  • Anonymization of the host IP address is supported for the following message types:
    • INVITE
    • BYE
    • OPTIONS
    • SUBSCRIBE
    • NOTIFY
    • UPDATE
    • PUBLISH
    • MESSAGE

 

 

  • No labels