| Ted Nugent 2007-03-31, 1:12 am |
| In my previous position we had a serious problem with
this at hundreds of locations throughout the US and in
some states the charges were outrageous. What we ended
up doing was create a TP for 911 that pointed to a
Unity AA or IPCC depending on the cluster (prefix site
code), prompting the user to dial 9911 in the future
however if it was an emergency they could hit 9 to be
transferred to emergency services (if 9 was hit,
transfer to sitecode+911CH, hits TP of sitecode.911
which striped predot and out the local RL). Fairly
admin intensive but much cheaper then the alternative.
--- Ed Leatherman <ealeatherman@gmail.com> wrote:
> What? I didnt call 911 by accident, your cdr records
> are certainly wrong!
> (never mind the callmanager traces showing the keys
> being pressed)
>
> Getting people here to stay on the line and explain
> (admit) that they
> misdialed and there is no emergency has been a
> struggle =\
>
>
> On 3/30/07, Jason Burwell
> <BurwellJ@firstcharter.com> wrote:
> explain that it was an
> police response. If
> seems to work OK for us
> patterns!
> [mailto:
> *Kris Seraphine
> 911 Policy - Please
> down on false dials but 20
> extreme. Do you have
> had situations where a
> dialing rules incorrectly
> to do a CDR search for 911
> the same source.
> <jrobbins@mercurypay.com> wrote:
> with 9 as the access code.
> between 20 and 30 911 false
> a year ago and have had 3
> [mailto:cisco-voip-bounces@puck.nether.net]
> 911 Policy - Please
> should be able to pick up
> emergency assistance...
> good idea... (do you want
> code to 7 or 8 to ensure
> <MillerS@dicksteinshapiro.com> wrote:
> as well as (9) 911. Is
> We've had 100 false 911 calls
> restrict 911 and force everyone
> would for any other outside
> know!
>
--------------------------------------------------------
> confidential and are intended solely for the use of
> the addressee(s) named above. This communication may
> contain material protected by attorney-client, work
> product, or other privileges. If you are not the
> intended recipient or person responsible for
> delivering this confidential communication to the
> intended recipient, you have received this
> communication in error, and any review, use,
> dissemination, forwarding, printing, copying, or
> other distribution of this e-mail message and any
> attached files is strictly prohibited. Dickstein
> Shapiro reserves the right to monitor any
> communication that is created, received, or sent on
> its network. If you have received this confidential
> communication in error, please notify the sender
> immediately by reply e-mail message and permanently
> delete the original message.
> an email to postmaster@dicksteinshapiro.com
> <http://www.dicksteinshapiro.com/>
>
========================================
======================================[v
bcol=seagreen]
> https://puck.nether.net/mailman/listinfo/cisco-voip
> https://puck.nether.net/mailman/listinfo/cisco-voip
> https://puck.nether.net/mailman/listinfo/cisco-voip
>[/vbcol]
=== message truncated ===>
________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
________________________________________
____
Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
http://answers.yahoo.com/dir/?link=list&sid=396546091
|