And what is Molten, Inc (a computer company) doing with HIPPA? (<font size="-1">Health Insurance Portability and Accountability Act</font>)<br><br><div><span class="gmail_quote">On 3/6/07, <b class="gmail_sendername">Brian Fertig
</b> &lt;<a href="mailto:brian@molten.us">brian@molten.us</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I have no control over that.&nbsp;&nbsp;Its something we have to have for HIPA sorry
<br>list..<br><br>--<br>........::::::::::.........<br>Brian Fertig<br>Director of Engineering<br>Molten, Inc.<br>Delaware Office<br>Office 800.418.4380 x 160<br>Direct 302.338.9601<br><br>|-----Original Message-----<br>|From: 
<a href="mailto:asterisk-biz-bounces@lists.digium.com">asterisk-biz-bounces@lists.digium.com</a> [mailto:<a href="mailto:asterisk-biz-">asterisk-biz-</a><br>|bounces@<a href="http://lists.digium.com">lists.digium.com</a>] On Behalf Of C F
<br>|Sent: Monday, March 05, 2007 9:23 PM<br>|To: Commercial and Business-Oriented Asterisk Discussion<br>|Subject: Re: [asterisk-biz] CALEA<br>|<br>|Brian, Am i allowed to read this electronic mail (e-mail)? You seem to<br>
|include that annoying long disclaimer to the list on every email.<br>|While i am quite sure that the disclaimer gives you zero additional<br>|protection on this list, and i am not sure how much if any outside<br>|this list. When you use it on your private emails i dont really care
<br>|but on a list its quite annoying.<br>|<br>|On 3/5/07, Brian Fertig &lt;<a href="mailto:brian@molten.us">brian@molten.us</a>&gt; wrote:<br>|&gt;<br>|http://www.google.com/url?sa=t&amp;ct=res&amp;cd=1&amp;url=http%3A%2F%2Fwww.calea.or
<br>|g%2F&amp;ei=5a_sReyQCZreggTtzZGrCQ&amp;usg=__6dGSAeKlpwbTwBL_Cq0afKdGcmw=&amp;sig2=D<br>|_KSpv9saPaPY9BvRTrLug<br>|&gt;<br>|&gt; To trunk that down..&nbsp;&nbsp;<a href="http://www.calea.org">www.calea.org</a><br>|&gt;<br>|&gt; --
<br>|&gt; ........::::::::::.........<br>|&gt; Brian Fertig<br>|&gt; Director of Engineering<br>|&gt; Molten, Inc.<br>|&gt; Delaware Office<br>|&gt; Office 800.418.4380 x 160<br>|&gt; Direct 302.338.9601<br>|&gt;<br>|&gt; |-----Original Message-----
<br>|&gt; |From: <a href="mailto:asterisk-biz-bounces@lists.digium.com">asterisk-biz-bounces@lists.digium.com</a> [mailto:<a href="mailto:asterisk-biz-">asterisk-biz-</a><br>|&gt; |bounces@<a href="http://lists.digium.com">
lists.digium.com</a>] On Behalf Of voiplist<br>|&gt; |Sent: Monday, March 05, 2007 5:31 PM<br>|&gt; |To: Commercial and Business-Oriented Asterisk Discussion<br>|&gt; |Subject: Re: [asterisk-biz] CALEA<br>|&gt; |<br>|&gt; |Or maybe I should say... Is there a document somewhere that puts it
<br>|&gt; |all in plain English?<br>|&gt; |<br>|&gt; |<br>|&gt; |<br>|&gt; |On 3/5/07, voiplist &lt;<a href="mailto:gotvoip@gmail.com">gotvoip@gmail.com</a>&gt; wrote:<br>|&gt; |&gt; Is there a beginners guide to CALEA somewhere?
<br>|&gt; |&gt;<br>|&gt; |&gt;<br>|&gt; |&gt;<br>|&gt; |&gt; On 11/7/06, <a href="mailto:asterisk_help@iwishi.nu">asterisk_help@iwishi.nu</a> &lt;<a href="mailto:asterisk_help@iwishi.nu">asterisk_help@iwishi.nu</a>&gt;<br>
|wrote:<br>|&gt; |&gt; &gt; On Tue, 7 Nov 2006, Mike Hammett wrote:<br>|&gt; |&gt; &gt; &gt; How are you guys solving your CALEA compliance requirement?<br>|&gt; |&gt; &gt; &gt; Mike Hammett<br>|&gt; |&gt; &gt;<br>|&gt; |&gt; &gt; Hi Mike,
<br>|&gt; |&gt; &gt;<br>|&gt; |&gt; &gt; Glad to see someone else ask the question.<br>|&gt; |&gt; &gt;<br>|&gt; |&gt; &gt; We have just completed our SSNI policy and filed that with the<br>|FCC.<br>|&gt; |&gt; &gt; SSNI is &quot;System Security and Network Integrity&quot;.&nbsp;&nbsp;All service
<br>|&gt; |providers<br>|&gt; |&gt; &gt; needed to file their written policies for the FCC to review<br>|before<br>|&gt; |&gt; &gt; November 2nd, that was 5 days ago for those of you who haven&#39;t<br>|&gt; |started<br>|&gt; |&gt; &gt; yet.
<br>|&gt; |&gt; &gt;<br>|&gt; |&gt; &gt; You can learn more at <a href="http://www.askcalea.net/">http://www.askcalea.net/</a><br>|&gt; |&gt; &gt;<br>|&gt; |&gt; &gt; At Astricon, I was unable to make the developers meeting, and
<br>|when I<br>|&gt; |asked<br>|&gt; |&gt; &gt; other presenters later in the week about their plans for CALEA, I<br>|&gt; |was<br>|&gt; |&gt; &gt; basicly blown off I guess. I think many service providers are<br>|&gt; |resisting
<br>|&gt; |&gt; &gt; regulation and ignoring the problems we are going to need to<br>|solve<br>|&gt; |to<br>|&gt; |&gt; &gt; remain legal.<br>|&gt; |&gt; &gt;<br>|&gt; |&gt; &gt; I need to work with our tech guys, but I suspect we are going to
<br>|&gt; |write a<br>|&gt; |&gt; &gt; manager monitor to collect the events we need.&nbsp;&nbsp;Any missing<br>|events<br>|&gt; |or<br>|&gt; |&gt; &gt; actions and we&#39;ll post a bounty for patches to Asterisk.<br>|&gt; |&gt; &gt;
<br>|&gt; |&gt; &gt; Here&#39;s some references to what we&#39;re expected to log or collect<br>|for<br>|&gt; |the<br>|&gt; |&gt; &gt; feds.&nbsp;&nbsp;<a href="http://www.askcalea.net/standards.html">http://www.askcalea.net/standards.html
</a><br>|&gt; |&gt; &gt;<br>|&gt; |&gt; &gt; Anyone have access to the ATIS docs?<br>|&gt; |&gt; &gt;<br>|&gt; |&gt; &gt; Here&#39;s an outline of the basics.<br>|&gt; |&gt; &gt;<br>|&gt; |&gt; &gt; Originating call from a Surveillance Subject
<br>|&gt; |&gt; &gt; Call Termination to a Surveillance Subject<br>|&gt; |&gt; &gt; Placing a Call on Hold<br>|&gt; |&gt; &gt; Call Redirection (Forwarding?)<br>|&gt; |&gt; &gt; Call Waiting<br>|&gt; |&gt; &gt; Call Transfer
<br>|&gt; |&gt; &gt; Three-Way Calling<br>|&gt; |&gt; &gt; Call Block<br>|&gt; |&gt; &gt; Repeat Call<br>|&gt; |&gt; &gt; Return Call<br>|&gt; |&gt; &gt; 911 Emergency and N11 Services<br>|&gt; |&gt; &gt; Mid-Call CODEC Change
<br>|&gt; |&gt; &gt; CallAnswer<br>|&gt; |&gt; &gt; TerminationAttempt<br>|&gt; |&gt; &gt; Registration events and deregistration and the why or how of it.<br>|&gt; |&gt; &gt; _______________________________________________
<br>|&gt; |&gt; &gt; --Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br>|&gt; |&gt; &gt;<br>|&gt; |&gt; &gt; asterisk-biz mailing list<br>|&gt; |&gt; &gt; To UNSUBSCRIBE or update options visit:
<br>|&gt; |&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http://lists.digium.com/mailman/listinfo/asterisk-biz">http://lists.digium.com/mailman/listinfo/asterisk-biz</a><br>|&gt; |&gt; &gt;<br>|&gt; |&gt;<br>|&gt; |_______________________________________________
<br>|&gt; |--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br>|&gt; |<br>|&gt; |asterisk-biz mailing list<br>|&gt; |To UNSUBSCRIBE or update options visit:<br>|&gt; |&nbsp;&nbsp; <a href="http://lists.digium.com/mailman/listinfo/asterisk-biz">
http://lists.digium.com/mailman/listinfo/asterisk-biz</a><br>|&gt;<br>|&gt;<br>|&gt;<br>|&gt;<br>|&gt;<br>|&gt; &quot;The information in this electronic mail (&quot;e-mail&quot;) message may<br>|contain<br>|&gt; information that is confidential and/or privileged, or may otherwise
<br>|be<br>|&gt; protected by work product or other legal rules. It is solely for the<br>|use<br>|&gt; of the individual(s) or the entity(ies) originally intended. Access to<br>|&gt; this electronic mail message by anyone else is unauthorized. If you
<br>|are<br>|&gt; not the intended recipient, be advised that any unauthorized review,<br>|&gt; disclosure, copying, distribution or use of this information, or any<br>|&gt; action taken or omitted to be taken in reliance on it, is prohibited
<br>|and<br>|&gt; may be unlawful. Please notify the sender immediately if you have<br>|received<br>|&gt; this electronic message by mistake, and destroy all copies of the<br>|original<br>|&gt; message.&quot;<br>|&gt;<br>
|&gt;<br>|&gt; &quot;The sender believes that this e-mail and any attachments were free of<br>|any<br>|&gt; virus, worm, Trojan horse, malicious code and/or other contaminants<br>|when<br>|&gt; sent. E-mail transmissions cannot be guaranteed to be secure or
<br>|&gt; error-free, so this message and its attachments could have been<br>|infected,<br>|&gt; corrupted or made incomplete during transmission. By reading the<br>|message<br>|&gt; and opening any attachments, the recipient accepts full responsibility
<br>|for<br>|&gt; any viruses or other defects that may arise, and for taking remedial<br>|&gt; action relating to such viruses and other defects. Neither Molten Inc<br>|nor<br>|&gt; any of its affiliated entities is liable for any loss or damage
<br>|arising in<br>|&gt; any way from, or for errors or omissions in the contents of, this<br>|message<br>|&gt; or its attachments.&quot;<br>|&gt;<br>|&gt; _______________________________________________<br>|&gt; --Bandwidth and Colocation provided by 
<a href="http://Easynews.com">Easynews.com</a> --<br>|&gt;<br>|&gt; asterisk-biz mailing list<br>|&gt; To UNSUBSCRIBE or update options visit:<br>|&gt;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http://lists.digium.com/mailman/listinfo/asterisk-biz">http://lists.digium.com/mailman/listinfo/asterisk-biz
</a><br>|&gt;<br>|_______________________________________________<br>|--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br>|<br>|asterisk-biz mailing list<br>|To UNSUBSCRIBE or update options visit:
<br>|&nbsp;&nbsp; <a href="http://lists.digium.com/mailman/listinfo/asterisk-biz">http://lists.digium.com/mailman/listinfo/asterisk-biz</a><br><br><br><br>_______________________________________________<br>--Bandwidth and Colocation provided by 
<a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-biz mailing list<br>To UNSUBSCRIBE or update options visit:<br>&nbsp;&nbsp; <a href="http://lists.digium.com/mailman/listinfo/asterisk-biz">http://lists.digium.com/mailman/listinfo/asterisk-biz
</a><br></blockquote></div><br>