HELP...911 Routing issue!! 2

[2newphoneguys]

I currently have an offsite switch that is sending 911 calls to the wrong dispatch center. All the calls go back to the main site as if they were originating there, thus causing a huge issue should an actual emergency occur. Since this is a potential life safe call, it's imperative I get it fixed right away...since it seems like my issue and not the CO/LEC.
The problem I am having is understanding the routing for the 911 call. Currently, it routes back to the main site over SIP trunks, but it should actually route out over the local PRI, through the local CO/LEC, to the local dispatch center.
The RLI for 911 is 6, the RLI for PRI/failover trunks is 1,and the RLI for SIP trunks is 0. I have attached some SPN info from LD 90 and RLI info from LD 86. Am I missing something?
If anyone could help with directions it would greatly appreciated?

 

[RickyPone]

I didn't look at your attachment but 911 should point to one rli with two entries. Entry 0 should send the call out your local pri for the switch and entry 1 should send it over the sip to the main site in case your pri is down. Set the frl to 0 so everyone can dial 911.

 

[KCFLHRC]

You don't see a route because the RLI is saying it's a local termination send to a dmi table 3

 

[KCFLHRC]

You need to see what DMI 3 is doing

 

[KCFLHRC]

Print DMI 3 in LD 86 and see what it is doing

 

[2newphoneguys]

Thanks RickyPone and KCFLHRC, I have checked out both of your suggestions and seem to have found some good leads....especially with the DMI tip. I think that might be where my problems lyes. Again, thanks to the both of you and Tek-tips...always a wealth of knowledge!

 

[2newphoneguys]

Help still needed....I checked my DMI 3 for RLI 6, changed it from NXX to LSC, CDP and virtually any other dialing plan option I could find. None of that made a difference. I change RLI 6 to where it should only route out over the PRI and calls still route back through the main site, wrong 911 dispatch center. I am at my wits end, because the only difference in this site and my other off site is ISET = 1 at other off site (which works fine). I changed that too, still didn't work! I don't know if this would make a difference, but the other off site has another route built that is designated 911 for a COT trk (no UNIV TRK card though), and then it has programming in that route for a PRI as well it seems. Strange to me, but could this be proper protocol to build a route for trks that are even there to get it to route over a PRI? If so could someone point me in the right direction? Should I build this extra route at this site too?

 

[RickyPone]

Can you just change 911 in ld 90 and send it out rli 1? Have you tried that? I took from your first post that rli 1 is where your local traffic is pointed.

 

[2newphoneguys]

How do I build an access code for a route...more like what ld(s) do I go to?
I tried that already RickyPone...doesn't work. Actually RLI 1's 1st ENTR = 0 which points to SIP trunks and 2nd ENTR = 1 which points to the local. All RLI entries are like that except for 6 which I built to directly access the local PRI. However, it still isn't working.
One thing I need to mention, if I haven't already, is that this site is in another state, whereas my other 2 sites are not. The same telco handles all of the area though. Just wandering if there are some regulations that won't allow a states number with different area codes to forward the 911 info to another jurisdiction in a neighboring state. Any help will be greatly appreciated.

 

[RickyPone]

When you build a route you have to assign an access code(acod). It is in the rdb.

 

[2newphoneguys]

OKa...did that, but I get a busy signal when I dial it from my set to test it. Is there any where else it needs to be programmed. If the access for the existing route I am trying to use is ex. 9999 and I built 9998 for new route, how is it gonna know to route over to 9999 for the call? And can I do that? I guess I should have asked these questions before I built it, but I thought I had a decent grasp on that part of the programming. Obviously not!

 

[jaxuser]

post DMI 3 so we can see what it does

 

[2newphoneguys]

There is a link to it where I started the thread...will give a good overview of what I am dealing with

 

[jaxuser]

I see your traces, and RLI but not the DMI table.

 

[RickyPone]

You would have to change rli 6 route entry to the new route in order for 911 calls to utilize the new route. What trunks are you using for the new route. And if your test phone has a tgar that matches the targ of the new route you won't be able to dial the access code. Change the targ of your test phone to 0.

 

[2newphoneguys]

I change the route to the new 1 I built and the trunks are the local PRI. I need to check my TAGR and TGAR though and make some adjustments if necessary...good lead. Thanks RickyPone

 

[RickyPone]

Change the targ for the new route to 0. That is better than changing the test phone which I would still do.

 

[2newphoneguys]

Ok, thanks...I'll try that on Monday.

 

[guycable2]

I can't look at the attachment so I'm not 100% sure what you posted but is it possible that ESA is setup in LD 24 and that is where the RLI or Route needs to be changed? You can have an SPN of 911 even though ESA is built it just gets ignored.

Go to LD 24 and do a PRT ESA and paste it here.

 

[2newphoneguys]

Yeah....cudo's to you guycable2 (and the rest of the tektip clan), but guycable your suggestion seemed to be on point. The RLI was 5 in ESA, I changed it to 6 and made some test calls. All of them routed properly over the local PRI. Everyone, I am so appreciative for all the good feedback that helped me get this issue resolved. No more "PLOOP PLOOP FIZZ FIZZ" cause oh what a releif it is! Thanks everyone