Tel-URI Resolution
The Oracle Communications Core Session Manager can initiate number resolution procedures for requests that have tel-URI or SIP-URI (with user=phone) numbers in the R-URI. It does this by querying number resolutions services, including the local routing table(s) or ENUM server(s) to resolve the R-URI to a SIP URI. In addition, the original R-URI may not include a full E.164 number. As such, you can also configure the Oracle Communications Core Session Manager to perform a number normalization procedure and ensure it presents a full E.164 number for resolution. Upon successful resolution, the Oracle Communications Core Session Manager proceeds with ensuing signaling procedures.
To configure the Oracle Communications Core Session Manager to perform these lookups, you create applicable local-routing-config or enum-config elements and set an option within the sip-registrar that specifies a primary and, optionally, a secondary local-routing-config or enum-config that the sip-registrar uses for LRT or ENUM lookups. If there is no ENUM configuration on the sip-registrar, the Oracle Communications Core Session Manager forwards applicable requests to a border gateway function via local policy.
Refer to the Oracle Communications Session Border Controller ACLI Configuration Guide , Session Routing and Load Balancing chapter for complete information on how to configure a local-routing-config and/or an enum-config.