Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Add_workflow_for_techpubsAUTH2AUTH1JIRAIDAUTHSBX-71659REV5REV6REV3REV1
Panel

In this section:

Table of Contents
maxLevel4

Info
iconfalse

Related articles:

Excerpt Include
Services - Privacy Profile
Services - Privacy Profile
nopaneltrue

Command Syntax

Code Block
languagenone
% 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:

Caption
0Table
1Privacy Profile Parameters
3Privacy 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

Spacevars
0product
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

Spacevars
0product
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

Spacevars
0product
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

Spacevars
0product
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

Spacevars
0product
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:

Code Block
languagenone
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]

 

Pagebreak