You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Current »
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.
Command Syntax
% set profiles services privacyProfile <privacyProfile>
applyPrivacyId <disabled | enabled>
applyPrivacyUser <disabled | enabled>
passThruPrivacyInfo <disabled | enabled>
supportPrivacyId <disabled | enabled>
supportPrivacyUser <disabled | enabled>
Command Parameters
The Privacy Profile parameters are defined below:
Privacy Profile Parameters
Parameter | Length/Range | Description |
---|
privacyProfile <name>
| 1-23 characters | <privacyProfile name> – The unique name for this Privacy Profile. This profile is used to apply privacy services independently on each call leg.
NOTE: To attach this Privacy Profile to a trunk group, refer to SIP Trunk Group - Services - CLI. |
applyPrivacyId | N/A | If the incoming SIP message contains "privacy: Id" and this flag is enabled, the Unable to show "metadata-from": No such page "_space_variables" does not include P-Asserted-Id header in the egress message.disabled (default)enabled
|
applyPrivacyUser
| N/A | If the incoming SIP message contains "privacy: user" and this flag is enabled, the Unable to show "metadata-from": No such page "_space_variables" anonymizes FROM and Contact headers.disabled (default)enabled
|
passThruPrivacyInfo
| N/A | NOTE: This flag overrides the other privacyProfile flags. If this flag is enabled, the Privacy header is passed transparently to the outgoing message and the Unable to show "metadata-from": No such page "_space_variables" sends P-Asserted-Id or FROM header as received.disabled enabled (default)
|
supportPrivacyId
| N/A | If this flag is enabled, the outgoing SIP message from the Unable to show "metadata-from": No such page "_space_variables" does not include the P-Asserted-Id header even though the incoming message does not contain "privacy: id" header.disabled (default)enabled
|
supportPrivacyUser
| N/A | If this flag is enabled, the outgoing SIP message from the Unable to show "metadata-from": No such page "_space_variables" includes anonymized FROM and Contact headers even though the incoming message does not contain "privacy: user" header.- disabled (default)
enabled
|
Command Examples
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]