The Privacy Profile configuration governs how the SBC applies privacy services. You may assign profiles to ingress or egress SIP trunk groups, and allows handling privacy independently on each call leg. The options in this profile determine how "privacy:id" and "privacy:user" are handled. It also can specify to 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.

For more information, refer to Privacy Profile - CLI.

Command Syntax

> show table profiles services privacyProfile <name>

Command Parameters


Privacy Profile Parameters

ParameterLength/RangeDescription

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.

applyPrivacyIdN/A

If the incoming SIP message contains "privacy: Id" and this flag is enabled, the SBC 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 SBC anonymizes FROM and Contact headers.

  • disabled (default)
  • enabled
  • ifRcvdPrivacyUserOrldOrBoth. If selected, then the applyPrivacyUser procedures are applied even if Privacy:id is received and Privacy:user is not.

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 SBC sends P-Asserted-Id or FROM header as received.

  • disabled
  • enabled (default)
sendPrivacyUserN/A

Controls sending the Privacy:user toward the Egress.

  • disabled
  • enabled (default)

supportPrivacyId

N/A

If this flag is enabled, the outgoing SIP message from the SBC does not include the P-Asserted-Id header even though the incoming message does not contain a privacy: id header.

  • disabled (default)
  • enabled
supportPrivacyUser N/A

If this flag is enabled, the outgoing SIP message from the SBC includes anonymized FROM and Contact headers even though the incoming message does not contain a privacy: user header.

  • disabled (default)
  • enabled
useReceivedValuesN/A

Send the From and PAI headers transparently in conjunction with the parameters above.

  • disabled (default)
  • enabled

Command Examples

> show table profiles services privacyProfile
                                          PASS
      APPLY    APPLY    SUPPORT  SUPPORT  THRU
      PRIVACY  PRIVACY  PRIVACY  PRIVACY  PRIVACY
NAME  ID       USER     ID       USER     INFO
----------------------------------------------------
Test  enabled  enabled  enabled  enabled  disabled