My Oracle Support Banner

Geographical Routing Node Is Not Selecting the Intended Exit (Best Matched) for an Incoming Number (Doc ID 1385370.1)

Last updated on APRIL 19, 2022

Applies to:

Oracle Communications Network Charging and Control - Version 4.4.0 and later
Information in this document applies to any platform.

Symptoms

For this entire article, please observe the following nomenclature regarding the NUMBER, PREFIX_A, and PREFIX_B tokens:
  • <NUMBER> is the exact same numerical string as <PREFIX_A>
  • <PREFIX_B> is the same as <PREFIX_A> except <PREFIX_B> is shorter by 2 digit which in theory is a worse match than <PREFIX_A>
  • <PREFIX_C> is the same as <PREFIX_B> except the last digit of <PREFIX_C> is different and results in <PREFIX_C> not matching <NUMBER>

The Geographical Routing (GR) Feature Node is not selecting the intended exit (best matched) for an incoming number.

If an incoming number is <NUMBER> and there are two prefixes, <PREFIX_A> and <PREFIX_B>, the GR node is selecting an exit associated with <PREFIX_B> instead of <PREFIX_A> even though <PREFIX_A> is the "Best Match" for the incoming number.

Changes

A new prefix/exit has been configured for Geographical Routing Node.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
 Example 1
 Example 2
 Example 3
 Example Summary
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.