AVP Search Value

The Oracle Communications Session Border Controller searches for matching values in AVPs by using the information defined in diameter-manip-rule elements. The following parameters specify the type of message to look in, the AVP code to look for, the value to look for, and how to determine the match:

  • msg-type: The messages (requests, replies, or any) where the SBC can look for an AVP.
  • avp-code: The AVP to act on, using a numeric AVP value.
  • avp-type: The AVP data type, so that the SBC knows how to correctly parse the AVPs it finds. Valid values are:
    • octet-string
    • octet-hex
    • integer32
    • unsignedint32
    • address
    • utfstring
    • diameteruri
    • enumerated
    • grouped
  • comparison-type: The correct way to determine if the match value appears in the AVP. Valid values are:
    • case-sensitive: Literally compares the value contained in the match-value parameter against the received value, respecting case.
    • case-insensitive: Literally compares the value contained in match-value against the received value, ignoring case.
    • pattern-rule: Treats match-value as a regular expression.
    • boolean: Treats match-value as a boolean expression. Compares the results of two or more manipulation rules with varying logic. For example, if ($rule1 & ($rule2 | $rule3)).
  • match-value: The string to find. You can optionally leave this empty to apply the rule on the AVP without testing for a match.
  • avp-path: The path of grouped AVPs that contain the AVP identified in avp-code. Used only when the action parameter is set to store or add. This lets you move data between grouped AVP hierarchies.

    The value consists of one or more comma-separated AVP codes, with optional 0-based index numbers in square brackets. For example, to look for the second instance of AVP 876 in grouped AVP 873, you would set this to 873,876[1].