In this article:

 

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

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 applyPrivacyId under profiles services privacyProfile is set to enabledthe SBC does not include P-ASSERTED-ID header in the egress message.

For more information on privacyProfile, refer to the following pages:

 Several flags prevent the SBC from relaying a re-INVITE, or an UPDATE, to the other leg of the call. When you enable such flags, the behavior is contradictory to that of the SIP Adaptive Transparency Profile. 

To resolve such conflicts, the SBC gives precedence to the SIP Adaptive Transparency Profile over the following flags:

  • Parent Object: profiles signaling ipSignalingProfile <profile_name> commonIpAttributes flags
    • relayDataPathModeChangeFromOtherCallLeg
    • minimizeRelayingOfMediaChangesFromOtherCallLegAll
    • disableMediaLockDown
    • lockDownPreferredCodec
    • callHoldInterworking 
  • Parent Object: addressContext <addressContext_name> zone <zone_name> sipTrunkGroup <sipTrunkGroup_name> signaling
    • sdp100relIwkForPrack
    • rel100Support
  • Parent Object: addressContext <addressContext_name> zone <zone_name> sipTrunkGroup <sipTrunkGroup_name> media
    • lateMediaSupport


For more information on the flags mentioned above, refer to the following pages:

Command Syntax

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

% 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
		
Note

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

Note

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:

Parameter 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:

      % set profiles services sipAdaptiveTransparencyProfile TPforPAI sipMethod UPDATE triggerHeader P-ASSERTED-ID
      % commit
      
    • To configure a SIP Adaptive Transparency Profile with a SIP Response:

      % set profiles services sipAdaptiveTransparencyProfile TPforPAI sipResponse 200 triggerHeader P-ASSERTED-ID
      % commit
      
  2. Enable the profile:

    % 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.

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

    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.

    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.

    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>]
    
    

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

 

Note

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