You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

In this section:

Related articles:

The SIP Param Filter Profile is used by 
Unable to show "metadata-from": No such page "_space_variables"
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.

The
Unable to show "metadata-from": No such page "_space_variables"
supports configuring up to 32 SIP Param Filter Profiles. Each profile can be configured using any/all of the three SIP headers.

Command Syntax

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

% 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

SIP Param Filter Profile

 

Parameter

Description

<profile name>

Name of SIP Parameter Filter Profile (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
    Unable to show "metadata-from": No such page "_space_variables"
    to reject a request if a 'require' SIP header tag is dropped due to this profile's settings.
    • disable (default)
    • enable

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

% 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

 

  • No labels