Well if you're willing to stick it out with us, I'm sure we'll get to the bottom of it. The price is certainly right!

I'm thinking that 1-206-xxx-xxxx calls have been defined as local toll rather than long distance (or appropriately defined as local, but with incorrect entries in the LNPA tables). Issue a display dialplan command and see if 206 is listed as one of the seven Local Area Codes. You'll find these at the top of the form, just to the right of your Home Area Code. It should be there if 206 is one of your local area codes.

If it's not there, then I need to take this another direction. But if it IS there, take a look at the CO codes that are listed in the LNPA Toll Table for the 206 area code. I'll bet one of the CO codes shown is 444 (along with the other prefixes chosen for your testing), and that it's defined as a local call. Actually, a quicker way to answer these questions might be to issue a display lnpa-toll 206:444 command and see what you get.

You also need to check the Prefix Mark for the various route patterns. If 206 represents a local area code for you, make sure that Prefix Mark for 206's route pattern is set to 0.

I would also remove the ars analysis table entry for 206 with the min/max digits of 10/10. Even if you modify it to be 1206 with 11/11, it won't fix the problem.


"Press play and record at the same time" -- Tim Alberstein