You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Back to Table of Contents

Back to Configuration

Back to Configuration - System Provisioning

Back to Category - Trunk Provisioning

Back to System Provisioning - Ip Signaling Profile

Back to Ip Signaling Profile - Egress Ip Attributes

Additional section:

In this section:

IMPORTANT

The Transparency Profile is the recommended method of configuring transparency on the SBC Core for new deployments as well as when 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

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

This parameter is visible only when the parameter, Transparency is disabled.

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

  • pAssertedId – Used among trusted SIP entities (typically intermediaries) to carry the identity of the caller as it was verified by authentication.
  • pPreferredId – 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.
  • remotePartyId – 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.

 

  • No labels