Rachelle

think through your BARS programming options. My first thought is to create a SPN for this DID range that is mucking up the works. You might want to look over the GHTROUT.com site for some pointers.

rlc

slagburn

That's a good step in the right direction.

We went through this exact same thing out here except that the customers made us keep their 4 digit station to station dialing on top of the 7 digit extensions on multi prefix sites some of which the 7 digit extension starts with 9. What we've wound up with is a weird combo of pre translation tables, SPNs, DMIs,RLIs and creative use of both the AC1 and AC2 tables.

EDIT: Here is something that might help. This is for a site that uses 920 as the prefix for 5 different extension ranges. DMI 5 is a dummy DMI that does nothing but this won't work if you set it to 0. Basically anything outside of the LDID numbers gets routed over RLI 4.

NXX 920
RLI 4
DMI 5
LDID 39

LDID 46

LDID 47

LDID 56

DMI 5
LDID 57

SDRR LDID CODES = 5
ITEI NONE

slagburn

I did some more poking around and realized that we aren't allowing 7 digit station to station only 4 digit station to station with 7 extensions and pre translation tables to convert the 4 digit dialed number to the 7 digit extension.

This works well on single prefix sites including the ones that have 9 as the first digit of the extension, in those cases we had to change the access code to a different number and then translate 9 to it in the pretranslation tables.

For locations with multiple prefixes you're off to BARS (or the bar in my case) for a nice cluster of programming.

Through all of this there is no 'plan' to our dialing, everything pretty much custom at each location on the network to make that site work within the customers needs.

Good Luck!!!