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 Apply Privacy Id
under Profiles > Services > Privacy Profile
is enabled, the SBC does not include P-ASSERTED-ID
header in the egress message.
For information on SIP Adaptive Transparency Profile, refer to Services - SIP Adaptive Transparency Profile.
On the SBC main screen, go to All > Profiles > Services > Privacy Profile. The Privacy Profile window opens.
To add a new Privacy Profile:
Click New Privacy Profile. The Create New Privacy window opens.
Use the following table to configure the profile then click Save.
Parameter | Description |
---|---|
Name | Specifies a unique identifier for the privacy profile. |
Apply Privacy ID | If this option is enabled and the incoming SIP message contains "privacy: id", the SBC does not include a P-Asserted-Id header in the egress message. The options are:
|
Apply Privacy User | If this option is enabled and the incoming SIP message contains "privacy: user", the SBC anonymizes the From and Contact headers. The options are:
|
Support Privacy ID | If this option is enabled, the outgoing SIP message from the SBC does not contain a P-Asserted-Id header even if the incoming message does not contain "privacy: id." The options are:
|
Support Privacy User | If this option is enabled, the outgoing SIP message from the SBC contains anonymized From and Contact headers even if the incoming message does not contain "privacy: user." The options are:
|
Pass Thru Privacy Info | This option overrides the other four profile options. If this option is enabled, the Privacy header is passed transparently to the outgoing message and the SBC sends P-Asserted-Id or From headers as received. The options are:
|
To edit a Privacy Profile:
To copy a Privacy Profile:
To delete a Privacy Profile: