Suddenly Cannot Dial 911 1

[Moshimoshi]

Whoa! Okay, I just got a call from our Switchboard that, for some reason, out Mountain Patrol can no longer dial 911 from inside of the switch. This is new starting to day I'm assuming.

Someone point me at the right thing, I cant see any alarms or anything that would prevent dialing 911!

 

[inerguard]

find out what phone they are dialing it from.
see what COR that phone has.
Look at the toll lists on that cor.
Look at the toll table and see if 911 appears and an "X" appears under the toll list (right hand side)
now look at ars anal (ch ars anal 9) and see if it appears and also what route pattern it goes out on.
check that route pattern to make sure it isn't deleteing any digits.



[Started on Version 3 software 15 years a go]

 

[wmainc]

Is it just them that can't dial 911? As stated above, look at the route pattern it should go out on and check the status of that trunk group to make sure you just didn't have a line go down.

 

[Moshimoshi]

Oh man I love stuff like this. So I bury myself in the diagnostic of this, looking at ARS digit conversions and everything else, finally they call back and were like "oh, we were dialing 9-911."

so it was blocking it, dialing regular 9-11 pushes the call through how it should.

hmm, should I add an entry for 9911 to be 911 too?

 

[telecomturner]

we set up our systems to route 911 or 9911.

 

[SF0751]

Ditto. In an emergency, it's best to allow both.

Susan
"An education isn't how much you have committed to memory, or even how much you know. It's being able to differentiate between what you do know and what you don't."
- Anatole France

 

[inerguard]

Oh well, the usual fix for 99% of problems on the switch. Yip, the switch never breaks, it's the usual human problem, lolol.

Glad you got the humans fixed now though.


[Started on Version 3 software 15 years a go]

 

[Moshimoshi]

Still working on this, hoping for some input...I want to add 9+911 so that it out-dials properly, and still alerts the switchboard.

ARS Digit-conversion looks like this:

ARS DIGIT CONVERSION TABLE
Location: all Percent Full: 1

Matching Pattern Min Max Del Replacement String Net Conv ANI Req

11 2 2 2 911 ars n n


And "ch ARS anal 9" looks like this:

ARS DIGIT ANALYSIS TABLE
Location: all Percent Full: 2

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
9 7 7 p13 hnpa n
911 3 3 p18 alrt n


What am I adding here?

I don't think I need to add anything in the analysis, thats just reading for digits "911" and sending an alert, and using pattern 18, but the digit conversion, how should I put that in for people dialing 9911 to reach 911?

9911 4 4 4 Replacement 911?

Also, rats on Tek-tips for the lack of Uni-space fonts

 

[SF0751]

Hint: use either [ignore][tt]whatever[/tt][/ignore] or [ignore]

whatever

[/ignore] tags when you need something in a fixed-font.

If 9 is your ARS code, individuals who dial "9911" will reach emergency services correctly. Your entries in the ARS Digit Conversion table is correcting the dialed digits "911" in "9911" so the call will go through. (The first "9" dialed directs the call to the ARS tables).

You have everything you need with your two entries. Make sure you put this in place for each location. And make two test calls (911 and 9911) so you KNOW that it works. Just tell the emergency services operator that you are testing your PBX configuration.

Susan
"An education isn't how much you have committed to memory, or even how much you know. It's being able to differentiate between what you do know and what you don't."
- Anatole France

 

[Moshimoshi]

Hmm, thats the issue though, 911 works, but not 9911. The gentleman who called from our patrol station indicated that when he tried 9+911 (considering for a moment that you usually dial 9 to get an outside line) he received a fast-busy signal.

Which now that I think of it, is interesting, why not the usual wave-off/denial tone?

Maybe I've missed something here..

 

[SF0751]

I would try again from the station, while running a "list trace station xxxx" command to see what error message you receive.

Susan
"An education isn't how much you have committed to memory, or even how much you know. It's being able to differentiate between what you do know and what you don't."
- Anatole France

 

[Moshimoshi]

Hmm...it worked this time. So the trunk was busy??

12:17:25 active station 5290 cid 0x151c
12:17:31 dial 9911# route:ARS
12:17:31 term trunk-group 15 cid 0x151c
12:17:32 dial 9911# route:ARS
12:17:32 route-pattern 20 preference 1 cid 0x151c
12:17:32 seize trunk-group 15 member 46 cid 0x151c
12:17:34 dial 9911# route:ARS
12:17:34 outpulse done 911#
12:17:34 G711MU ssff ps:20 rn:1/1 10.130.1.66:2602 10.130.1.61:2908
12:17:34 xoip: fax:Relay modemT tty:US uid:0x400ae cid:0x151c
12:17:37 active trunk-group 15 member 46 cid 0x151c
12:17:57 idle station 5290 cid 0x151c

 

[SF0751]

Perhaps. It's hard to tell since so much time has elapased. If you haven't already, I would set up a seperate route pattern just for emergency calls, and make sure that every local trunk you have is listed in the route pattern. Just in case. Do you use the "trunk analyzer" tool in ASA?

Susan
"An education isn't how much you have committed to memory, or even how much you know. It's being able to differentiate between what you do know and what you don't."
- Anatole France

 

[Moshimoshi]

Giving you a star for the input, and excellent response times

I agree, its been a while since then. I'm still sort of new at this, so I'm uncertain how to set up a seperate route pattern just for emergency calls, or if P18 is already specifically configured to act as an emergency only route (weird that it'd be full though...)

And to answer your question, no, I haven't gotten around to playing with the trunk analyzer. I'm sort of having to reverse engineer our switch and trunking to get an idea of how its all configured :X

 

[SF0751]

Thank you. Route patterns are fun (NOT!). It took me about 6 months to get mine organized the way I really wanted them. Avaya had put everything in partition tables, and I took all of those out and used location entries instead. On your "list trace" output, I see that the 911 call went out on route pattern 20, which I'm sure is the correct entry for p18 on your partition-route-table.

Use the command 'list ars ana' or 'list ars ana loc X' to see what call types are used by route pattern 20 and/or route p18.

Susan
"An education isn't how much you have committed to memory, or even how much you know. It's being able to differentiate between what you do know and what you don't."
- Anatole France