<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div><div><div>Every calea request that we have had to deal with we have had a setup like the one described below where we would basically fork the call to an external # for the audio as well as we setup a vpn connection with the requesting agency to send them the live call data. Eg. Touch tones pressed ect.</div><div><div><br></div><div>Carlos Alcantar</div><div>Race Communications / Race Team Member </div><div><font class="Apple-style-span" face="Consolas"><span class="Apple-style-span" style="font-family: Calibri, sans-serif; ">1325 Howard Ave. #604, Burlingame, CA. 94010</span></font></div><div>Phone: +1 415 376 3314 / carlos@race.com / http://www.race.com</div></div></div></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Ryan Delgrosso <<a href="mailto:ryandelgrosso@gmail.com">ryandelgrosso@gmail.com</a>><br><span style="font-weight:bold">Reply-To: </span> "<a href="mailto:ryandelgrosso@gmail.com">ryandelgrosso@gmail.com</a>" <<a href="mailto:ryandelgrosso@gmail.com">ryandelgrosso@gmail.com</a>><br><span style="font-weight:bold">Date: </span> Friday, January 18, 2013 3:59 PM<br><span style="font-weight:bold">To: </span> VoiceOps <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [VoiceOps] CALEA for the small fry operator<br></div><div><br></div><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div bgcolor="#FFFFFF" text="#000000">
Well in our case we were provided with a destination that signaling was to be sent to at Quantico, and a phone number that would be dialed to collect the audio (forked in the network). This is of course the fancy way. I'm sure any call recording solution that
can associate signaling and media in a neat package would probably suffice, presuming its local and not federal. Again IANAL so you might want to consult with one before taking anything I say as gospel.
<br><br>
-Ryan <br><br><div class="moz-cite-prefix">On 01/18/2013 03:50 PM, Carlos Alvarez wrote:<br></div><blockquote cite="mid:CAFn1dUG3MJXU+gNtRwJpCwd2Fy-mJpZn8vHz1gwn4mZ=j7EfNQ@mail.gmail.com" type="cite">
On Fri, Jan 18, 2013 at 4:44 PM, Ryan Delgrosso <span dir="ltr"><<a moz-do-not-send="true" href="mailto:ryandelgrosso@gmail.com" target="_blank">ryandelgrosso@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">I would respectfully disagree. We are most certainly not a CLEC, but we have received warrants for wire taps, and have complied. Fortunately we do use a commercial softswitch that can provide this.<br></div></blockquote><div><br></div><div>When you say "provide this" can you tell us exactly how? It seems like a simple ability to listen in to calls may or may not be compliant.</div><div><br></div></div><div><br></div>
-- <br><div>Carlos Alvarez</div><div>TelEvolve</div><div>602-889-3003</div><div><br></div><br><fieldset class="mimeAttachmentHeader"></fieldset> <br><pre wrap="">_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a></pre></blockquote><br></div></div></span></body></html>