|
Home > Archive > Voice over IP Cisco > December 2007 > 91 possibly calling 911?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
91 possibly calling 911?
|
|
| Scott Voll 2007-12-14, 7:11 pm |
| Is it possible if someone dials 91 and pauses long enough would it auto dial
911? I think I might have 911 set to emergency priority or what every it's
called.
CM 5.1
Scott
| |
|
|
| Scott Voll 2007-12-16, 7:11 pm |
| only asking because the last PBX did that so people are blaming the
accidental 911 calls on the CM now.
Scott
On Dec 14, 2007 3:47 PM, Wes Sisk <wsisk@cisco.com> wrote:
> 91 would definitely not match 911, not enough chars. the only way you
> could timeout and match the pattern would be pattern 91? as ? matches zero
> or more chars.
>
> /Wes
>
> Scott Voll wrote:
>
> Is it possible if someone dials 91 and pauses long enough would it auto
> dial 911? I think I might have 911 set to emergency priority or what every
> it's called.
>
> CM 5.1
>
> Scott
>
> ------------------------------
>
> ________________________________________
_______
> cisco-voip mailing listcisco-voip@puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-voip
>
>
| |
| Jonathan Charles 2007-12-16, 7:11 pm |
| Change your access code to 8...
We recommend it, but mostly because CM routes calls so much faster
than older PBXs do...
J
On Dec 16, 2007 4:04 PM, Scott Voll <svoll.voip@gmail.com> wrote:
> only asking because the last PBX did that so people are blaming the
> accidental 911 calls on the CM now.
>
> Scott
>
>
>
> On Dec 14, 2007 3:47 PM, Wes Sisk <wsisk@cisco.com> wrote:
>
> could timeout and match the pattern would be pattern 91? as ? matches zero
> or more chars.
> dial 911? I think I might have 911 set to emergency priority or what every
> it's called.
>
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Leonardo D'Urso 2007-12-16, 7:11 pm |
| hi Scott
have you tried to simulate the call with the Dialed Number Anaiyzer?
2007/12/15, Wes Sisk <wsisk@cisco.com>:
>
> 91 would definitely not match 911, not enough chars. the only way you
> could timeout and match the pattern would be pattern 91? as ? matches zero
> or more chars.
>
> /Wes
>
> Scott Voll wrote:
>
> Is it possible if someone dials 91 and pauses long enough would it auto
> dial 911? I think I might have 911 set to emergency priority or what every
> it's called.
>
> CM 5.1
>
> Scott
>
> ------------------------------
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
--
Leonardo D'Urso
l.durso@gmail.com
| |
| Scott Voll 2007-12-17, 1:12 pm |
| "Block this pattern" -- Good Call (no pun intended ;-)
Thanks All
Scott
On Dec 16, 2007 2:36 PM, Leonardo D'Urso <l.durso@gmail.com> wrote:
> hi Scott
>
> have you tried to simulate the call with the Dialed Number Anaiyzer?
>
>
>
> 2007/12/15, Wes Sisk <wsisk@cisco.com>:
>
>
>
>
> --
> Leonardo D'Urso
> l.durso@gmail.com
| |
| Leetun, Rob 2007-12-18, 1:12 pm |
|
How about changing the route pattern to 911? and 9.911?; then this would
give the caller enough time to hang up the phone based on the t.302
timer?
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Jonathan
Charles
Sent: Sunday, December 16, 2007 3:07 PM
To: Scott Voll
Cc: ciscovoip
Subject: Re: [cisco-voip] 91 possibly calling 911?
Change your access code to 8...
We recommend it, but mostly because CM routes calls so much faster
than older PBXs do...
J
On Dec 16, 2007 4:04 PM, Scott Voll <svoll.voip@gmail.com> wrote:
> only asking because the last PBX did that so people are blaming the
> accidental 911 calls on the CM now.
>
> Scott
>
>
>
> On Dec 14, 2007 3:47 PM, Wes Sisk <wsisk@cisco.com> wrote:
>
you[vbcol=seagreen]
> could timeout and match the pattern would be pattern 91? as ? matches
zero
> or more chars.
auto[vbcol=seagreen]
> dial 911? I think I might have 911 set to emergency priority or what
every
> it's called.
>
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Craig Staffin 2007-12-18, 1:12 pm |
| hey Rob thats an interesting concept
Thanks
On Dec 18, 2007 11:51 AM, Leetun, Rob <rleetun@co.boulder.co.us> wrote:
>
> How about changing the route pattern to 911? and 9.911?; then this would
> give the caller enough time to hang up the phone based on the t.302
> timer?
>
>
> -----Original Message-----
> From: cisco-voip-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Jonathan
> Charles
> Sent: Sunday, December 16, 2007 3:07 PM
> To: Scott Voll
> Cc: ciscovoip
> Subject: Re: [cisco-voip] 91 possibly calling 911?
>
> Change your access code to 8...
>
> We recommend it, but mostly because CM routes calls so much faster
> than older PBXs do...
>
>
>
> J
>
> On Dec 16, 2007 4:04 PM, Scott Voll <svoll.voip@gmail.com> wrote:
> you
> zero
> auto
> every
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
--
Craig Staffin
Craig@staffin.org
(H) 262-437-7313
(C) 262-613-6003
| |
| Jonathan Charles 2007-12-18, 7:11 pm |
| Unless you live in Illinois where 911 must be an urgent priority pattern....
Jonathan
On Dec 18, 2007 12:32 PM, Craig Staffin <cmstaffin@gmail.com> wrote:
> hey Rob thats an interesting concept
>
> Thanks
>
>
>
> On Dec 18, 2007 11:51 AM, Leetun, Rob <rleetun@co.boulder.co.us> wrote:
>
>
>
> --
> Craig Staffin
> Craig@staffin.org
> (H) 262-437-7313
> (C) 262-613-6003
| |
| Matthew Saskin 2007-12-19, 1:12 am |
| Urgent priority or not, 911 and 9.911 should always be distinct matches
and not have to wait for the t.302 timer to expire.
NPA's start with 2-9, and international calls start with 011, there
shouldn't be anything (unless you have DN's starting with 911 or 9911)
to be an alternate match...
-matt
Jonathan Charles wrote:
> Unless you live in Illinois where 911 must be an urgent priority pattern....
>
>
>
> Jonathan
>
> On Dec 18, 2007 12:32 PM, Craig Staffin <cmstaffin@gmail.com> wrote:
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Leetun, Rob 2007-12-19, 7:11 pm |
| I understand your point of view. However, when there are over 150 '911'
and '9.911' miss-dials a month. A few seconds of waiting should not be
that big of deal unless you live in Illinois as Jonathan noted. My
state does not required any urgent setting on the 911 and 9.911 route
patterns.
Rob
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Matthew Saskin
Sent: Tuesday, December 18, 2007 8:51 PM
To: Jonathan Charles
Cc: ciscovoip
Subject: Re: [cisco-voip] 91 possibly calling 911?
Urgent priority or not, 911 and 9.911 should always be distinct matches
and not have to wait for the t.302 timer to expire.
NPA's start with 2-9, and international calls start with 011, there
shouldn't be anything (unless you have DN's starting with 911 or 9911)
to be an alternate match...
-matt
Jonathan Charles wrote:
> Unless you live in Illinois where 911 must be an urgent priority
pattern....
>
>
>
> Jonathan
>
> On Dec 18, 2007 12:32 PM, Craig Staffin <cmstaffin@gmail.com> wrote:
>
wrote:[vbcol=seagreen]
would[vbcol=seagreen]
matches[vbcol=seagreen]
what[vbcol=seagreen]
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Jason Aarons \(US\) 2007-12-19, 7:11 pm |
| There are still locations that don't have 911 yet. The front cover of a
phone book in Western Oklahoma listed the sheriff's phone number.
For a fire they suggested you contact your neighbors to help put it out.
I asked the locals about this, they said if you don't help your neighbor
extinguish his fire it could spread to your property and burn your stuff
too!
Some companies re-direct 911 to a central 24-hour security/receptionist
to filter out location and help guide a local responder to you. Many
employers have CPR and other trained staff onsite.
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Leetun, Rob
Sent: Wednesday, December 19, 2007 5:55 PM
To: Matthew Saskin; Jonathan Charles
Cc: ciscovoip
Subject: Re: [cisco-voip] 91 possibly calling 911?
I understand your point of view. However, when there are over 150 '911'
and '9.911' miss-dials a month. A few seconds of waiting should not be
that big of deal unless you live in Illinois as Jonathan noted. My
state does not required any urgent setting on the 911 and 9.911 route
patterns.
Rob
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Matthew Saskin
Sent: Tuesday, December 18, 2007 8:51 PM
To: Jonathan Charles
Cc: ciscovoip
Subject: Re: [cisco-voip] 91 possibly calling 911?
Urgent priority or not, 911 and 9.911 should always be distinct matches
and not have to wait for the t.302 timer to expire.
NPA's start with 2-9, and international calls start with 011, there
shouldn't be anything (unless you have DN's starting with 911 or 9911)
to be an alternate match...
-matt
Jonathan Charles wrote:
> Unless you live in Illinois where 911 must be an urgent priority
pattern....
>
>
>
> Jonathan
>
> On Dec 18, 2007 12:32 PM, Craig Staffin <cmstaffin@gmail.com> wrote:
>
wrote:[vbcol=seagreen]
would[vbcol=seagreen]
matches[vbcol=seagreen]
what[vbcol=seagreen]
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
| |
| Jonathan Charles 2007-12-19, 7:11 pm |
| It is actually worse than that...
The City of Chicago fines you $1500 per instance of a bogus 911 call...
So, we change the access code to 8 to solve the problem.
Jonathan
On Dec 19, 2007 4:55 PM, Leetun, Rob <rleetun@co.boulder.co.us> wrote:
> I understand your point of view. However, when there are over 150 '911'
> and '9.911' miss-dials a month. A few seconds of waiting should not be
> that big of deal unless you live in Illinois as Jonathan noted. My
> state does not required any urgent setting on the 911 and 9.911 route
> patterns.
>
>
> Rob
>
> -----Original Message-----
> From: cisco-voip-bounces@puck.nether.net
>
> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Matthew Saskin
> Sent: Tuesday, December 18, 2007 8:51 PM
> To: Jonathan Charles
> Cc: ciscovoip
> Subject: Re: [cisco-voip] 91 possibly calling 911?
>
> Urgent priority or not, 911 and 9.911 should always be distinct matches
> and not have to wait for the t.302 timer to expire.
>
> NPA's start with 2-9, and international calls start with 011, there
> shouldn't be anything (unless you have DN's starting with 911 or 9911)
> to be an alternate match...
>
> -matt
>
> Jonathan Charles wrote:
> pattern....
> wrote:
> would
> matches
> what
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Matthew Saskin 2007-12-20, 1:11 pm |
| I'm not talking about best practices or suggestions, or about using the
urgent option.
From a *purely routing* point of view, there is no way (unless you have
extensions that start with 911 or 9911) for a call to a 911 or 9.911
route pattern to ever hit the T.302 timer, since they will immediately
match and route due to how the NANP is set up.
The T.302 timer only takes effect when you don't exactly match a pattern
(i.e.; you have an open-ended pattern like 9.011!)
-matt
Leetun, Rob wrote:
> I understand your point of view. However, when there are over 150 '911'
> and '9.911' miss-dials a month. A few seconds of waiting should not be
> that big of deal unless you live in Illinois as Jonathan noted. My
> state does not required any urgent setting on the 911 and 9.911 route
> patterns.
>
>
> Rob
>
> -----Original Message-----
> From: cisco-voip-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Matthew Saskin
> Sent: Tuesday, December 18, 2007 8:51 PM
> To: Jonathan Charles
> Cc: ciscovoip
> Subject: Re: [cisco-voip] 91 possibly calling 911?
>
> Urgent priority or not, 911 and 9.911 should always be distinct matches
> and not have to wait for the t.302 timer to expire.
>
> NPA's start with 2-9, and international calls start with 011, there
> shouldn't be anything (unless you have DN's starting with 911 or 9911)
> to be an alternate match...
>
> -matt
>
> Jonathan Charles wrote:
> pattern....
> wrote:
> would
> matches
> what
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Kevin Dunn 2007-12-26, 1:11 pm |
| >From a telco standpoint it is ABSOLUTELY possible to do this...
in fact most Teclo's have 91(drop) calls forward Call Information to the
PSAP in case the emergency has disrupted the call. This was very indicative
of old access codes and PBX's
>From Call Manager 5.1 the pots dial peers are matched on each digit, so 91
would not match a destination pattern of 911
So I don't think it is possible. If we are talkign about PRI connections
andnot FXO ports you might want to check with the serivce provider to see if
they are doing interdigit timeouts on their dial peers. If they are set too
quickly you sending them 9 1 NPA NXX THGP might be too slow betweenthe 1 and
the NPA and THAT telco setting could register a 911 call. ( pretty far
fetched though)
one thing we do here is whenever a 91 or 911 is called (outside access code
is 8) then there is a CDR dip that emails us so wecna ceck the erroneously
dialed numbers. I bet you have a user who is dialing incorrectly or a sticky
9 button (hits 9 and it sends 2 9's) then the 99 1 will trigger a 9. dial
peer that will contact the PSAP)
Thanks
Kevin
On 12/14/07, Scott Voll <svoll.voip@gmail.com> wrote:
>
> Is it possible if someone dials 91 and pauses long enough would it auto
> dial 911? I think I might have 911 set to emergency priority or what every
> it's called.
>
> CM 5.1
>
> Scott
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Kent Roberts 2007-12-26, 7:11 pm |
| We addressed this doing 2 things. 1 make all fax and modems unable to dial
911. (solved 50% right off the bat). Then we setup 911 to play a quick
"you have dialed 911 if this is an emergency stay on the line" and off
route. 9911 is immediate. This solved 99.99% of all our accidental 911
issues. Its amazing what a 4-6 second message saying you dialed 911 will do
to keep the local police happy.
just a though...
On 12/26/07, Kevin Dunn <cheesevoice@gmail.com> wrote:
>
> From a telco standpoint it is ABSOLUTELY possible to do this...
> in fact most Teclo's have 91(drop) calls forward Call Information to the
> PSAP in case the emergency has disrupted the call. This was very indicative
> of old access codes and PBX's
>
> From Call Manager 5.1 the pots dial peers are matched on each digit, so 91
> would not match a destination pattern of 911
>
> So I don't think it is possible. If we are talkign about PRI connections
> andnot FXO ports you might want to check with the serivce provider to see if
> they are doing interdigit timeouts on their dial peers. If they are set too
> quickly you sending them 9 1 NPA NXX THGP might be too slow betweenthe 1 and
> the NPA and THAT telco setting could register a 911 call. ( pretty far
> fetched though)
>
> one thing we do here is whenever a 91 or 911 is called (outside access
> code is 8) then there is a CDR dip that emails us so wecna ceck the
> erroneously dialed numbers. I bet you have a user who is dialing incorrectly
> or a sticky 9 button (hits 9 and it sends 2 9's) then the 99 1 will trigger
> a 9. dial peer that will contact the PSAP)
>
> Thanks
> Kevin
>
>
> On 12/14/07, Scott Voll <svoll.voip@gmail.com> wrote:
>
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
|
|
|
|
|