<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body 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>
<br>
Its a dangerous game, of not if but when they will come asking, and
if you have a solution in place before that time comes, since the
fines for non-compliance are extreme. <br>
<br>
<br>
Additionally, what you may do if you are using a reputable DID
provider who is a CLEC (not a reseller) is inquire with them about
them supporting CALEA, and see if they can fill this gap for you. I
know in the past when speaking with certain large national providers
on this topic (much may have changed since then) if they owned the
DID AND I Could route all outbound calls for the subscriber with the
warrant back to them, since they were the CLEC that the number was
actually owned by, I could deflect the warrants to them. Might be
worth looking into. <br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 01/18/2013 02:30 PM, Joshua Goldbard
wrote:<br>
</div>
<blockquote
cite="mid:FD4A91ABAD370D4383186A56320046BE083869E5@mbx022-w1-ca-9.exch022.domain.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>From: <a moz-do-not-send="true"
href="http://transition.fcc.gov/pshs/services/calea/">http://transition.fcc.gov/pshs/services/calea/</a></div>
<div><br>
</div>
<div>
<h2 style="margin: 0em; padding: 6px 10px 0px 1.5em; font-size:
11pt; font-family: Geneva, Arial, Helvetica, sans-serif; ">
CALEA Compliance for Packet Equipment, And Equipment for
Facilities-Based Broadband Internet Access Providers and
Providers of Interconnected VoIP</h2>
<div style="margin: 0em; padding: 0px 10px 12px 1.7em;
font-family: Geneva, Arial, Helvetica, sans-serif; font-size:
12px; line-height: 20.390625px; ">
All facilities-based broadband Internet access providers and
providers of interconnected VoIP service must ensure that
their services comply with CALEA upon launch. In the May 12,
2006 Commission order, the Commission found that section
107(c)(1) may not be used by entities seeking extensions for
equipment, facilities, and services deployed on or after
October 25, 1998 (the effective date of the CALEA section 103
and 105 requirements).</div>
</div>
<div>I believe you aren't subject to CALEA unless you're a
facilities-based CLEC/ILEC. I am not a lawyer, this is not legal
advice, but I don't think this applies to you. (Someone please
correct me if I'm mistaken).</div>
<br>
<div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: medium; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: -webkit-auto; text-indent:
0px; text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
Joshua Goldbard</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: medium; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: -webkit-auto; text-indent:
0px; text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
VP of Marketing, 2600hz</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: medium; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: -webkit-auto; text-indent:
0px; text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: medium; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: -webkit-auto; text-indent:
0px; text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
116 Natoma Street, Floor 2</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: medium; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: -webkit-auto; text-indent:
0px; text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
San Francisco, CA, 94104</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: medium; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: -webkit-auto; text-indent:
0px; text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
415.886.7923 | <a moz-do-not-send="true"
href="mailto:j@2600hz.com">j@2600hz.com</a></div>
<br class="Apple-interchange-newline" style="color: rgb(0, 0,
0); font-family: Helvetica; font-size: medium; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; ">
<span></span> </div>
<br>
<div>
<div>On Jan 18, 2013, at 2:16 PM, Nathan Anderson <<a
moz-do-not-send="true" href="mailto:nathana@fsr.com">nathana@fsr.com</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">Nope.<br>
<br>
-- Nathan <br>
<br>
-----Original Message-----<br>
From: Joshua Goldbard [<a class="moz-txt-link-freetext" href="mailto:j@">mailto:j@</a><a moz-do-not-send="true"
href="http://2600hz.com">2600hz.com</a>] <br>
Sent: Friday, January 18, 2013 2:03 PM<br>
To: Nathan Anderson<br>
Cc: <a moz-do-not-send="true"
href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a><br>
Subject: Re: [VoiceOps] CALEA for the small fry operator<br>
<br>
Are you a CLEC? <br>
<br>
Cheers,<br>
Joshua<br>
<br>
Joshua Goldbard<br>
VP of Marketing, 2600hz<br>
<br>
116 Natoma Street, Floor 2<br>
San Francisco, CA, 94104<br>
415.886.7923 | <a moz-do-not-send="true"
href="mailto:j@2600hz.com">j@2600hz.com</a><br>
<br>
<br>
On Jan 18, 2013, at 1:54 PM, Nathan Anderson <<a
moz-do-not-send="true" href="mailto:nathana@fsr.com">nathana@fsr.com</a>><br>
wrote:<br>
<br>
<br>
<span class="Apple-tab-span" style="white-space:pre"></span>We
are a small-ish, regional broadband ISP in the U.S. (inland
Washington and Idaho) that has also rolled out an
interconnected VoIP product over the past year. I'm trying to
wrestle through and understand what our responsibilities and
obligations are with regards to CALEA compliance at both the
legal and technical levels.<br>
<span class="Apple-tab-span" style="white-space:pre"></span><br>
<span class="Apple-tab-span" style="white-space:pre"></span>Confession
time: we did not purchase a commercial softswitch product. We
built our own solution on top of Asterisk. (I can already
hear the groans and feel the tangible disapproval.) We went
this route for cost reasons, yes, but more importantly we did
it because with a custom-engineered solution, we were able to
seamlessly integrate our new voice offering with our other
existing products when it comes to both provisioning and
billing, and this (I believe) leads to a better and more
uniform experience for our customers. For better or worse, we
are an ISP first and foremost, and an ITSP second, and
provisioning for the new product needed to conform to existing
practices rather than be an island unto itself, as so many
"turn-key" offerings are.<br>
<span class="Apple-tab-span" style="white-space:pre"></span><br>
<span class="Apple-tab-span" style="white-space:pre"></span>But
I recognize that going down this path has brought with it a
distinct disadvantage when it comes to solving the CALEA
complaince problem. Notably, there are no known CALEA
solutions for Asterisk of any stripe that I have been able to
find, and any discussion about Asterisk and CALEA seems to
have peaked around the time (2006-2007) that the feds
announced VoIP providers were going to have to bring
themselves into compliance, and then quickly faded after that.<br>
<span class="Apple-tab-span" style="white-space:pre"></span><br>
<span class="Apple-tab-span" style="white-space:pre"></span>Sure,
I could easily come up with something that would allow for
live or recorded call interception and/or delivery of CDR/CPNI
to law enforcement using existing tools already available to
me. What is unclear to me, though, is whether there is any
particular format or delivery mechanism for this data that the
law stipulates we follow. I know that there is an ANSI
standard, T1.678v2 (and the subsequent supplements), but of
course I have no access to that (200+ page) document without
paying the publisher hundreds of dollars for a copy. And even
if we got our hands on a copy, it sounds like it would be
prohibitively difficult to implement by ourselves.<br>
<span class="Apple-tab-span" style="white-space:pre"></span><br>
<span class="Apple-tab-span" style="white-space:pre"></span>Does
the law actually stipulate that T1.678 be followed, and are
you not in compliance with CALEA regulations unless you
specifically use a solution that is T1.678-compatible? Or is
the T1.678 standard simply recommended and preferred by LEAs?
I have seen discussion threads where other people have talked
about their "creative" solutions to CALEA compliance, which
include things such as proxying the RTP stream and having a
bank of E&M channels at the ready to mirror the audio to (<a
moz-do-not-send="true"
href="http://fonality.com/trixbox/forums/trixbox-forums/open-discussion/what-i-need-start-ip-phone-service-provider-business">http://fonality.com/trixbox/forums/trixbox-forums/open-discussion/what-i-need-start-ip-phone-service-provider-business</a>).
Do these people actually know if their solution gets a
passing grade, or are they taking a gamble?<br>
<span class="Apple-tab-span" style="white-space:pre"></span><br>
<span class="Apple-tab-span" style="white-space:pre"></span>Thanks,<br>
<span class="Apple-tab-span" style="white-space:pre"></span><br>
<span class="Apple-tab-span" style="white-space:pre"></span>--
<br>
<span class="Apple-tab-span" style="white-space:pre"></span>Nathan
Anderson<br>
<span class="Apple-tab-span" style="white-space:pre"></span>First
Step Internet, LLC<br>
<span class="Apple-tab-span" style="white-space:pre"></span><a
moz-do-not-send="true" href="mailto:nathana@fsr.com">nathana@fsr.com</a><br>
<span class="Apple-tab-span" style="white-space:pre"></span>_______________________________________________<br>
<span class="Apple-tab-span" style="white-space:pre"></span>VoiceOps
mailing list<br>
<span class="Apple-tab-span" style="white-space:pre"></span><a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
<span class="Apple-tab-span" style="white-space:pre"></span><a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<span class="Apple-tab-span" style="white-space:pre"></span><br>
<br>
<br>
</blockquote>
</div>
<br>
<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>
</body>
</html>