Route pattern for local & LD calls

[Muhammad Chaudhry]

First off, I am new to VOIP and still learning.

I am setting up toll bypass to Canada for calls made from our offices in USA. We have an office in Canada with a voice gateway and PRI trunk. The issue I am having is with setting up route patterns to use the toll bypass.

I have identified more than 1000 NPA-NXX that are considered local calls from the rate center our Canada office is in. These are spread out and do not follow a pattern. For instance, 905-206-XXXX and 905-208-XXXX are local, whereas, 905-207-XXXX is long-distance.

For long-distance, the telco expects a 1 before the 10 digit number, whereas for local, just the 10 digit number.

My question is, apart from creating a route pattern for each local NPA-NXX so that I discard the 1 before the 10 digit number, how would I achieve this?

Please let me know if I need to share more details. Thanks for your help.

[Chris Deren]

You wouldn't, you should define 10 and 11 digit route pattern and let user decide what they need to dial.

HTH,

Chris

[derek.andrew]

We did this with Route Filters. (Numbering Plan is NANP in the Route Pattern.)

Set up Route Patterns,

1. 9.@ Route-Filter1 Gateway1
2. 91.@ Route-Filter1 Gateway1
3. 9.@ Route-Filter2 Gateway2
4. 91.@ Route-Filter2 Gateway2

The Route Filter1 contains the NPA-NXX local to Gateway1.

The Route Filter2 contains the NPA-NXX local to Gateway2.

The NPA was defined in the Route Filter as a LOCAL AREA CODE, and the NXX was the OFFICE CODE. Then, when either 9XXXNXXXXXX or 91XXXNXXXXXX is dialed, the matching Route Filter sends it out the approriate gateway.

Note that the number of entries a Route Filter can hold is limited. We had to set up 8 route filters to contain all NPA-NXXs of interest.

D