New 800 numbers not in CCM NANP?

Unanswered Question
Jan 16th, 2008
User Badges:

CCM 5.1

Had a complaint that users were unable to dial 800500XXXX. All other toll numbers can be dialed using the 9.@ tollfree route pattern.

I put in an explicit 9.1800500XXXX and it worked.

Does this mean that the NANP dialplan installed in 5.1 is out of date? If so how to update it? Since it's not a windows box I can't get to the file.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
gogasca Wed, 01/16/2008 - 09:42
User Badges:
  • Green, 3000 points or more

If you use Route Filters?

sposte Wed, 01/16/2008 - 10:09
User Badges:

Yes we are using route filters

rf_tollfree contains 800,877,888 etc.

eg: ==800

long distance code EXISTS

gogasca Wed, 01/16/2008 - 22:39
User Badges:
  • Green, 3000 points or more

Hi Scott,

If you use DNA (Dialed Number Analizer) which pattern selects when you delete de 1800 explicit and the only existing is 9.@ with RF.

Which exact version of CCM

Can you provide us the traces?


Tommer Catlin Thu, 03/27/2008 - 11:21
User Badges:
  • Green, 3000 points or more

I have the same problem with 888 and 866. 800 works.

I have a RP setup for 918xxxxxxxxx

I also have a RF with NANP for 9.@. I checked the dial numbered analysis and it said each of the 888 and 866 both work fine going through the RP 918xxxxxxxx, but when the end user dials, it gets a busy signal. So I think it's still trying to use the RF.


This Discussion