Subexpression builder for adding a routing policy SIP rule

Use the subexpression builder to build complex rule conditions from subexpressions by using AND, OR, NOT and parenthetical grouping. The rule builder validates the rule when you apply the changes, and alerts you to mismatched parentheses, and unsupported logic operators.

To view this administrative console page, click Servers > On demand routers > odr_name> SIP On demand router properties > Routing policy SIP rules > Add > Subexpression builder.

To modify rules with the rule builder, you must have administrator administrative privileges.

Select operand

The following list includes operand choices:

  • SIP method
  • Scheme on to header
  • Scheme on request URI
  • Scheme on from header
  • SIP request URI
  • SIP to URI
  • SIP from URI
  • SIP from header
  • SIP to header
  • To header display name
  • From header display name
  • To URI host
  • Server host
  • Port
  • Contact header
  • Contact URI
  • Server IPV4
  • Server IPV6
  • SIP request transport
  • Request URI user
  • From URI user
  • To URI user
  • Request URI host
  • From URI host
  • Request URI port
  • From URI port
  • To URI host
  • SIP request header name
  • Day of week
  • Day of month
  • Month of year
  • Hour of day in 24 hour format
  • Minute of day
  • Second of day
  • Year in yyyy format
Operator
  • = The equality operator expresses a case-sensitive match.
  • <> The not equal operator expresses that the operand value is not equal to the value you enter.
  • > The greater-than operator is for use with numbers.
  • >= The greater-than or equal to operator is for use with numbers.
  • < The less-than operator is for use with numbers.
  • <= The less-than or equal to operator is for use with numbers.
  • AND: For xx AND yy, expresses matches that contain both xx, yy.
  • BETWEEN: This operator is used with AND to select a range of values inclusive of the first, or low, value and the last, or high, value. Together, they operate on numbers and dates.
  • EXISTS: This Boolean operator checks for an operand or the result of a compound subexpression, for example, while checking for certain HTTP header element attributes.
  • IN: This operator expresses an operand with multiple values in a single expression. For example, if, for an operand called port, you want to express that the port value can be any or all of the values such as 9080, 9090, 9091, the expression fragment is port IN (9080,9090,9091). How the values inside the brackets are expressed depends on the data type of port. If port is an integer, the correct syntax is the values without quote marks. If port is a string, the correct syntax is port IN (‘9080’,‘9090’,‘9091’).
  • IS NULL: This operator expresses that a validation of the query shows that the requested parameter does not exist.
  • IS NOT NULL: This operator expresses that a validation of the query shows that the requested parameter exists.
  • LIKE: This operator expresses pattern matching for string operand values. The value must contain the wildcard character percent sign (%) in the position where the pattern matching starts. For example, the expression, host LIKE %blanca, matches the word blanca, or any other word that ends in blanca, while the expression host LIKE blanca% matches the word blanca or any other word that starts with blanca, and the expression, host LIKE %blanca% matches the word blanca or any word that has blanca embedded in it.
  • NOT: For NOT xx, this operator expresses matches that do not contain xx.
  • OR: For xx OR yy, this operator expresses matches that contain either xx, yy.
Value

Depending on the operator that you choose, type in a value for the subexpression that you are choosing to create.

Generate subexpression

Generate the subexpression as a result of the operand, operator, and values that you have specified.

Append

Click to append to the box on the rules panel.




WebSphere Extended Deployment information center (online)

Related information
Routing policy SIP rules
Service policy SIP rules

sip_rulebuilder_detail