In this section:
Use this window to configure privacy profiles that govern how the SBC applies privacy services. Profiles can be assigned to ingress or egress SIP trunk groups and therefore allows handling privacy independently on each call leg. Options in this profile determine how privacy:id and privacy:user are handled. It also can specify to removed non-essential headers that are added by the user agent, including the Subject, Call-Info, Organization, User-Agent, Reply-To, and In-Reply-To headers. For details on the privacy handling that is governed by the Privacy Profile, refer to Caller Privacy Support.
The SBC gives precedence to SIP Privacy handling when the SIP Adaptive Transparency Profile is enabled. For example, if the incoming SIP message has "privacy: Id" and the flag applyPrivacyId
under profiles services privacyProfile
is set to enable
, the SBC does not include P-ASSERTED-ID
header in the egress message.
For information on SIP Adaptive Transparency Profile, refer to SIP Adaptive Transparency Profile - CLI.
% set profiles services privacyProfile <privacyProfile> applyPrivacyId <disabled | enabled> applyPrivacyUser <disabled | enabled> passThruPrivacyInfo <disabled | enabled> supportPrivacyId <disabled | enabled> supportPrivacyUser <disabled | enabled>
The Privacy Profile parameters are defined below:
The following example configures a Privacy Profile and attaches it to a trunk group:
set profiles services privacyProfile Test applyPrivacyId enabled applyPrivacyUser enabled passThruPrivacyInfo disabled supportPrivacyId enabled supportPrivacyUser enabled set addressContext default zone defaultSigZone sipTrunkGroup TG1 services privacyProfile Test commit show profiles services privacyProfile privacyProfile Test { applyPrivacyId enabled; applyPrivacyUser enabled; supportPrivacyId enabled; supportPrivacyUser enabled; passThruPrivacyInfo disabled; } [ok]