<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Alex,<BR> <BR>Good info, I was not aware of this. We will start handing this info out to LEOs as well. Its an easy enough flow they won't need to learn a whole new system for it. If its not in NPAC they will still need something like <a href="http://localcallingguide.com">http://localcallingguide.com</a> to find the original carrier.<BR> <BR>Thanks<BR>Brian<br> <BR><div>> Date: Tue, 17 Dec 2013 13:33:18 -0500<br>> From: abalashov@evaristesys.com<br>> To: voiceops@voiceops.org<br>> Subject: Re: [VoiceOps] Spoofed Traffic<br>> <br>> On 12/17/2013 01:23 PM, Brian R wrote:<br>> <br>> > Community question: Would it be viable/worthwhile for law enforcement<br>> > to have an agent in each department with access to tools (NPAC and<br>> > others) to look up a number and contact the correct Telco? Is this<br>> > something we even want?<br>> <br>> Note that Neustar does have, and has had for a very long time, an <br>> LEO-oriented IVR that dips NPAC for the true carrier affiliation of a <br>> number.<br>> <br>> http://www.npac.com/the-npac/access/law-enforcement-agencies-psaps/ivr-system<br>> <br>> -- Alex<br>> <br>> -- <br>> Alex Balashov - Principal<br>> Evariste Systems LLC<br>> 235 E Ponce de Leon Ave<br>> Suite 106<br>> Decatur, GA 30030<br>> United States<br>> Tel: +1-678-954-0670<br>> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/<br>> _______________________________________________<br>> VoiceOps mailing list<br>> VoiceOps@voiceops.org<br>> https://puck.nether.net/mailman/listinfo/voiceops<br></div> </div></body>
</html>