I'm trying to get a better understanding of the NANP and how call manager compiles all of it's route patterns into the macro.
From what (limited) documentation I can find, I found that a basic USA dial-plan deployment contains the following route-patterns:
- "local": 9.[2-9][02-9]XXXXX
- "Extended local": 9.[2-9]XX[2-9]XXXXXX
So the next step was to find some random USA numbers, and I found some interesting things:
The local number 7900122 will not hit the "extended local" pattern because the second 0 does not match the pattern - so the call will go straight out.
I found at least another 3 patterns however, that match both patterns, and thus I would presume that the CUCM has to wait for it's T302 timer to expire before it matches the local pattern and routes the call.
I spoke to a friend in the USA and he is using the NANP/Route filters/9.@ and when he dials 7 digit numbers that theoretically match both patterns, it routes out without waiting for the T302 timer to expire.
Anyone care to shed any light on how I could make route patterns more specific, IE mimicking the NANP built in to CM without using it?
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...