<HTML><HEAD></HEAD>
<BODY>
<DIV dir=ltr id=idOWAReplyText25212>
<DIV dir=ltr><FONT color=#000000 size=2 face=Arial>E911 does not follow the standard SIP RFC. That would be a good reason that they couldn't/wouldn't do it. Now that I say that I should qualify it and say "NG911 (or ESINet) does not follow SIP RFC" <A href="http://en.wikipedia.org/wiki/Next_Generation_9-1-1" target=_blank>http://en.wikipedia.org/wiki/Next_Generation_9-1-1</A>. That is not saying your county is not using standard SIP for E911, it just wouldn't be considered NG911.</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> Chris Nighswonger<BR><B>Sent:</B> Fri 4/19/2013 11:41 AM<BR><B>To:</B> Asterisk Users Mailing List - Non-Commercial Discussion<BR><B>Subject:</B> [asterisk-users] E911 Voip Trunking<BR></FONT><BR></DIV>
<DIV>
<DIV dir=ltr>
<DIV>
<DIV>During the course of a conversation with an member of the IT group who handles the E911 center for our county, I learned that all of the county's E911 is voip based. This got me to wondering why we could not just configure up a SIP or some such trunk directly to the E911 center to handle our emergency traffic. The county seems interested in exploring the possibility.<BR><BR></DIV>So I'm wondering if anyone else has attempted this.<BR><BR></DIV>Kind Regards,<BR>Chris<BR></DIV></DIV></BODY></HTML>