Called number doesn't match with most specific RoutePattern

Unanswered Question
Jun 28th, 2007

I have configured a RoutePattern 0.0044! to match calls from our Dutch CCM cluster to our UK CCM cluster. When I call a UK number in the DNA (Dialed Number Analyzer) it matches with the more generic RoutePattern 0.@ When I configure a RoutePattern with a prefix 2 (2.0044!) it does match with this specific 2.0044! pattern... Do you have any suggestions what goes wrong? The same configuration does work for our other ICL to Sweden...

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3.3 (3 ratings)
Loading.
Zin.Karzazi Thu, 06/28/2007 - 03:16

The @ pattern causes many individual patterns to be added on the user?s behalf.

If an individual pattern in the @ wildcard is a better match than the user?s pattern,

then the @ pattern will be chosen. Look in the NANP file to see the list of patterns or look in the CCM trace to see which pattern was matched.

marjoleinholsboer Sun, 07/01/2007 - 22:43

thank you for the reply;

So if I understand correctly; NANP comprises a route pattern to the UK that is more specific than 0044! "44" is the international number for the UK. How can I work around this? Do I have to configure more specific RoutePatterns like 00441!, 00442!, etc? Is there a document with the specific NANP RoutePatterns?

marjoleinholsboer Sun, 07/01/2007 - 22:57

In the Dutch NANP file, I read the following for the UK (+44):

P: 00 INTERNATIONAL-ACCESS

P: 4[013-9] COUNTRY-CODE

P: ! NATIONAL-NUMBER

P: # END-OF-DIALING

T: I

W: OP

So my RoutePattern 0044! is more specific than the NANP pattern for the UK.

mlucas1911 Mon, 07/02/2007 - 05:46

That is correct, it is more specific but the logic CCM will use when there is a @ present is to try it first. The recommended design is to only use the @ when you are utilizing Route Filters. Otherwise, create more site specific patterns like 0044!

marjoleinholsboer Thu, 07/05/2007 - 01:15

The issue is solved. We allready were using @ in combination with RouteFilters. We have removed the UK international number from the RouteFilter and now it works. It is still strange because for Sweden it works with the Swedish international number included in the RouteFilter...

Thank's for all the help!

Actions

This Discussion