Multistage Routing Conceptual Example

Multistage routing is enabled by setting a policy attribute’s lookup parameter to multi. Instead of replacing the SIP message’s request URI with the policy attribute’s next hop address or response from an ENUM or LRT lookup, the system uses that next hop or ENUM or LRT lookup response to reconstruct the SIP message. The reconstructed SIP message is fed again through all configured local policy configuration elements (and policy attribute sub elements). Each time the Oracle® Enterprise Session Border Controller re-evaluates a SIP message against local policies, it is considered an additional routing stage. When multiple records are returned from an ENUM or LRT lookup, the Oracle® Enterprise Session Border Controller evaluates the first response against all applicable local policies. If unsuccessful, the Oracle® Enterprise Session Border Controller evaluates all additional responses, in turn, against all applicable local policies.

For example: