(string element only).
Action Value
CLI: action-value
[MessageManipulation
s_ActionValue]
Defines a value (string) that you want to use in the manipulation.
The syntax is as follows:
string/<message-element>/<call-param> +
string/<message-element>/<call-param>
For example:
'itsp.com'
header.from.url.user
param.call.dst.user
param.call.dst.host + '.com'
param.call.src.user + '<' + header.from.url.user + '@' + header.p-
asserted-id.url.host + '>'
Note: Only single quotation marks must be used.
Row Role
CLI: row-role
[MessageManipulation
s_RowRole]
Determines which condition must be used for the rule of this table row.
[0] Use Current Condition = The condition entered in this row must be
matched in order to perform the defined action (default).
[1] Use Previous Condition = The condition of the rule configured
directly above this row must be used in order to perform the defined
action. This option allows you to configure multiple actions for the
same condition.
Note: When multiple manipulations rules apply to the same header, the
next rule applies to the result string of the previous rule.
20.5 Configuring SIP Message Policy Rules
You can configure SIP message policy rules for blocking (blacklist) unwanted incoming SIP
messages or allowing (whitelist) receipt of desired messages. This feature allows you to
define legal and illegal characteristics of a SIP message. Message policies can be applied
globally (default) or per signaling domain by assigning it to a SIP interface in the SIP
Interface table (see 'Configuring SIP Interface Table' on page 207).
This feature is helpful against VoIP fuzzing (also known as robustness testing), which
sends different types of packets to its "victims" for finding bugs and vulnerabilities. For
example, the attacker might try sending a SIP message containing either an over-sized
parameter or too many occurrences of a parameter.
Each message policy rule can be configured with the following:
To Next Page
Loading...
