Versions Compared

Old Version 2

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_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
JIRAIDAUTHSBX-117403
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca1703948a00a02355cd1c2f0155cd26cdec0ad4, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca1703948a00a02355cd1c2f0155cd26cdec0ad4, userName='null'}


Panel

In this section:

Table of Contents
maxLevel4



Info
iconfalse

Related articles:


Excerpt Include
Services - Privacy Profile
Services - Privacy Profile
nopaneltrue

Info
titleNote

The SBC gives precedence to SIP Privacy handling when the SIP Adaptive Transparency Profile is enabled. For For example, if suppose the incoming SIP message contains "privacy: Id" and the flag applyPrivacyId under profiles services privacyProfile is set to enable. In that case, the SBC does not include the P-ASSERTED-ID header in the egress message. 

The SBC supports privacy profile over GW-GW calls (SBC-SBC GW calls).

For information on SIP Adaptive Transparency Profile information, refer to SIP Adaptive Transparency Profile - CLI.

Command Syntax

Code Block
languagenone
% set profiles services privacyProfile <privacyProfile>
	anonymizationValueforHostpart <anonymization string>
	anonymizationValueforUserpart <anonymization string>
	anonymizationValueforDispName <anonymization string>
	applyPrivacyId <disabled | enabled>
	applyPrivacyUser <disabled | enabled | <ifRcvdPrivacyUserOrIdOrBoth>
    passThruPrivacyInfo <disabled | enabled>
    supportPrivacyId <disabled | enabled | ifRcvdPrivacyId>
	supportPrivacyUser <disabled | enabled | ifRcvdPrivacyUser | ifRcvdPrivacyUserOrIdOrBoth>

Command Parameters

The Privacy Profile parameters are defined below:

Caption
0Table
1Privacy Profile Parameters
3Privacy Profile Parameters

.

ParameterLength/RangeDescription
anonymizationValueforHostpartUCHAR (0..64)Values
to use
for anonymization Hostpart in from" and contact headers while applying privacy semantics.
anonymizationValueforUserpartUCHAR (0..64)Values to use for anonymization Userpart in from and contact headers while applying privacy semantics.
anonymizationValueforDispNameUCHAR (0..64)Values to use for anonymization Display Name in from and contact headers while applying privacy semantics.

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
  • ifRcvdPrivacyUserOrIdOrBoth -
<need info, not on DSD>
  • 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

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 (PAI) header even though the incoming message does not contain "privacy: id" header. When set to the option "ifRcvdPrivacyId", the
Spacevars
0product
 removes PAI/Privacy: id only if the ingress INVITE includes the "privacy: id" header.

  • disabled (default)
  • enabled
  • ifRcvdPrivacyUserOrIdOrBoth -
<need info, not on DSD>
  •  The SupportPrivacyUser procedures are applied even if Privacy:id is received and Privacy:user is not.

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.

When set to the option "ifRcvdPrivacyUser", the 
Spacevars
0product
 anonymizes

 

  • disabled (default)
  • enabled
  • ifRcvdPrivacyUser - Anonymizes "from" and "contact" headers only if the ingress INVITE includes the "privacy: user" header.
  • disabled (default)
  • enabled
    • ifRcvdPrivacyUser
    useReceivedValuesn/aSend the From and PAI headers transparently in conjunction with the parameters above.
     



    Info

    When privacy profile and privacyParamRestricted is set, then the privacy profile gets higher precedence.


    Info
    titleNote

    When an Invite is received with the Privacy:id, even though the Privacy Profile is not configured to Anonymize From /Contact Header due to Ingress Leg properties, the SBC sends the From Header anonymized.

    Ribbon recommends to configure configuring useReceivedValues < sipFromHeader/ telFromHeader> to avoid this scenario.
    Refer to SBX-101165 Privacyprofile issues on applyPrivacyid & SupportedPrivacyId 2.



    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]

    The following examples configure a Privacy Profile using the fields anonymizationValueforUserpart, anonymizationValueforHostpart, and anonymizationValueforDispName in the privacy profile.

    Code Block
    set profiles services privacyProfile <EGR_PRIV> anonymizationValueforHostpart <Anonymous.invalid >

set profiles services privacyProfile <EGR_PRIV> anonymizationValueforUserpart <Anonymous >

set profiles services privacyProfile <EGR_PRIV> anonymizationValueforDispName <Anonymous>

set profiles services privacyProfile EGR_PRIV supportPrivacyId <disabled/enabled/ifRcvdPrivacyId >

set profiles services privacyProfile EGR_PRIV supportPrivacyUser<disabled/enabled/ ifRcvdPrivacyUser>


    Code Block
    titleExample
    % set profiles services privacyProfile <EGRPRIVACYPROFILE> useReceivedValues sipFromHeader displayName,fqdnHostPart,ipHostPart,params,userPart

% set profiles services privacyProfile <EGRPRIVACYPROFILE> useReceivedValues sipPaiHeaderr displayName,fqdnHostPart,ipHostPart,params,userPart

% set profiles services privacyProfile <EGRPRIVACYPROFILE> useReceivedValues TelPaiHeader displayName,userPart,params

% set profiles services privacyProfile <EGRPRIVACYPROFILE> useReceivedValues TelFromHeader displayName,userPart,params
    pagebreak