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
AUTH1sbsarkarUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca7f046c, userName='null'}
JIRAIDAUTHSBX-92380
REV5ghoppeUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6ghoppeUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3sguhaUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c8c30174, userName='null'}
REV1rguptUserResourceIdentifier{userKey=8a00a0c85652e498015697f3e3b3000b, userName='null'}

Panel

In this article:

Table of Contents

 

Overview

Use the SIP Adaptive Transparency Profile  to configure SIP header transparency for P-ASSERTED-IDENTITY.

When the profile is enabled for a Trunk Group and the SBC receives an updated P-ASSERTED-IDENTITY header as part of SIP Request Methods (INVITE/UPDATE), or in SIP Responses (200/180/183), the SBC relays the SIP message transparently to the other leg of the call. 

Note that SIP privacy handling takes precedence over the  SIP Adaptive Transparency Profile.

Feature Precedence and Backward Compatibility

Multiexcerpt include
MultiExcerptName_cli_precendence_sipAdaptiveTransparencyProfile
PageWithExcerpt_precedence_sipAdaptiveTransparencyProfile

Command Syntax

To configure SIP Adaptive Transparency Profile, use the following syntax:

Code Block
% set profiles services
	sipAdaptiveTransparencyProfile <profile_name>
		sipMethod <UPDATE | INVITE>
		sipResponse <180 | 183 | 200>
		state <disabled | enabled>
		triggerHeader <P-ASSERTED-ID>
			action new-value
			trigger value-change
Info
titleNote

The SIP Method INVITE applies only to "re-INVITE" scenarios, and not "initial INVITE" scenarios.

Info
titleNote

The SBC does not support all SIP requests, responses, and headers. For information on the limited support for the supported values, see the Command Parameters table below.

Command Parameters

The parameters for SIP Adaptive Transparency Profile are as follow:

Caption
0Table
1Parameter Descriptions
ParameterLength/RangeDefaultDescriptionM/O
sipAdaptiveTransparencyProfile1-23 charactersN/A<name> Specifies the profile name for which the SBC passes configured SIP headers "adaptive transparently".O
sipMethod
N/AN/A

Specifies the SIP method for which the SBC performs the configured action, when the configured triggerHeader matches with the received SIP header.

  • UPDATE
  • INVITE 

Note: The SIP Method INVITE applies only to "re-INVITE" scenarios, and not "initial INVITE" scenarios.

M
sipResponseN/AN/A

Specifies the SIP response code for which the SBC performs the configured action, when the configured triggerHeader matches with the received SIP header.

  • 180
  • 183
  • 200
M
stateN/Adisabled

The administrative state of the SIP Adaptive Transparency Profile.

  • disabled (default)
  • enabled
O
triggerHeaderN/AN/A

Specifies the SIP header which, if present in the SIP request/method or response, triggers the configured action.

  • P-ASSERTED-ID
M
actionN/Anew-value

The action that the SBC performs, when the SIP header in the request/response matches with the configured triggerHeader.

  • new-value (default)
O
triggerN/Avalue-change

The action/process that the SBC initiates, when the SIP header in the request/response matches with the configured triggerHeader. The value for this parameter acts as an indication for the configured action.

  • value-change (default)
O

Configuration Examples

To configure SIP Adaptive Transparency Profile, execute the following steps:

  1. Configure SIP Adaptive Transparency Profile with a SIP Method, or a SIP Response:

    • To configure a SIP Adaptive Transparency Profile with a SIP Method:

      Code Block
      % set profiles services sipAdaptiveTransparencyProfile TPforPAI sipMethod UPDATE triggerHeader P-ASSERTED-ID
% commit

    • To configure a SIP Adaptive Transparency Profile with a SIP Response:

      Code Block
      % set profiles services sipAdaptiveTransparencyProfile TPforPAI sipResponse 200 triggerHeader P-ASSERTED-ID
% commit

  2. Enable the profile:

    Code Block
    % set profiles services sipAdaptiveTransparencyProfile TPforPAI state enabled
% commit

  3. Attach the configured SIP Adaptive Transparency Profile to the trunk group that sends the UPDATE request.

    Code Block
    % set addressContext default zone defaultSigZone sipTrunkGroup test_sip services sipAdaptiveTransparencyProfile TPforPAI
% commit
    Tip
    titleTip

    To decide the Trunk Group to which the SIP Adaptive Transparency Profile is attached, consider the following example:

    A calls B and the call is connected. Suppose, A sends UPDATE request with changed PAI header. To configure the SBC to relay the UPDATE request to B, attach the profile to A's Trunk Group.

    Similarly, if B sends the UPDATE request that the SBC must relay to A, attach the profile with B's Trunk Group.

  4. (Optional) Display the configured profile.

    Code Block
    admin@SBC% show profiles services sipAdaptiveTransparencyProfile
sipAdaptiveTransparencyProfile TPforPAI {
    state disabled;
    sipMethod INVITE;
    sipMethod UPDATE {
        triggerHeader P-ASSERTED-ID;
    }
    sipResponse 180;
    sipResponse 200 {
        triggerHeader P-ASSERTED-ID;
    }
}
sipAdaptiveTransparencyProfile TPforPAI_2;
[ok][<YYYY-MM-DD> <HH:MM:SS>]

    Alternatively, exit from the "configure" mode and display the profile in a tabular form.

    Code Block
    admin@SBC> show table profiles services sipAdaptiveTransparencyProfile
                      METHOD                                          RSP
NAME        STATE     NAME    HDR NAME       TRIGGER       ACTION     CODE  HDR NAME       TRIGGER       ACTION
--------------------------------------------------------------------------------------------------------------------
TPforPAI    disabled  INVITE
                      UPDATE  P-ASSERTED-ID  value-change  new-value  180
                                                                      200   P-ASSERTED-ID  value-change  new-value
TPforPAI_2  disabled
[ok][<YYYY-MM-DD> <HH:MM:SS>]

    Noprint

    For more information on the "show commands, refer to Show Table Profiles - Services.

 

Info
titleNote

The SIP Method INVITE applies only to "re-INVITE" scenarios, and not to "initial INVITE" scenarios.

 


Pagebreak