AVP Search Value

After the Oracle Communications Session Border Controller has identified the messages where it can look for an AVP, the avp code must be defined with a numeric AVP value to be searched. Also the AVP data type is defined so Oracle Communications Session Border Controller knows how to correctly parse the AVP once found. This is configured in the avp type parameter with valid values of: octet-string, octet-hex, integer32, unsignedint32, address, utfstring, diameteruri, or enumerated.

The comparison type is defined so that the Oracle Communications Session Border Controller knows the correct way to determine if the match value appears in the avp code. Valid comparison types are:

• Case-sensitive—The comparison-type of both case-sensitive and case-insensitive literally compares the value contained in the match-value against the received value.
• Case-insensitive—The comparison-type of both case-sensitive and case-insensitive literally compares the value contained in the match-value against the received value.
• pattern-rule—the match-value is treated as a regular expression.
• boolean—Used when it is necessary to compare the results of two or several manipulation rules with varying logic (e.g. if ($rule1 & ($rule2 | $rule3))). When the comparison-type is set to boolean, the match-value will be evaluated as a boolean expression.

Finally, the match operation is configured by defining a match value, which is the string to find. The Oracle Communications Session Border Controller evaluates if the match value is found in the avp code AVP. You may also leave the match value empty for the DMR to be applied on the AVP without testing for a match.