[asterisk-biz] CALEA

[Brian Fertig]

http://www.google.com/url?sa=t&ct=res&cd=1&url=http%3A%2F%2Fwww.calea.org%2F&ei=5a_sReyQCZreggTtzZGrCQ&usg=__6dGSAeKlpwbTwBL_Cq0afKdGcmw=&sig2=D_KSpv9saPaPY9BvRTrLug

To trunk that down..  www.calea.org

-- 
........::::::::::.........
Brian Fertig
Director of Engineering
Molten, Inc.
Delaware Office
Office 800.418.4380 x 160
Direct 302.338.9601

|-----Original Message-----
|From: asterisk-biz-bounces at lists.digium.com [mailto:asterisk-biz-
|bounces at lists.digium.com] On Behalf Of voiplist
|Sent: Monday, March 05, 2007 5:31 PM
|To: Commercial and Business-Oriented Asterisk Discussion
|Subject: Re: [asterisk-biz] CALEA
|
|Or maybe I should say... Is there a document somewhere that puts it
|all in plain English?
|
|
|
|On 3/5/07, voiplist <gotvoip at gmail.com> wrote:
|> Is there a beginners guide to CALEA somewhere?
|>
|>
|>
|> On 11/7/06, asterisk_help at iwishi.nu <asterisk_help at iwishi.nu> wrote:
|> > On Tue, 7 Nov 2006, Mike Hammett wrote:
|> > > How are you guys solving your CALEA compliance requirement?
|> > > Mike Hammett
|> >
|> > Hi Mike,
|> >
|> > Glad to see someone else ask the question.
|> >
|> > We have just completed our SSNI policy and filed that with the FCC.
|> > SSNI is "System Security and Network Integrity".  All service
|providers
|> > needed to file their written policies for the FCC to review before
|> > November 2nd, that was 5 days ago for those of you who haven't
|started
|> > yet.
|> >
|> > You can learn more at http://www.askcalea.net/
|> >
|> > At Astricon, I was unable to make the developers meeting, and when I
|asked
|> > other presenters later in the week about their plans for CALEA, I
|was
|> > basicly blown off I guess. I think many service providers are
|resisting
|> > regulation and ignoring the problems we are going to need to solve
|to
|> > remain legal.
|> >
|> > I need to work with our tech guys, but I suspect we are going to
|write a
|> > manager monitor to collect the events we need.  Any missing events
|or
|> > actions and we'll post a bounty for patches to Asterisk.
|> >
|> > Here's some references to what we're expected to log or collect for
|the
|> > feds.  http://www.askcalea.net/standards.html
|> >
|> > Anyone have access to the ATIS docs?
|> >
|> > Here's an outline of the basics.
|> >
|> > Originating call from a Surveillance Subject
|> > Call Termination to a Surveillance Subject
|> > Placing a Call on Hold
|> > Call Redirection (Forwarding?)
|> > Call Waiting
|> > Call Transfer
|> > Three-Way Calling
|> > Call Block
|> > Repeat Call
|> > Return Call
|> > 911 Emergency and N11 Services
|> > Mid-Call CODEC Change
|> > CallAnswer
|> > TerminationAttempt
|> > Registration events and deregistration and the why or how of it.
|> > _______________________________________________
|> > --Bandwidth and Colocation provided by Easynews.com --
|> >
|> > asterisk-biz mailing list
|> > To UNSUBSCRIBE or update options visit:
|> >    http://lists.digium.com/mailman/listinfo/asterisk-biz
|> >
|>
|_______________________________________________
|--Bandwidth and Colocation provided by Easynews.com --
|
|asterisk-biz mailing list
|To UNSUBSCRIBE or update options visit:
|   http://lists.digium.com/mailman/listinfo/asterisk-biz





"The information in this electronic mail ("e-mail") message may contain 
information that is confidential and/or privileged, or may otherwise be 
protected by work product or other legal rules. It is solely for the use 
of the individual(s) or the entity(ies) originally intended. Access to 
this electronic mail message by anyone else is unauthorized. If you are 
not the intended recipient, be advised that any unauthorized review, 
disclosure, copying, distribution or use of this information, or any 
action taken or omitted to be taken in reliance on it, is prohibited and 
may be unlawful. Please notify the sender immediately if you have received 
this electronic message by mistake, and destroy all copies of the original 
message."


"The sender believes that this e-mail and any attachments were free of any 
virus, worm, Trojan horse, malicious code and/or other contaminants when 
sent. E-mail transmissions cannot be guaranteed to be secure or 
error-free, so this message and its attachments could have been infected, 
corrupted or made incomplete during transmission. By reading the message 
and opening any attachments, the recipient accepts full responsibility for 
any viruses or other defects that may arise, and for taking remedial 
action relating to such viruses and other defects. Neither Molten Inc nor 
any of its affiliated entities is liable for any loss or damage arising in 
any way from, or for errors or omissions in the contents of, this message 
or its attachments."