Local Policy Matching for Parent Realms
For SIP and H.323, you can configure the Oracle® Enterprise Session Border Controller to use the parent realm for routing purposes even when the source realm for an incoming message is a child realm.
With this feature disabled (default), the Oracle® Enterprise Session Border Controller uses the specific source realm to perform a local policy look-up. When the source realm is a child realm and any relevant local policies are configured with the parent realm, there will be no matches and the local policy look-up will fail. To avoid this issue and ensure successful look-ups, you must configure multiple local policies if you want to use a configuration with nested realms.
The Oracle® Enterprise Session Border Controller examines the source realm to determine if it is a parent realm with any child realms when you enable this feature. If the parent, source realm does have child realms, then the Oracle® Enterprise Session Border Controller creates local policy entries for the parent and all of its child realms. This operation is transparent and can save time during the configuration process.
It is possible, then, for a local policy look-up to match the same child realm in two ways:
- Through a match via the parent realm
- Through a direct match for a local policy configured with that specific child realm
In such a case, the child realm must have different costs for each type of match to avoid collisions.
This feature is enabled on a global basis in the session router configuration. Because it applies system-wide, all source realms will use this form of matching when enabled.
To enable local policy matching for parent realms:
