e911 config - completing too early

[lscd-fort]

Another question I'm working on, with our UC560,

Currently '9' is our dial out digit to access the pstn.

We have a (fairly serious) problem where if a user dials '9', then '1' as if they were going to place a long distance call, then pauses for more than a few secs before entering the rest of the #, the system automatically completes the call as a 911 call.

I'd prefer to keep '9' as our trunk access digit.

From what I know so far, I feel the system should be waiting for all 3 digits of 911 (maybe even with a couple sec pause afterwards), and should not be autocompleting '91' as 911.

This seems to me to me a dial plan misconfiguration issue.

Here's snippet of the config that I think is involved, but I don't see any glaring issues with it, there must be something I'm missing.

!

dial-peer voice 58 pots

trunkgroup ALL_FXO

corlist outgoing call-emergency

description **CCA*North American-7-digit*Emergency**

translation-profile outgoing OUTGOING_TRANSLATION_PROFILE

preference 5

destination-pattern 9911

forward-digits all

no sip-register

!

dial-peer voice 59 pots

trunkgroup ALL_FXO

corlist outgoing call-emergency

description **CCA*North American-7-digit*Emergency**

preference 5

destination-pattern 911

forward-digits all

no sip-register

!

dial-peer voice 60 pots

trunkgroup ALL_FXO

corlist outgoing call-local

description **CCA*North American-7-digit*7-Digit Local**

translation-profile outgoing OUTGOING_TRANSLATION_PROFILE

preference 5

destination-pattern 9[2-9].........

forward-digits all

no sip-register

!

dial-peer voice 61 pots

trunkgroup ALL_FXO

corlist outgoing call-local

description **CCA*North American-7-digit*Service Numbers**

translation-profile outgoing OUTGOING_TRANSLATION_PROFILE

preference 5

destination-pattern 9[2-9]11

forward-digits all

no sip-register

!

dial-peer voice 62 pots

trunkgroup ALL_FXO

corlist outgoing call-national

description **CCA*North American-7-digit*Long Distance**

translation-profile outgoing OUTGOING_TRANSLATION_PROFILE

preference 5

destination-pattern 91[2-9]..[2-9]......

forward-digits all

no sip-register

!

Thanks

[mcasimirc63]

Did you verify this issue peronally because your dial-peers state that 91 is an incomplete string.

At the promt I would do the following.

term mon

debug voip dialpeer all

-dial 91

-dial 911

Then paste your debugs in a text file and post it.

[paolo bevilacqua]

I'm not aware of the possibility of the system autocompleting 91 to 911 and making the call

Yes I've seen report where users dial 91 and then 1 by mistake, even frequently.

In these cases what has worked for me, is to only allow calling 9911 in emergency, and inform anybody about. I found that is accepted as user are also used to call 9411, 9511, etc.

[mcasimirc63]

Paolo Bevilacqua wrote:
I'm not aware of the possibility of the system autocompleting 91 to 911 and making the call
Yes I've seen report where users dial 91 and then 1 by mistake, even frequently. 
In these cases what has worked for me, is to only allow calling 9911 in emergency, and inform anybody about. I found that is accepted as user are also used to call 9411, 9511, etc.

This is a lawsuit waiting to happen and people have been sued for this.  God forbid someone new or a guest freaks in an emergency and can't dial out.  There is a reason why Cisco built-in the ability to dial both.