redG

We are going to add 4 remote EPNs to our G3r rel.11. These will be in different states, connected by T-1. We are converting to High Reliability from Critical Reliability to avoid having to duplicate interstate spans. The issue is the programming of partitioning. We wish to allow each remote site to dial intra-lata using their local facilities, and also to allow anyone else on the switch to call that same 'local' area from a remote area, using the same local facilites so we can avoid LD charges. Example: People in Southern Georgia wish to call a location in Louisiana. If we have an EPN in Louisiana with local trunks, how can the Georgia folks dial out on them to make it appear as a local call?

stubborne

ARS and location-based routing will do the trick. Each location (EPN) has an ARS location table with just 7 digit dialing assigned (and 911 or toll free). Your PPN ARS would have all 10 digit dialing entries. You would build 2 route patterns around each trunk group (local to the EPNs). One for the 7 digit dialing entries where you insert NPA and pad if needed, and one for LD where NPA is generic and no padding exists. Trick is on the location table, the number plan area code assigned to the location must match the area code in the NPA field on the route pattern.

If your using IP phones, the network region form has a location field. Use this to assign the phone/network region to a location.

__________________
Stu

PBXtech.info

 

nexSIP

Also just a though. You should make sure what you are doing is legal.

koelemon

Definately do the location routing, nice feature made especially for situations like this.

Good point, I think the only legality is to make sure each EPN has its own 911 routing and caller ID set up.

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."