Best Practices

This section lists practices that Oracle recommends you follow for successful implementation of this feature.

• Define all storage rules first.

  This recommendation is made because each subsequent header rule processes against the same SIP message, so each additional header rules works off of the results from the application of the rule that precedes it.

  In general, you want to store values from the original SIP header rather than from the iteratively changed versions.

• Implement rules at the element rule rather than the header rule level.

  Header rules should only be a container for element rules.

• When you are creating rules to edit a header, add additional element rules to modify a single header rather than try to create multiple header rules each with one element rule. That is, create multiple element rules within a header rule rather than creating multiple header rules.
• Do not use header or element rule names that are all capital letters (i.e., $IP_ADDRESS). Capitals currently refer to predefined rules that are used as macros, and they might conflict with a name that uses capital letters.