In this section:
The SBC supports privacy profile over GW-GW calls (SBC-SBC GW calls). For details on the privacy handling that is governed by the Privacy Profile, refer to Caller Privacy Support.
Use this screen to configure privacy profiles that govern how the SBC applies privacy services. Profiles are assigned to ingress or egress SIP trunk groups and therefore allow handling privacy independently on each call leg. Options in this profile determine how privacy:id and privacy:user are handled. Using this screen you can also remove 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.
Note
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 displays.
Figure 1: Privacy Profile Window
To Create a Privacy Profile
To add a new Privacy Profile:
Click New Privacy Profile. The Create New Privacy window displays.
Figure 2: Create New Privacy Profile Window
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:
|
| Anonymization Valuefor Disp Name | Value to use for anonymization Display Name in "from" and "contact" headers while applying privacy semantics. |
| Anonymization Valuefor Userpart | Value to use for anonymization Userpart in "from" and "contact" headers while applying privacy semantics. |
| Anonymization Valuefor Hostpart | Value to use for anonymization Hostpart in "from" and "contact" headers while applying privacy semantics. |
To Edit a Privacy Profile
To edit a Privacy Profile:
- Click the radio button adjacent to the name of the profile to edit.. The Edit Privacy Profile window displays.
- Change the values as necessary and click Save.
To Copy a Privacy Profile
To copy a Privacy Profile:
- Click the radio button adjacent to the name of the profile to copy. Click Copy Privacy Profile. The Copy Privacy Profile window displays.
- Change the values as necessary and click Save.
To Delete a Privacy Profile
To delete a Privacy Profile:
- Click the radio button adjacent to the name of the profile to delete.
- Click the X at the end of the row to delete.
- Confirm the deletion when prompted.
Overview
Content Tools