When dialing 94 and number i am routed to ac1. How do i route it to ac2?

[chansel77]

Currently I have several NXX and SPN that need to match. Is there a way to point to AC2 when dialing 94 rather than pointing to ac2? This would allow me to put all SPN's on AC2 so they dont conflict with NXX's

 

[KCFLHRC]

You route to AC2 by putting in an access code for AC2

 

[trvlr1]

Just curious, what SPN's do you have that conflict with NXX's? If you need something to be an SPN, delete it from NXX then add in SPN.

 

[chansel77]

KCFLHRC that is what i am trying to figure out. How do i make access code 94 go to ac2 rather than ac1? TRVLR1 i have A DSN country code 315 and a local NXX 315. I need both for the call to go through. Thanks

 

[KCFLHRC]

AC2 access code is assigned in LD 86

 

[chansel77]

Ok I found that in ld 86. Problem is i have to use 94 to access ac2 but i am using 99 to access ac1. Since i am already using 9 for ac1 the system wont allow 9 for ac2. Is there a better way to do what i am trying to do? Thanks again.

 

[KCFLHRC]

If it's programmed correctly I have never seen a need to use AC2. There should not be any conflicts if programmed correctly. If it's something you absolutely want to use the I might suggest you use 8 or something like that.

 

[chansel77]

Before we had a vendor come in a year ago we didnt have a problem. I have been trying to work this out since then. I can get the long distance to work by putting it in NPA as 1315 but with our DSN country codes i have to have a spn to get it to work. But to put 315 in as a SPN i have to delete NXX 315 which makes local calls not work. I am thinking it has something to do with the FLEN. Unfortunately the only way i can get the FLEN option is with the SPN. I dont think most people have to deal with this due to only having local and long distance. Unfortunately I have to deal with those and DSN. Appreciate all the help i can get.

 

[KCFLHRC]

So you dial 9 315 xxxx for local, how do you dial for the DSN call? Do you have different trunks for DSN as you do for local and LD?

 

[chansel77]

we actually dial 99 for local calls, we dial a pin then 98 for long distance, and we dial 94 (country code)dsn prefix and number for DSN. Yes our DSN has its own trunks.

 

[KCFLHRC]

I'm trying to figure this out in my head why in the world it is programmed like this. Not knowing your set up though I can only speculate. So "9" is AC1, so the 9 after that would tell the system you are dialing locally? Almost like 9315 would be built as an SPN for local nxx call.Are your local trunks like centrex trunks?

 

[chansel77]

yes 9 is ac1, so you are correct the 9 after that tells it is local. when i put in a local prefix i put it in as a nxx 315. our trunks are normal NI2 trunks. I am certain it is not set up correctly i just dont know how to fix it.

 

[KCFLHRC]

Very strange. I see your dilemma but without actually looking at the programming I'm not sure what direction to point you. I don't however see how 9 9 315 would be in conflict with 9 4 xx 315. If you put in a local nxx as 315 whre does the second 9 come into play when you dial 9 9 315. What is the second 9 for? It would appear to me if that is the case then your local calls would be built as SPN's as 9315.

 

[trvlr1]

Assume for a moment you only have AC1. In most PBX's to dial locally you would dial 9316xxxx but to dial LD you would dial 91315xxxxxxx. The difference is the 1 in front. So you would put the local in Nxx as 315 and the LD in NPA as 1315. You must have DMI's in place that are translating the second digit to what ever the telco needs to see.

 

[Nodal]

Usually with DSN dial plan you just define SPN's 0,1,2,3,4,5,6,7,8,9 and utilize a RLB of the first choice your local/LD T1 and second choice is the DSN circuit. Your local/LD T1 has a DMI that strips the extra 9 or 8 (99,98). Your other 91,92,93,94 access the DSN circuit. There should not be a conflict if the person is dialing 94 315-xxxx compared to 99 315-xxxx. 99 and 98 are defined as local in ESN. Hope this helps.

 

[chansel77]

Nodal I understand how that would work. Which RLB do i need to do this on? My DSN RLB is already setup that way. When i put everything as a SPN i cant make local calls. Thanks for the help.

 

[Nodal]

All SPN's would point to the same RLB which would have your Local/LD t1 as the 1st choice (ENTR) and DSN 2nd choice. 99 and 98 should be defined as local in the ESN block.

 

[chansel77]

Ok this is making me pull my hair out. i changed all my NXX and SPN's in the 300 range to just have a SPN of 3. I am able to dial DSN 315 xxx-xxxx but i cannot call a local number with an nxx of 315. I believe it has something to do with TON being NATL rather than LOCL. When i make an outgoing call to a nxx of 414 the call goes through and the TON is LOCL. I cant figure out why it is going out national. any help is greatly appreciated

 

[nessman]

Sounds like your ESN, SPN, NPA and NXX tables are a mess.

For starters, I like to use SPN when I need to make an *exception* to normal outbound dialing rules (i.e., 411, 911, international, etc.)... and not use it to create rules for normal outbound dialing. Once you do that - things get complicated and next thing you know you have a big SPN table of exceptions to your NPA/NXX tables. The fewer SPN entries, the better.

I see problems out there a lot where either customers or install/design techs make things much more complicated than they used to be. NPA/NXX tables worked great back in the day when long distance was 25 cents per minute for LD, 20 cents for in-state, 15 cents for intra-LATA, etc. But with LD plans costing practically nothing and local calls free over PRI's these days - all that work to develop least-cost routing with different carriers is just wasted effort. Long distance calling is very competitive these days. Don't like AT&T? Switch over to Windstream.

That said, go into LD 86, print out your ESN, and in LD 90, print out your SPN, NPA and NXX tables. See where the calls you're running into trouble with are being routed and work it from there. It may just end up you need to route calls to NXX 315 over a different carrier to make it work. I would also do an enhanced trace on a TN making a call to a 315 exchange and even turn up D-channel messaging for the route the call is going out over - see where the failure lies in your PBX.

I rarely see AC2 in use these days outside of large multisite enterprise settings where they had an access code for telco and an access code for their large internal telephone network. If you don't need it - I'd disable AC2. Why make things more complicated?

 

[chansel77]

Thank you for the comments nessman. I have turned on d-channel messaging and for the the 3xx calls they are going out national rather than local. The reason i have to use the spn is for the country code on our dsn network normally anywhere in the US we can dial using 7 digits but when we have to call overseas we have to use the country code. Pretty much the same as commercial. My problem is i have a 315 local prefix and a 315 DSN country code. If i put the 315 in as an NXX i cannot dial DSN country code and if i put 315 in as a SPN i cant dial the local prefix 315. Im sure my dialing plan is screwed up somewhere i just cant figure out where. Everything worked great until we had a vendor come in and switch us to 7 digit dialing and upgrade us from 3.0 to 5.0