<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoHeader, li.MsoHeader, div.MsoHeader
{mso-style-name:"Header\,Header2";
mso-style-link:"Header Char\,Header2 Char1";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{mso-style-link:"Body Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BodyTextChar
{mso-style-name:"Body Text Char";
mso-style-link:"Body Text";}
span.HeaderChar
{mso-style-name:"Header Char\,Header2 Char1";
mso-style-link:"Header\,Header2";}
span.HeaderChar1
{mso-style-name:"Header Char1";
mso-style-priority:99;
mso-style-link:"Header\,Header2";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoBodyText>The MSAG (Master Street Address Guide) is a table of
information in the FR/DBMS that is built by a municipality with the telephone
company. It contains a listing of all streets and housing number ranges
within a 9-1-1-service area. <o:p></o:p></p>
<p class=MsoBodyText><o:p> </o:p></p>
<p class=MsoBodyText>The ALI data is usually exported from CER in NENA 2.0 or
2.1 format for upload to the ALI database of the Provider. The format may vary
slightly depending on the vendor requirements. Attached is a description of the
fields required.<o:p></o:p></p>
<p class=MsoBodyText><o:p> </o:p></p>
<p class=MsoBodyText>Suggest going to this site to search for E911 contacts
depending on what servicing area the customer is located:<o:p></o:p></p>
<p class=MsoBodyText><o:p> </o:p></p>
<p class=MsoBodyText><a href="https://clec.att.com/clec/hb/index.cfm">https://clec.att.com/clec/hb/index.cfm</a><o:p></o:p></p>
<p class=MsoBodyText><o:p> </o:p></p>
<p class=MsoBodyText>Joe<o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Voice Noob<br>
<b>Sent:</b> Friday, June 12, 2009 10:11 AM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [cisco-voip] E-911 setup ERL information<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>CUCM 7.x with Emergency Responder 7.x. I have all of
the translations and locations setup working correctly. My problem is with the
local PSAP operator. The place I am setting up is a large campus but the local
Telco did not offer PRI’s or CAMA trunks before this installation. This
customer has enough clout locally to get the Telco to get the equipment so they
can have PRI’s because they wanted to implement E-911 to the police even
though there is no law requiring it yet. Now when I try to export my
location information the local PSAP administrator does not know what to do with
it. He states that all of that is handled by AT&T at the MSAG. I
don’t know what MSAG is but it sounds like that is where I need to go.
Does anyone know of a standard way to export the information that
AT&T would accept. I think I have hit a brick wall locally. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
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.
</STRONG></P></BODY></HTML>