<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.5">
<TITLE>911 Calling Help</TITLE>
</HEAD>
<BODY>
Jacquie, <BR>
<BR>
There are several problems here:<BR>
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.<BR>
<BR>
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. <BR>
<BR>
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. <BR>
(Remember, that Cisco IOS matches longest destination pattern possible not the first pattern it encounters.)<BR>
<BR>
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' <BR>
<BR>
Hope this helps,<BR>
Bob<BR>
<BR>
<BR>
On Fri, 2009-08-21 at 14:42 -0500, Jacquie Manick wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000080">We currently have two</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">route patterns</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">to route 911 calls. 9.911 & 911 (in case people forget to dial the 9). </FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">We are experiencing too many</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">users</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">dialing 911</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">when trying to dial LD</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">and routing out the 911 pattern, then get calls from emergency services to</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">our main #/security personnel to verify if emergency at our location or not. </FONT></FONT> <BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#000080">· </FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">I am wondering how I could route all the 911 (usually mistake) calls to my</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">24 x 7</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">on-site</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">security personnel extension rather than off-site?</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080"> I would still leave the 9.911 routing as is to off-site/gateway.</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#000080">· </FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">The second issue I have is that when I do try to track the 911 misdial calls in CDR</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">to see who the offenders are, they are no where to be found?</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#000080">Avaya had</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">a feature that would notify a designated extension when calls would be</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">placed to</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">an</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">“alert” flagged</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">route pattern, if that could be duplicated it would be helpful</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#000080">Any</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">suggestions or</FONT></FONT> <FONT SIZE="2"><FONT COLOR="#000080">workarounds would be appreciated.</FONT></FONT><BR>
<BR>
<BR>
<BR>
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.
<PRE>
_______________________________________________
cisco-voip mailing list
<A HREF="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>