Multiple SIP HMR Sets
In general you use SIP HMR by configuring rules and then applying those rules to session agents, realms, or SIP interfaces in the inbound or outbound direction. In addition, the Oracle® Enterprise Session Border Controller has a set method for how certain manipulation rules take precedence over others. For instance, inbound SIP manipulation rules defined in a session agent take precedence over any configured for a realm, and the rules for a realm take precedence over SIP interface manipulation rules.
The multiple SIP HMR feature gives you the ability to:
- Apply multiple inbound and outbound manipulations rules to a SIP message
- Provision the order in which the Oracle® Enterprise Session Border Controller applies manipulation rules
The action parameter in the header rules configuration now takes the value sip-manip. When you set the parameter to sip-manip, you then configure the new-value parameter with the name of a SIP manipulation rule that you want to invoke. The values for the match-value, comparison-type, and methods parameters for invoked rule are all supported. This means that the manipulation defined by the rules identified in the new-value parameter are carried out when the values for the match-value, comparison-type, and methods parameters are true.
The relationship between manipulation rules and manipulation rule sets is created once you load your configuration, meaning that the order in which you enter them does not matter. It also means that the Oracle® Enterprise Session Border Controller cannot dynamically perform validation as you enter rules, so you should use the ACLI verify-config command to confirm your manipulation rules contain neither invalid nor circular references. Invalid references are those that point to SIP manipulation rules that do not exist, and circular references are those that create endless loops of manipulation rules being carried out over and over. If you load a configuration exhibiting either of these issues, the Oracle® Enterprise Session Border Controller forces the action value for the rule to none and the rule will not be used.
