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_docset_workflow
APPRJIDSBX-27564
AUTH1bscoggins
DEV1akuriakose
LDEV1sgardell
SVT1dbheeman
LSVT1radaikalam
AUTHJIDSBX-27564

Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to CLI Configure Mode

Back to Profiles - CLI

Back to Services - CLI

...

Panel

In this section:

Table of Contents

...

width40%
Info

Related articles:

...

...

 

 

...

...

classexcerptdiv
Excerpt

The SIP Param Filter Profile is used by 

Spacevars
0product
to create one or more profiles defining whether to block or to transparently pass option tags/methods for

...

SIP headers

...

Allow, Require and Supported.

The SIP Param Filter Profile includes the following characteristics:

  • This profile takes precedence over existing mechanism/flags when transparently passing Allow/Supported/Require headers, but does not impact corresponding configurations established by the operator. It is operators responsibility to ensure the system is configured properly so that transparently-passed values do not conflict with existing configurations. For example, do not configure 100rel as pass-through if 100rel support fro SIP Trunk Group Signaling is disabled.
  • The settings of SIP Param Filter Profiles for both ingress and egress legs dictate the actual pass-through results (see SIP Param Filter Profile table below for details.)
  • Pass-through of individual header values is configurable.
  • SIP tags are provided for unknown SIP parameter transparency only. Known SIP parameter transparency is still determined using existing SBC application logic (from Ingress leg to Egress leg) and configurations.

For additional details, see SBC SIP Transparency Implementation Guide.

Info
titleInfo
The
Spacevars
0product
supports configuring up to 32 SIP Param Filter Profiles. Each profile can be configured using any/all of the three SIP headers.

...

Include Page
Transparency_Profile_Note
Transparency_Profile_Note

...

Command Syntax

The CLI syntax to configure the SIP Param Filter Profile is shown below:

Code Block
languagenone
% set profiles services sipParamFilterProfile <profile name>
	action 
		block <all, or  comma-separated list of tags/methods to include>
		passthru <all, or comma-separated list of tags/methods to include>
		rejectRequest <disable | enable>
	sipHeader <allow | require | supported>
	state <disable | enable>

Command Parameters

Caption
0Table
1SIP Param Filter Profile
3SIP

...

Param Filter Profile

 

Parameter

...

Description

<profile name>

...

1-23 characters

Name of SIP Parameter Filter Profile

...

Identification of the SIP header to block or transparently pass a specific tag/method, a list if tags/methods or all tags/methods, depending upon the settings for action parameter below.

  • allow (default) –  Take action on 'allow' header.
  • require – Take action on 'require' header.
  • supported – Take action on 'supported' header.

...

(1-23 characters).

action

...

Use this parameter to specify the action to take against a specified list of SIP option tags/methods for the selected SIP Headers.

  • block – Use this parameter to define which option tags/methods to block for this profile.
    • all –

...

    • Block all tags/methods.
    • <tags/methods list> – Enter one or more (comma-separated) names of the tags/methods to

...

    • block.
  • passthru – Use this parameter to define which option tags/methods to transparently pass for this profile.
    • all – Transparently pass all tags/methods.
    • <tags/methods list> – Enter one or more (comma-separated) names of the tags/methods to transparently pass.
  • rejectRequest – Enable this flag to allow
    Spacevars
    0product
    to reject a request if a 'require' SIP header tag is dropped due to this profile's settings.
    • disable (default)
    • enable
Note

The rejectRequest flag only applies to the 'require' SIP header.

sipHeader

Identification of the SIP header to block or transparently pass a specific tag/method, a list if tags/methods or all tags/methods, depending upon the settings of the action parameter.

  • allow (default) –  Take action on 'allow' header.
  • require – Take action on 'require' header.
  • supported – Take action on 'supported' header.

state

The admin state of this SIP Param Filter Profile.

...

  • disable (default)
  • enable

 

Command Example

Code Block
languagenone

...

% set profiles services sipParamFilterProfile Prof_AS sipHeader allow action block INVITE,REGISTER,OPTIONS,MESSAGE
% set addressContext default zone ZONE_AS sipTrunkGroup TG_SIPART_AS services sipParamFilterProfile Prof_AS
% commit

 

Pagebreak