[cisco-voip] 911 Calling Help

[Robert Kochis]

Jacquie, 

There are several problems here:
    1. 9<dot>911 dial peer would only work is someone dialed 9<some
digit>911, you need to remove the <dot> for 9911 to work correctly.

    2. I believe your logic is flawed.  The are NO area codes that start
with a digit one so long distance is not the issue.  I mean dialing 9
for an external line, then 1 for long distance and then an area code
starting with 1.  I had a similar situation in one of my offices where
the cleaning crew was attempting to call international and never dialed
the 0, they were dialing 911 instead of 9011. 

    This would only occur if you had a dial peer that was 911<multiple
dots> or 911T.  A destination pattern of 9T would work if your callers
were dialing 9911.  
    (Remember, that Cisco IOS matches longest destination pattern
possible not the first pattern it encounters.)

    3. As far as the CDR reporting goes, did you search for a string
containing the digits '911' or simply a field value of 911.  I am sure I
am not explaining this correctly but a search string of '%911%' (in
Microsoft Access) would return any records containing the value of 911
anywhere in the field, not just records that contained the literal value
of '911' 

Hope this helps,
Bob


On Fri, 2009-08-21 at 14:42 -0500, Jacquie Manick wrote:

> We currently have two route patterns to route 911 calls.  9.911 & 911
> (in case people forget to dial the 9).  We are experiencing too many
> users dialing 911 when trying to dial LD and routing out the 911
> pattern,  then get calls from emergency services to our main
> #/security personnel to verify if emergency at our location or not.  
> 
> ·       I am wondering how I could route all the 911 (usually mistake)
> calls to my 24 x 7 on-site security personnel extension rather than
> off-site?  I would still leave the 9.911 routing as is to
> off-site/gateway.
> 
> ·       The second issue I have is that when I do try to track the 911
> misdial calls in CDR to see who the offenders are, they are no where
> to be found?
> 
> Avaya had a feature that would notify a designated extension when
> calls would be placed to an “alert” flagged route pattern, if that
> could be duplicated it would be helpful
> 
> Any suggestions or workarounds would be appreciated.
> 
>  
> 
> CONFIDENTIAL: The information contained in this email communication is
> confidential information intended only for the use of the addressee.
> Unauthorized use, disclosure or copying of this communication is
> strictly prohibited and may be unlawful. If you have received this
> communication in error, please notify us immediately by return email
> and destroy all copies of this communication, including all
> attachments.
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090823/16dadf9e/attachment.html>