<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.lexblog.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
   <channel>
      <title>Telecom Law Monitor</title>
      <link>http://www.telecomlawmonitor.com/</link>
      <description>Washington D.C. Telecom Lawyer &amp; Attorney : Kelley Drye &amp; Warren Law Firm : New York, Chicago, Connecticut, New Jersey, Brussels</description>
      <language>en</language>
      <copyright>Copyright 2012</copyright>
      <lastBuildDate>Tue, 15 May 2012 08:04:35 -0500</lastBuildDate>
      <pubDate>Tue, 15 May 2012 08:04:35 -0500</pubDate>
      <generator>http://www.movabletype.org</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <feedburner:info uri="telecomlawmonitor" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://www.telecomlawmonitor.com/index.xml" /><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://www.telecomlawmonitor.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><feedburner:feedFlare href="http://www.plusmo.com/add?url=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://plusmo.com/res/graphics/fbplusmo.gif">Subscribe with Plusmo</feedburner:feedFlare><feedburner:feedFlare href="http://www.thefreedictionary.com/_/hp/AddRSS.aspx?http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://img.tfd.com/hp/addToTheFreeDictionary.gif">Subscribe with The Free Dictionary</feedburner:feedFlare><feedburner:feedFlare href="http://www.bitty.com/manual/?contenttype=rssfeed&amp;contentvalue=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.bitty.com/img/bittychicklet_91x17.gif">Subscribe with Bitty Browser</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsalloy.com/?rss=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.newsalloy.com/subrss3.gif">Subscribe with NewsAlloy</feedburner:feedFlare><feedburner:feedFlare href="http://www.live.com/?add=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://tkfiles.storage.msn.com/x1piYkpqHC_35nIp1gLE68-wvzLZO8iXl_JMledmJQXP-XTBOLfmQv4zhj4MhcWEJh_GtoBIiAl1Mjh-ndp9k47If7hTaFno0mxW9_i3p_5qQw">Subscribe with Live.com</feedburner:feedFlare><feedburner:feedFlare href="http://mix.excite.eu/add?feedurl=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://image.excite.co.uk/mix/addtomix.gif">Subscribe with Excite MIX</feedburner:feedFlare><feedburner:feedFlare href="http://download.attensa.com/app/get_attensa.html?feedurl=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.attensa.com/blogs/attensa/WindowsLiveWriter/BadgeredintoBadges_10C02/attensa_feed_button5.gif">Subscribe with Attensa for Outlook</feedburner:feedFlare><feedburner:feedFlare href="http://www.webwag.com/wwgthis.php?url=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.webwag.com/images/wwgthis.gif">Subscribe with Webwag</feedburner:feedFlare><feedburner:feedFlare href="http://www.podcastready.com/oneclick_bookmark.php?url=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.podcastready.com/images/podcastready_button.gif">Subscribe with Podcast Ready</feedburner:feedFlare><feedburner:feedFlare href="http://www.flurry.com/pushRssFeed.do?r=fb&amp;url=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.flurry.com/images/flurry_rss_logo2.gif">Subscribe with Flurry</feedburner:feedFlare><feedburner:feedFlare href="http://www.wikio.com/subscribe?url=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.wikio.com/shared/img/add2wikio.gif">Subscribe with Wikio</feedburner:feedFlare><feedburner:feedFlare href="http://www.dailyrotation.com/index.php?feed=http%3A%2F%2Fwww.telecomlawmonitor.com%2Findex.xml" src="http://www.dailyrotation.com/rss-dr2.gif">Subscribe with Daily Rotation</feedburner:feedFlare><item>
         <title>Commissioners Rosenworcel and Pai Take Office</title>
         <description>&lt;p&gt;One week after Senate confirmation, new FCC Commissioners Jessica Rosenworcel and Ajit Pai were sworn in to office.&amp;nbsp; With these appointments, the FCC reaches its full complement of commissioners for the &lt;a href="http://www.telecomlawmonitor.com/2011/05/articles/fcc/fcc-commissioner-baker-joining-comcastnbcu/"&gt;first time in nearly a year&lt;/a&gt;.&amp;nbsp; Both Commissioners released short statements expressing excitement to begin their tenures on the FCC.&amp;nbsp; The statements are available &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Rosenworcel.pdf"&gt;here&lt;/a&gt; and &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Pai.pdf"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;They will get their first opportunity to comment publicly as commissioners tomorrow, when the Senate Commerce Committee will hold an oversight hearing.&amp;nbsp;&amp;nbsp;Their first full Commission meeting will be May 24th.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/bw5C2YqMwNk" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/bw5C2YqMwNk/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/05/articles/fcc/commissioners-rosenworcel-and-pai-take-office/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">FCC</category>
         <pubDate>Tue, 15 May 2012 07:53:04 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/05/articles/fcc/commissioners-rosenworcel-and-pai-take-office/</feedburner:origLink></item>
            <item>
         <title>VoIP Outage Reporting Obligations One Step Closer to Implementation</title>
         <description>&lt;p&gt;This post was co-written by &lt;a href="http://www.kelleydrye.com/attorneys/randall_sifers"&gt;Randy Sifers&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In February, the FCC adopted new outage reporting rules for interconnected VoIP providers.&amp;nbsp; Our story and our advisory on the new rules are available at &lt;a href="http://www.telecomlawmonitor.com/2012/03/articles/fcc/fcc-extends-outage-reporting-requirements-to-all-interconnected-voip-providers/"&gt;this link&lt;/a&gt;.&amp;nbsp; At the time, we told you that the rules would become effective 90 days after OMB approved the new information collection.&lt;/p&gt;
&lt;p&gt;On Friday, the new outage reporting rules took one step closer to becoming effective.&amp;nbsp; No,&amp;nbsp;OMB has not yet approved the rules.&amp;nbsp; However, the FCC &lt;a href="http://www.telecomlawmonitor.com/uploads/file/VoIP Outage Reporting FR Notice.pdf"&gt;published notice&lt;/a&gt;&amp;nbsp;in the &lt;em&gt;Federal Register&lt;/em&gt; of its Report and Order extending the network outage reporting requirements to interconnected VoIP service providers.&amp;nbsp; Friday&amp;rsquo;s publication was made to comply with OMB information collection requirements. The FCC will make a future publication announcing the effective date of the new rule when OMB approval is obtained.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This notice does have the effect of starting the clock for appeals or petitions for reconsideration of the new outage reporting rules.&amp;nbsp; Interested parties may file for reconsideration within 30 days of the notice; petitioners may appeal the decision within 60 days.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/oGbbLyIuszU" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/oGbbLyIuszU/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/04/articles/voip/voip-outage-reporting-obligations-one-step-closer-to-implementation/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Compliance Filing</category><category domain="http://www.telecomlawmonitor.com/articles">VoIP</category><category domain="http://www.telecomlawmonitor.com/tags">outage reporting</category>
         <pubDate>Mon, 30 Apr 2012 07:20:52 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/04/articles/voip/voip-outage-reporting-obligations-one-step-closer-to-implementation/</feedburner:origLink></item>
            <item>
         <title>FCC Settles Slamming Case with Unusual Remedies</title>
         <description>&lt;p&gt;Slamming cases are &lt;a href="http://www.telecomlawmonitor.com/2010/05/articles/enforcement/blast-from-the-past-long-distance-carrier-faces-14-million-fine-for-slamming/"&gt;a rarity&lt;/a&gt; these days, but this settlement is noteworthy not because it involves slamming, but because of the unusual remedies the FCC required in its consent decree.&lt;/p&gt;
&lt;p&gt;The case involves two Notices of Apparent Liability issued to companies now under common ownership, &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Horizon NAL.pdf"&gt;Horizon Telecom, Inc.&lt;/a&gt; and &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Reduced Rate LD NAL.pdf"&gt;Reduced Rate Long Distance, LLC&lt;/a&gt;. &amp;nbsp;In &lt;em&gt;Horizon&lt;/em&gt;, the Commission proposed a fine of $5,084,000 for slamming. &amp;nbsp;In &lt;em&gt;Reduced Rate&lt;/em&gt;, the Commission proposed a fine of $8,000 for failing to respond to two informal consumer complaints. &amp;nbsp;Both NALs were issued in 2008. &amp;nbsp;Yesterday, the Enforcement Bureau released a &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Horizon Reduced Rate Consent Decree.pdf"&gt;consent decree&lt;/a&gt; settling the two cases.&lt;/p&gt;
&lt;p&gt;What is so unusual about the settlement?&lt;/p&gt;&lt;ul&gt;
    &lt;li&gt;For starters, the settlement amount is only $53,000. &amp;nbsp; This is a significant reduction from the over $5 million in fines proposed against the two companies. &amp;nbsp;(Though not quite &lt;a href="http://www.telecomlawmonitor.com/2010/09/articles/enforcement/fcc-settles-100000-proposed-fine-for-only-250/"&gt;this significant&lt;/a&gt;.) &amp;nbsp;The Order notes that the payment &amp;quot;is reduced from the proposed NAL amounts based upon their demonstrated inability to pay.&amp;quot;&lt;/li&gt;
    &lt;li&gt;Second, Horizon, which had sold its customer base to Reduced Rate in 2007, agreed never to provide telecommunications services again. &amp;nbsp;Not since the Fletcher Companies in 1997 have I seen a telecommunications carrier barred from the market.&lt;/li&gt;
    &lt;li&gt;Third, Reduced Rate's compliance plan requires outside counsel review of its materials. &amp;nbsp;The consent decree states that Reduced Rate &amp;quot;shall submit [its Policy Manual, sales scripts, TPV scripts and other marketing materials] to legal counsel of its own designation for review and editing ...&amp;quot; &amp;nbsp;The order further requires that such counsel &amp;quot;shall have experience with federal telecommunications and consumer protection laws, including the law relating to fraudulent, deceptive, unconscionable, and unfair acts or practices.&amp;quot; &amp;nbsp;To our knowledge, this is the first time the FCC has ever &lt;u&gt;required&lt;/u&gt;&amp;nbsp;a regulated entity to obtain counsel. &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;Finally, although not unprecedented, the consent decree requires Horizon and Reduced Rate to self-report non-compliance with the consent decree within 30 days. &amp;nbsp;Such self-reporting obligations have appeared in a few consent decrees in the past year or so (though not in the &lt;a href="http://www.telecomlawmonitor.com/2012/03/articles/fcc/verizon-and-verizon-wireless-pay-200000-to-settle-outage-reporting-investigations/"&gt;Verizon and Verizon Wireless consent decrees&lt;/a&gt; last month). &amp;nbsp;It's not quite a trend, but it is something worth monitoring in the future. &amp;nbsp;(That's what we're here for).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/Uk2csHWV-Ww" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/Uk2csHWV-Ww/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/04/articles/enforcement/fcc-settles-slamming-case-with-unusual-remedies/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Enforcement</category><category domain="http://www.telecomlawmonitor.com/tags">Horizon Telecom, Inc.</category><category domain="http://www.telecomlawmonitor.com/tags">Reduced Rate Long Distance, LLC</category><category domain="http://www.telecomlawmonitor.com/tags">slamming</category>
         <pubDate>Fri, 06 Apr 2012 08:53:08 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/04/articles/enforcement/fcc-settles-slamming-case-with-unusual-remedies/</feedburner:origLink></item>
            <item>
         <title>Verizon and Verizon Wireless Pay $200,000 to Settle Outage Reporting Investigations</title>
         <description>&lt;p&gt;&lt;em&gt;&lt;a href="http://www.kelleydrye.com/attorneys/randall_sifers"&gt;Randy Sifers&lt;/a&gt; contributed to this blog post. &lt;/em&gt;&lt;br /&gt;
&lt;br /&gt;
On March 14, 2012, the FCC released two consent decrees settling investigations into Verizon&amp;rsquo;s and Verizon Wireless&amp;rsquo;s outage reporting practices.  Collectively, the two affiliates will pay $200,000 to resolve a Notice of Apparent Liability for filing inaccurate outage reports and possibly other violations.  The release of these two settlements confirms that the Enforcement Bureau views the filing of inaccurate or incomplete network outage reports, not just the failure to file outage reports, as significant violations of the Communications Act.&lt;/p&gt;&lt;p&gt;The cases involve Verizon and Verizon Wireless.  In July 2009, Verizon experienced a reportable network outage and submitted a timely report concerning that outage.  In July 2010, the FCC issued a &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Verizon NAL_03_16_12 post.pdf"&gt;Notice of Apparent Liability&lt;/a&gt; against Verizon for failing to file a true, complete and accurate outage report regarding a significant disruption in service.  The Bureau proposed a monetary forfeiture of $25,000.  Subsequently, in March 2011, the Bureau issued a letter of inquiry to Verizon, expanding its investigation into Verizon&amp;rsquo;s compliance with reporting requirements.  In the &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Verizon Consent Decree_03_16_12 post(1).pdf"&gt;Consent Decree &lt;/a&gt;released on Wednesday, Verizon agreed to pay $90,000 to resolve the investigation.&lt;/p&gt;
&lt;p&gt;In the other investigation, the Bureau first issued a letter of inquiry in June 2008, directing Verizon Wireless to submit a sworn written response to a series of questions relating to Verizon Wireless&amp;rsquo;s compliance with the Commission&amp;rsquo;s network outage reporting rules.  Verizon Wireless submitted a timely response and, in response, the Bureau subsequently issued five follow-up letters of inquiry over the September 2008 through October 2009 time period.  Because no notice of inquiry was issued, it is not clear whether the Verizon Wireless investigation involved failure to report or the filing of inaccurate or incomplete reports, or both types of infractions.  But in the &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Verizon Wireless Consent Decree_03_16_12 post.pdf"&gt;Consent Decree&lt;/a&gt; released on Wednesday, Verizon Wireless agreed to pay $110,000 to resolve the investigation.&lt;/p&gt;
&lt;p&gt;Both consent decrees contain provisions requiring Verizon and Verizon Wireless to develop a compliance plan, designate a compliance officer, to perform training of its personnel, to file compliance reports, and to report future violations to the FCC.  In addition, the Verizon decree requires it to modify its existing processes for gathering, analyzing, and reporting information about its network outages particularly as they relate to public safety answering points.  The Verizon decree does not indicate how many outages were involved, but nothing suggests that it was more than one.&lt;/p&gt;
&lt;p&gt;Because the FCC received substantially more than the amount it originally proposed in the Verizon NAL, it appears that the Bureau found additional potential violations in its subsequent investigation.  In a case settled in August 2011, &lt;a href="http://www.telecomlawmonitor.com/2011/08/articles/enforcement/alpheus-settles-outage-reporting-nal-for-55000/"&gt;Alpheus Communications&lt;/a&gt; agreed to pay $55,000 for failing to timely file outage reports.  &lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/PAIGNjqcvxA" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/PAIGNjqcvxA/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/03/articles/fcc/verizon-and-verizon-wireless-pay-200000-to-settle-outage-reporting-investigations/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">FCC</category><category domain="http://www.telecomlawmonitor.com/tags">Verizon</category><category domain="http://www.telecomlawmonitor.com/tags">Verizon Wireless</category><category domain="http://www.telecomlawmonitor.com/tags">outage reporting</category>
         <pubDate>Fri, 16 Mar 2012 09:00:11 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/03/articles/fcc/verizon-and-verizon-wireless-pay-200000-to-settle-outage-reporting-investigations/</feedburner:origLink></item>
            <item>
         <title>FCC Releases 2012 Universal Service Revenue Reporting Worksheet</title>
         <description>&lt;p&gt;As it does every year, the FCC released its update to the annual Form 499-A.&amp;nbsp; The Form 499-A is used to report revenues for purposes of the federal Universal Service Fund and also for calculating associated revenue-based contribution obligations such as TRS, NANP, LNP and FCC Regulatory Fees.&amp;nbsp; The &lt;a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2012/db0305/DA-12-337A1.pdf"&gt;Public Notice&lt;/a&gt; describes changes to the form, primarily to implement&amp;nbsp;the new requirement that non-interconnected VoIP providers contribute to the TRS fund.&amp;nbsp; (Non-interconnected VoIP providers were &lt;a href="http://www.telecomlawmonitor.com/2011/12/articles/compliance-filing/reminder-noninterconnected-voip-providers-must-register-by-december-31/"&gt;required to register with USAC&lt;/a&gt; for this purpose by December 31, 2011.)&lt;/p&gt;
&lt;p&gt;The&amp;nbsp;2012 Form 499-A&amp;nbsp;has been posted on USAC's website.&amp;nbsp; Go to &amp;quot;universal service links&amp;quot; in our Resource Center on the right-hand side of this page for the USAC Forms page.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;REMINDER:&lt;/strong&gt;&amp;nbsp;&amp;nbsp;Kelley Drye will discuss these changes, important developments in USF audits and other topics at our &lt;a href="http://www.telecomlawmonitor.com/2012/02/articles/kelley-drye/please-join-us-for-kelley-dryes-3rd-annual-usf-update-webinar/"&gt;3rd Annual USF Update Webinar&lt;/a&gt; next week.&amp;nbsp;&amp;nbsp;This is our most&amp;nbsp;popular webinar of the year.&amp;nbsp; Please register today.&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/Gr_upODiL7M" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/Gr_upODiL7M/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/03/articles/universal-service-fund/fcc-releases-2012-universal-service-revenue-reporting-worksheet/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Compliance Filing</category><category domain="http://www.telecomlawmonitor.com/tags">Form 499-A</category><category domain="http://www.telecomlawmonitor.com/tags">TRS</category><category domain="http://www.telecomlawmonitor.com/tags">Telecommunications Relay Service</category><category domain="http://www.telecomlawmonitor.com/articles">Universal Service Fund</category>
         <pubDate>Tue, 06 Mar 2012 08:48:16 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/03/articles/universal-service-fund/fcc-releases-2012-universal-service-revenue-reporting-worksheet/</feedburner:origLink></item>
            <item>
         <title>FCC Extends Outage Reporting Requirements To All Interconnected VoIP Providers</title>
         <description>&lt;p&gt;On February 21, 2012, the Federal Communications Commission issued a Report and Order (&amp;quot;Order&amp;quot;) adopting outage reporting requirements for both facilities-based and &lt;em&gt;non-facilities-based&lt;/em&gt; interconnected Voice over Internet Protocol (&amp;quot;VoIP&amp;quot;) service providers on a mandatory basis in order to further ensure reliable 9-1-1 service.  Outage notification and reporting requirements currently apply to a variety of voice providers, including wireline carriers, CMRS providers, cable companies, and satellite providers.  The Commission's final action was narrower than had been first suggested in 2011, when the FCC also proposed to extend outage reporting requirements to providers of broadband Internet services.  In short, interconnected VoIP providers will be subject to notification and reporting requirements only in the event of &lt;em&gt;complete loss of service&lt;/em&gt;.  Their reporting obligations do not extend to situations where service is technically available but technical conditions effectively prevent communication.  Rather, the FCC deferred action on performance degradation thresholds for measuring an outage of interconnected VoIP service and all action relative to outages of broadband Internet services.  Finally, the Commission clarified that Part 4 of its rules relating to outage reporting applies to voice services provided using new wireless spectrum bands.&lt;/p&gt;
&lt;p&gt;Click &lt;a href="http://www.kelleydrye.com/publications/client_advisories/0727"&gt;here&lt;/a&gt; to read the full Kelley Drye Client Advisory.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/dB03NKPikhk" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/dB03NKPikhk/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/03/articles/fcc/fcc-extends-outage-reporting-requirements-to-all-interconnected-voip-providers/</guid>
         <category domain="http://www.telecomlawmonitor.com/tags">CRMS</category><category domain="http://www.telecomlawmonitor.com/articles">FCC</category><category domain="http://www.telecomlawmonitor.com/articles">VoIP</category>
         <pubDate>Thu, 01 Mar 2012 15:33:58 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/03/articles/fcc/fcc-extends-outage-reporting-requirements-to-all-interconnected-voip-providers/</feedburner:origLink></item>
            <item>
         <title>Please Join Us for Kelley Drye's 3rd Annual USF Update Webinar</title>
         <description>&lt;p&gt;With the Universal Service Fund continuing to grow and the USF contribution factor skyrocketing to nearly 18%, the federal Universal Service Fund remains a critical area for all telecommunications providers. Customers increasingly are focusing on the USF surcharge in negotiations, and the competitive consequences of over- or under- reporting USF directly affect the company&amp;rsquo;s bottom line.&lt;br /&gt;
&lt;br /&gt;
In this annual webinar, Kelley Drye will walk you through the USF changes you need to know, with an eye toward what to expect in 2012. We also will discuss the audit and appeal process in detail, including the differences between USAC and Inspector General audits. Our speakers will offer analysis and practical advice based on front line experience in audits and appeals, and years of providing compliance and enforcement advice in this area. &lt;br /&gt;
&lt;br /&gt;
The following topics will be addressed:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;The 2012 USF Reform Agenda -- High Cost (CAF) and Low-Income (Lifeline)&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;Changes to the 2012 Form 499A and instructions&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;Significant USF Appeals in 2011&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
    &lt;li&gt;Developments in the USF Audit and FCC Appeal Process&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Kelley Drye Speakers:&amp;nbsp;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.kelleydrye.com/attorneys/steven_augustino"&gt;Steve Augustino&lt;/a&gt;, Partner &lt;br /&gt;
&lt;a href="http://www.kelleydrye.com/attorneys/john_heitmann"&gt;John Heitmann&lt;/a&gt;, Partner&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;When:&lt;/strong&gt;&amp;nbsp;&lt;br /&gt;
March 13, 2012, 12:00PM - 1:00 PM&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Where:&lt;/strong&gt;&amp;nbsp;&lt;br /&gt;
Webinar&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;RSVP:&lt;/strong&gt;&amp;nbsp; &lt;br /&gt;
This webinar is free of charge. Presentation slides and a recording of the webinar will be available to registrants. Email &lt;a href="javascript:location.href='mailto:'+String.fromCharCode(100,99,101,118,101,110,116,115)+'?subject=RSVP%20for%20USF%20Update%20Webinar'"&gt;dcevents@kelleydrye.com&lt;/a&gt; or contact Cassidy Russell at 202.342.8400.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/pcUlSK499Cc" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/pcUlSK499Cc/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/kelley-drye/please-join-us-for-kelley-dryes-3rd-annual-usf-update-webinar/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Kelley Drye</category>
         <pubDate>Tue, 28 Feb 2012 17:37:08 -0500</pubDate>
         <dc:creator>Steve Augustino &amp;amp; John Heitmann</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/kelley-drye/please-join-us-for-kelley-dryes-3rd-annual-usf-update-webinar/</feedburner:origLink></item>
            <item>
         <title>Reminder:  Annual CPNI Certification Due March 1</title>
         <description>&lt;p&gt;All telecommunications carriers and interconnected VoIP providers must file an annual report certifying their compliance with the Federal Communications Commission&amp;rsquo;s (FCC) rules regarding Customer Proprietary Network Information (CPNI). &amp;nbsp;The report covers calendar year 2011 and must be filed with the FCC by March 1, 2012. &amp;nbsp;Providers may file CPNI certifications via an FCC web application or via ECFS, mail or hand delivery.&lt;/p&gt;
&lt;p&gt;The FCC&amp;rsquo;s Enforcement Bureau actively enforces the filing requirement, and &lt;a href="http://www.telecomlawmonitor.com/2011/03/articles/cpni/fcc-proposes-new-cpni-fines/"&gt;proposes fines for failure to file the certification &lt;/a&gt;at approximately this time every year. &amp;nbsp;Any company that submits USF revenue reports should ensure that it is in compliance with the CPNI certification requirement.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/Y8Dblg-sAO0" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/Y8Dblg-sAO0/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/cpni/reminder-annual-cpni-certification-due-march-1/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">CPNI</category><category domain="http://www.telecomlawmonitor.com/articles">Compliance Filing</category><category domain="http://www.telecomlawmonitor.com/articles">Enforcement</category>
         <pubDate>Sun, 26 Feb 2012 14:16:40 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/cpni/reminder-annual-cpni-certification-due-march-1/</feedburner:origLink></item>
            <item>
         <title>Insights from Kelley Drye's 4th Annual Privacy Seminar</title>
         <description>&lt;p&gt;On February 16, 2012, Kelley Drye &amp;amp; Warren LLP hosted the seminar  and audiocast, &amp;ldquo;Privacy in 2012: What to Watch Regarding COPPA, Mobile  Apps, and Evolving Law Enforcement and Public Policy Trends.&amp;rdquo; The  seminar highlighted regulatory and legislative developments in privacy  and information security during the past year, with an emphasis on  children's online privacy and mobile applications.&lt;/p&gt;
&lt;p&gt;&lt;img hspace="5" height="110" align="right" width="201" vspace="5" src="http://www.adlawaccess.com/uploads/image/priv_2012_facebookbut_v1(1).jpg" alt="" /&gt;Peter  Swire, a professor at The Ohio State University Michael E. Moritz  College of Law and a Senior Fellow with the Center for American  Progress, opened the seminar with a keynote address that gave historical  context to the most recent regulatory efforts addressing consumer  privacy. Professor Swire&amp;rsquo;s remarks were followed by two panel sessions  that included six experts representing key industry representatives and  the federal agencies integral to recent privacy initiatives. The first  panel discussed children's online privacy and the Federal Trade  Commission&amp;rsquo;s proposed revisions to the Children's Online Privacy  Protection Rule. The second panel discussed various consumer privacy  enforcement and regulatory initiatives relating to mobile apps.&lt;/p&gt;
&lt;p&gt;For more on the seminar, including a &lt;a href="http://www.kelleydrye.com/publications/client_advisories/0725"&gt;synopsis of&amp;nbsp;key takeaways&lt;/a&gt;, see the Kelley Drye client advisory. An &lt;a href="http://w.on24.com/r.htm?e=395981&amp;amp;s=1&amp;amp;k=9F1BB2DDC43885E4CD98A547DF2C3B2D"&gt;audio recording &lt;/a&gt;of the full program is also available.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/GUryUqLveb0" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/GUryUqLveb0/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/kelley-drye/insights-from-kelley-dryes-4th-annual-privacy-seminar/</guid>
         <category domain="http://www.telecomlawmonitor.com/tags">COPPA</category><category domain="http://www.telecomlawmonitor.com/tags">Federal Trade Commission</category><category domain="http://www.telecomlawmonitor.com/articles">Kelley Drye</category><category domain="http://www.telecomlawmonitor.com/articles">Mobile Marketing</category><category domain="http://www.telecomlawmonitor.com/tags">Privacy and Information Security</category><category domain="http://www.telecomlawmonitor.com/tags">mobile apps</category>
         <pubDate>Thu, 23 Feb 2012 10:01:08 -0500</pubDate>
         <dc:creator>John J. Heitmann</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/kelley-drye/insights-from-kelley-dryes-4th-annual-privacy-seminar/</feedburner:origLink></item>
            <item>
         <title>Interconnected VoIP Providers Required to Report Outages</title>
         <description>&lt;p&gt;&lt;a href="http://www.telecomlawmonitor.com/2012/02/articles/voip/voip-outage-reporting-obligations-to-be-adopted-at-february-15-fcc-meeting/"&gt;As we've discussed&lt;/a&gt;, today the FCC adopted rules to require interconnected VoIP providers to report network outages to the FCC.&amp;nbsp; The text of the FCC's order has not been released, but the order adopts a &lt;a href="http://www.telecomlawmonitor.com/2011/05/articles/compliance-filing/fcc-proposes-to-require-interconnected-voip-and-broadband-service-providers-to-file-outage-reports/"&gt;much narrower outage reporting requirement&lt;/a&gt; than originally proposed.&amp;nbsp; Under the new rules, interconnected VoIP providers will be required to report &amp;quot;hard&amp;quot; outages -- inabilities to complete calls -- that meet thresholds also applicable to traditional telecom services.&amp;nbsp; This decision continues the trend to treat interconnected VoIP the same as traditional TDM voice services, at least with respect to its obligations.&lt;/p&gt;&lt;p&gt;According to the &lt;a href="http://www.telecomlawmonitor.com/uploads/file/VoIP Outage Reporting press release.pdf"&gt;Public Notice&lt;/a&gt;, the Report and Order &amp;quot;means that interconnected VoIP service providers will be obligated to report significant service outages to the FCC.&amp;quot;&amp;nbsp; The Public Notice also promises that the Report and Order &amp;quot;defines outage reporting for interconnected VoIP service, establishes reporting criteria and thresholds, and discusses how the reporting process should work, what information should be reported, and confidential treatment of the outage reports.&amp;quot;&amp;nbsp; Details on these obligations will not be available until the text of the order is released.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Importantly, the FCC&amp;nbsp;also significantly narrowed the scope of the rules that it initially proposed.&amp;nbsp; The FCC deferred action on a number of questions, including the possibility of setting thresholds for reporting outages of broadband Internet service, and measurements for outages of both interconnected VoIP and broadband Internet services based on performance degradation, as opposed to complete service outage.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Significant Enforcement Penalties May Apply.&lt;/u&gt;&lt;/strong&gt;&amp;nbsp; Meanwhile, interconnected VoIP providers should take note of these rules. In the past, the FCC has set significant fines for failing to file the required outage reports.&amp;nbsp; It has proposed a base forfeiture of $40,000 for failing to file the Electronic Notification, $20,000 for failing to file the subsequent Outage Reports and $25,000 for filing incomplete or inaccurate reports.&amp;nbsp; Presumably, the same fines will apply, but only after the &lt;a href="http://www.telecomlawmonitor.com/2010/10/articles/enforcement/interconnected-voip-providers-getting-one-free-bite/"&gt;VoIP provider first receives a citation&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/xFVpS2lNnSE" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/xFVpS2lNnSE/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/voip/interconnected-voip-providers-required-to-report-outages/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Broadband</category><category domain="http://www.telecomlawmonitor.com/articles">Compliance Filing</category><category domain="http://www.telecomlawmonitor.com/articles">VoIP</category><category domain="http://www.telecomlawmonitor.com/tags">outage reporting</category>
         <pubDate>Wed, 15 Feb 2012 14:42:03 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/voip/interconnected-voip-providers-required-to-report-outages/</feedburner:origLink></item>
            <item>
         <title>FCC Releases Comprehensive Low-Income Program Reform</title>
         <description>&lt;p&gt;The Federal Communications Commission (&amp;quot;FCC&amp;quot; or &amp;quot;Commission&amp;quot;) released an Order on February 6, 2012 to comprehensively reform the low-income program of the Universal Service Fund to eliminate Link Up in non-Tribal areas; impose uniform eligibility, certification and verification requirements in part through the use of duplicates and eligibility databases; begin the process of modernizing the program to shift to supporting broadband and constrain the growth of the $2.1 billion low-income fund by $200 million in 2012 and by an estimated $2 billion over the next three years.  Many of the new rules will be effective 30 days after publication of the Order in the Federal Register, however, there will be important deadlines for eligible telecommunications carriers (&amp;quot;ETCs&amp;quot;) throughout the year.  At the same time, the FCC released a Further Notice of Proposed Rulemaking (&amp;quot;FNPRM&amp;quot;) seeking comment on a number of issues presented by its reform of the program.  Comments and reply comments on the issues raised in the FNPRM are due 30 days and 60 days, respectively, after publication of the FNPRM in the Federal Register.&lt;/p&gt;
&lt;p&gt;Click &lt;a href="http://www.kelleydrye.com/email/ADVISORY_comprehensive_low-income_reform_v1.pdf"&gt;here&lt;/a&gt; to read the Kelley&amp;nbsp;Drye Client Advisory outlining the entire Order.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/1AvBE4cSGoQ" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/1AvBE4cSGoQ/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/fcc/fcc-releases-comprehensive-lowincome-program-reform/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">FCC</category>
         <pubDate>Tue, 14 Feb 2012 17:32:24 -0500</pubDate>
         <dc:creator>John Heitmann</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/fcc/fcc-releases-comprehensive-lowincome-program-reform/</feedburner:origLink></item>
            <item>
         <title>Tidbits from the FCC's Proposed Budget</title>
         <description>&lt;p&gt;Yesterday, the FCC released its proposed budget for fiscal year 2013 (beginning in October 2012).&amp;nbsp; The budget offers a few interesting insights into the balance of the FCC's functions.&amp;nbsp; It also offers a preview of what to expect with the FCC's regulatory fees, which are due in September of each year.&amp;nbsp; See below for more.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;&lt;u&gt;FCC Proposed Budget&lt;/u&gt;&lt;/strong&gt;.&amp;nbsp; The FCC released its &lt;a href="http://www.telecomlawmonitor.com/uploads/file/FCC 2013 proposed budget.pdf"&gt;proposed FY 2013 budget&lt;/a&gt; yesterday.&amp;nbsp; It also released a &lt;a href="http://www.telecomlawmonitor.com/uploads/file/FCC 2013 budget news release.pdf"&gt;press release&lt;/a&gt; highlighting that the budget will, among other things, promote its efforts to &amp;quot;accelerate broadband deployment&amp;quot; and to implement reforms to the Universal Service Fund programs.&lt;/p&gt;
&lt;p&gt;A few highlights relevant to the areas we cover in this blog:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Enforcement is the FCC's largest bureau.&lt;/u&gt;&lt;/strong&gt;&amp;nbsp; The budget proposes an Enforcement Bureau of 299 FTEs, 15% of the total FTEs in the Commission.&amp;nbsp; Enforcement is largest bureau, larger than Wireless Telecom (232 FTEs) and&amp;nbsp;Media (213 FTEs).&amp;nbsp; The Wireline Competition Bureau is proposed to have only 170 FTEs, which is smaller than the Consumer &amp;amp; Governmental Affairs Bureau (195 FTEs).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Twice as many employees work on &amp;quot;competition and innovation&amp;quot; in wireless than in the Wireline Competition Bureau.&lt;/u&gt;&lt;/strong&gt;&amp;nbsp; The budget distributes the number of FTEs by goal identified by the FCC.&amp;nbsp; According to the distribution, in FY 2012 (the current year), Wireless Telecom has 143 FTEs working on &amp;quot;competition and innovation,&amp;quot; while the Wireline Competition Bureau has roughly half that amount, 77 FTEs.&amp;nbsp; For FY 2013, the budget restates the goals somewhat, but Wireless Telecom will have 100 FTEs furthering the goal to &amp;quot;promote competition,&amp;quot; while the Wireline Competition Bureau will have only 54.&amp;nbsp; Enforcement (53), OET&amp;nbsp;(53) and International (52) have nearly as many FTEs identified as promoting competition as does the Wireline Competition Bureau.&lt;/p&gt;
&lt;p&gt;Wireless also will have more FTEs who &amp;quot;advance key national purposes&amp;quot; than Wireline Competition (34 vs 20).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Enforcement has nearly as many employees working on &amp;quot;public safety&amp;quot; as does the Public Safety and Homeland Security Bureau.&lt;/u&gt;&lt;/strong&gt;&amp;nbsp; The&amp;nbsp;budget identifies 61 Enforcement FTEs as furthering the goal of &amp;quot;public safety and homeland security.&amp;quot;&amp;nbsp; The Public Safety Bureau, by contrast, has 83.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;FCC Regulatory Fees should rise 3%&amp;nbsp;over the next two years.&lt;/u&gt;&lt;/strong&gt;&amp;nbsp; FY 2011 Regulatory Fees (which were paid in September 2011) collected $335 million.&amp;nbsp;The&amp;nbsp;FY 2102 budget&amp;nbsp;calls for the FCC to collect $339 million in Regulatory Fees.&amp;nbsp; The FY 2013 budget proposes a request of $346 million in Regulatory&amp;nbsp;Fees.&amp;nbsp;&amp;nbsp;Next year's fee total is&amp;nbsp;1% higher; while the fee total proposed in the budget (which would be collected in two years) is 3% higher.&amp;nbsp; There always is&amp;nbsp;a slight shift in the FTE allocations each year, so&amp;nbsp;the actual amount of the increase for each category may vary slightly.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Broadcasters and other entities with spectrum not obtained via auction should be cautious.&amp;nbsp; The FCC is also backing legislation that will allow the Commission to collect user fees on unauctioned spectrum licenses.&amp;nbsp; This legislation, if enacted, would phase the user fees in over time, but would collect $4.8 billion through 2022, per the FCC.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/n6eaBo72ag8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/n6eaBo72ag8/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/fcc/tidbits-from-the-fccs-proposed-budget/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Broadband</category><category domain="http://www.telecomlawmonitor.com/articles">CLECs</category><category domain="http://www.telecomlawmonitor.com/articles">Enforcement</category><category domain="http://www.telecomlawmonitor.com/articles">FCC</category><category domain="http://www.telecomlawmonitor.com/tags">competition</category><category domain="http://www.telecomlawmonitor.com/tags">wireless</category>
         <pubDate>Tue, 14 Feb 2012 08:54:20 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/fcc/tidbits-from-the-fccs-proposed-budget/</feedburner:origLink></item>
            <item>
         <title>VoIP Outage Reporting Obligations to be Adopted at February 15 FCC Meeting</title>
         <description>&lt;p&gt;VoIP providers, prepare to report outages to the FCC. &amp;nbsp;Since early in 2010, the FCC&amp;nbsp;has &lt;a href="http://www.telecomlawmonitor.com/2010/07/articles/broadband-1/fcc-begins-groundwork-to-extend-outage-reporting-obligations-to-broadband-and-interconnected-voip-providers/"&gt;been on a path to impose new outage reporting obligations&lt;/a&gt;&amp;nbsp;on providers of interconnected VoIP services, despite industry opposition to the new requirements.&amp;nbsp; Today, the FCC released its &amp;quot;Sunshine Notice&amp;quot; confirming that it will vote on an order to adopt reporting requirements at its February 15th open meeting. &amp;nbsp;Here is how it described the VoIP item:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The Commission will consider a Report and Order to extend outage reporting under &lt;br /&gt;
Part IV of the rules to interconnected Voice over Internet Protocol (VoIP) service providers. Extended reporting will enable the Commission to fulfill statutory E9-1-1 obligations and help protect the growing number of Americans who rely on VOIP phone service.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The FCC notice is available at &lt;a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2012/db0208/DOC-312362A1.pdf"&gt;this link&lt;/a&gt;.&amp;nbsp; On the 15th, interested persons may view the FCC meeting at &lt;a href="http://www.fcc.gov/events/open-commission-meeting-february-2012"&gt;this link&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/uTKXfxdj67Y" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/uTKXfxdj67Y/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/voip/voip-outage-reporting-obligations-to-be-adopted-at-february-15-fcc-meeting/</guid>
         <category domain="http://www.telecomlawmonitor.com/tags">911</category><category domain="http://www.telecomlawmonitor.com/articles">Compliance Filing</category><category domain="http://www.telecomlawmonitor.com/articles">VoIP</category><category domain="http://www.telecomlawmonitor.com/tags">outage reporting</category>
         <pubDate>Wed, 08 Feb 2012 15:52:08 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/voip/voip-outage-reporting-obligations-to-be-adopted-at-february-15-fcc-meeting/</feedburner:origLink></item>
            <item>
         <title>FCC Clarifies USF Reform/Intercarrier Compensation Order</title>
         <description>&lt;p&gt;&lt;em&gt;This post was drafted by &lt;a href="http://www.kelleydrye.com/attorneys/chip_yorkgitis"&gt;Chip Yorkgitis&lt;/a&gt; and &lt;a href="http://www.kelleydrye.com/attorneys/joshua_guyan"&gt;Josh Guyan&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;On Friday, February 3, 2012, the FCC's&amp;nbsp;Wireline Competition Bureau and Wireless Telecommunications Bureau jointly released an order revising and clarifying certain aspects of the &lt;a href="http://www.telecomlawmonitor.com/2011/11/articles/access-charges/fcc-releases-text-of-intercarrier-compensation-order/#more"&gt;sweeping universal service and intercarrier compensation reform order&lt;/a&gt; adopted last November. The clarifications address the rates applicable to VoIP-PSTN traffic, access stimulation and the CETC phase-down of high-cost support, among other things.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The clarification order will be effective thirty days after it is published in the Federal Register, which is likely to occur quickly. However, as a practical matter, the clarifications are effective immediately in light of the rules being clarified already having taken effect.&lt;/p&gt;
&lt;p&gt;For more information, see &lt;a href="http://www.kelleydrye.com/publications/client_advisories/0721"&gt;Kelley Drye's Advisory&lt;/a&gt; on the clarification order.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/nUbBUHddn-A" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/nUbBUHddn-A/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/fcc/fcc-clarifies-usf-reformintercarrier-compensation-order/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Access Charges</category><category domain="http://www.telecomlawmonitor.com/articles">Broadband</category><category domain="http://www.telecomlawmonitor.com/articles">CLECs</category><category domain="http://www.telecomlawmonitor.com/articles">FCC</category><category domain="http://www.telecomlawmonitor.com/articles">Universal Service Fund</category><category domain="http://www.telecomlawmonitor.com/articles">VoIP</category>
         <pubDate>Wed, 08 Feb 2012 12:28:14 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/fcc/fcc-clarifies-usf-reformintercarrier-compensation-order/</feedburner:origLink></item>
            <item>
         <title>FCC Issues Clarification, Warning about Call Blocking Practices</title>
         <description>&lt;p&gt;Responding to complaints by rural LECs that call blocking has increased, the FCC yesterday issued a clarification and a stern warning to carriers not to block, choke or restrict calls to other carriers&amp;rsquo; customers. While call completion issues can occur for a variety of reasons, allegations of &amp;ldquo;blocking&amp;rdquo; have arisen in a number of access charge disputes and &lt;a href="http://www.telecomlawmonitor.com/2010/09/articles/litigation/text-messaging-provider-sues-tmobile-for-unlawful-call-blocking/"&gt;other forms of telecommunications litigation&lt;/a&gt; that we track.&lt;/p&gt;
&lt;p&gt;The FCC&amp;rsquo;s declaratory ruling serves as a warning that carriers involved in such disputes should not intentionally block or restrict the ability of callers to reach their intended destinations. It also appears to create affirmative obligations to correct call completion problems that are occurring.&lt;/p&gt;&lt;p&gt;Yesterday&amp;rsquo;s &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Call Blocking Declaratory Ruling.pdf"&gt;Declaratory Ruling&lt;/a&gt; came in response to filings made in June 2011 by several rural local exchange carriers. It reiterates and builds upon a similar &lt;a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-07-2863A1.pdf"&gt;Declaratory Ruling issued in 2007 &lt;/a&gt;that call blocking is unlawful.&lt;/p&gt;
&lt;p&gt;As explained by the FCC, the latest order addresses issues raised by rural carriers:&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Call completion problems appear to be occurring particularly in rural areas served by rate of return carriers where the costs that long distance providers incur to complete calls are generally higher than in non-rural areas. To minimize call termination charges, long distance providers often use third-party &amp;ldquo;least cost routers,&amp;rdquo; which attempt to connect calls to their destination at the lowest cost possible, usually within defined service parameters. Rural associations state that the call completion problems appear to arise from how originating carriers choose to set up the signaling and routing of their calls, and that many of these call routing and termination problems could lie with underlying routing providers selected by carriers who offer retail long distance services.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;In the Declaratory Ruling, the FCC broadly asserted that, &amp;ldquo;carriers are prohibited from blocking, choking, reducing or restricting traffic in any way, including to avoid termination charges.&amp;rdquo; This prohibition, said the FCC, extends to VoIP-PSTN traffic as well as traditional TDM traffic.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Unjust and Unreasonable Blocking Practices.&lt;/u&gt;&lt;/strong&gt; The noteworthy portion of the Declaratory Ruling is the Commission&amp;rsquo;s list of practices that it considers unjust and unreasonable. The order continues a recent trend by the Commission to rely broadly on Section 201(b) to declare specific practices unlawful. For example:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;It is unjust and unreasonable for a carrier that knows (or should know) that it is providing degraded service to certain areas to fail to correct the problem or to fail to ensure that intermediate carriers &amp;ldquo;are performing adequately.&amp;rdquo;&lt;/li&gt;
    &lt;li&gt;It may be unjust and unreasonable to provide a false or misleading intercept message when a call fails to complete, such as stating that a number is out of service when in fact the number is in service and is reachable.&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In addition, the Commission warned that the provision of lower quality service to rural or high cost areas could constitute an unreasonable discrimination under Section 202 of the Act. &lt;br /&gt;
&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Enforcement Actions.&lt;/u&gt;&lt;/strong&gt; The Commission warned that it may &amp;ldquo;take appropriate enforcement action&amp;rdquo; against carriers that violate these prohibitions. Although not setting a base forfeiture for call blocking, the FCC noted that the statute authorizes a penalty of up to $150,000 per violation or $1.5 million for a continuing violation of the Act.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/g3XzypJTYeQ" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/g3XzypJTYeQ/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/enforcement/fcc-issues-clarification-warning-about-call-blocking-practices/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Access Charges</category><category domain="http://www.telecomlawmonitor.com/articles">Enforcement</category><category domain="http://www.telecomlawmonitor.com/articles">Litigation</category><category domain="http://www.telecomlawmonitor.com/articles">VoIP</category><category domain="http://www.telecomlawmonitor.com/tags">call blocking</category>
         <pubDate>Tue, 07 Feb 2012 08:40:41 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/enforcement/fcc-issues-clarification-warning-about-call-blocking-practices/</feedburner:origLink></item>
            <item>
         <title>FCC Takes No Action Against Verizon 911 Outage; Maryland Still Investigating</title>
         <description>&lt;p&gt;Last year, we posted a couple of items about &lt;a href="http://www.telecomlawmonitor.com/2011/04/articles/enforcement/investigations-into-verizon-911-outages-moving-forward/"&gt;outages in Verizon's 911 call completion systems&lt;/a&gt;, and investigations by the FCC&amp;nbsp;and the Maryland PSC.&amp;nbsp; We thought now would be a good time for an update on those investigations.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;&lt;u&gt;FCC:&lt;/u&gt;&lt;/strong&gt;&amp;nbsp; As we noted previously, the FCC&amp;nbsp;investigation was started by the Public Safety Bureau, not the FCC's Enforcement Bureau, which suggested to us that the Commission was not looking to impose fines for the outages.&amp;nbsp; We are left to guess what happened, however, because the FCC has not released any information about the investigation since the February 2011 &lt;a href="http://www.telecomlawmonitor.com/uploads/file/FCC%20Letter%20to%20Verizon%20re%20911.pdf"&gt;Inquiry Letter&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;One thing we do know, however, is that the FCC cannot now impose a fine for the outage that sparked the investigation.&amp;nbsp; Section 503 of the Communications Act limits the FCC to taking enforcement action against common carriers only for violations that occurred within one year of the date of the Notice of Apparent Liability.&amp;nbsp; The outages in question occurred on January 26, 2011, which would mean that the FCC&amp;nbsp;had to issue a NAL by January 26, 2012 if if&amp;nbsp;sought to impose a fine.&amp;nbsp; Because it has not done so, the FCC is barred from proposing a fine for that outage.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Maryland PSC:&lt;/u&gt;&lt;/strong&gt;&amp;nbsp; The Maryland PSC held a hearing in March 2011 and then &lt;a href="http://www.telecomlawmonitor.com/2011/04/articles/enforcement/investigations-into-verizon-911-outages-moving-forward/"&gt;ordered Verizon to show cause why a civil penalty should not be imposed&lt;/a&gt;.&amp;nbsp; Subsequently, the Maryland PSC &lt;a href="http://www.telecomlawmonitor.com/uploads/file/MD PSC Order.pdf"&gt;expanded its investigation&lt;/a&gt; to include another outage affecting wireless and VoIP 911 calls that occurred on May 30, 2011.&amp;nbsp; After a hearing into that outage, &lt;a href="http://www.telecomlawmonitor.com/uploads/file/VerizonOpeningBrief.pdf"&gt;Verizon&amp;nbsp;maintains that no fines may be imposed&lt;/a&gt;.&amp;nbsp; The Maryland &lt;a href="http://www.telecomlawmonitor.com/uploads/file/PSC Staff Brief.pdf"&gt;PSC staff is recommending a civil penalty&lt;/a&gt; be assessed.&amp;nbsp; The Maryland case has been under advisement since October 2011.&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/WpXntCdX4JQ" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/WpXntCdX4JQ/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/enforcement/fcc-takes-no-action-against-verizon-911-outage-maryland-still-investigating/</guid>
         <category domain="http://www.telecomlawmonitor.com/tags">911</category><category domain="http://www.telecomlawmonitor.com/articles">Enforcement</category><category domain="http://www.telecomlawmonitor.com/tags">Verizon</category>
         <pubDate>Fri, 03 Feb 2012 08:50:33 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/enforcement/fcc-takes-no-action-against-verizon-911-outage-maryland-still-investigating/</feedburner:origLink></item>
            <item>
         <title>Prepaid Card Provider Settles Failure to Disclose Action for $2.3 Million</title>
         <description>&lt;p&gt;In 2011, the FCC was extremely active in the prepaid calling card area, &lt;a href="http://www.telecomlawmonitor.com/2011/11/articles/prepaid-cards/fcc-proposes-another-5-million-prepaid-card-fine/"&gt;proposing $25 million in fines&lt;/a&gt; and &lt;a href="http://www.telecomlawmonitor.com/2011/12/articles/enforcement/fcc-proposes-25000-fine-for-failure-to-respond-to-investigation/"&gt;investigating several other prepaid card providers&lt;/a&gt;.&amp;nbsp; While the FCC has exclusive jurisdiction over prepaid cards when provided by common carriers, the Federal Trade Commission also has jurisdiction over non-carrier marketers of prepaid calling cards.&amp;nbsp; This case is a reminder of the shared jurisdiction between the agencies.&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The FTC case was initiated in May of 2011 against Millennium Telecard, Inc. and related entities.&amp;nbsp; The &lt;a href="http://www.telecomlawmonitor.com/uploads/file/110601milleniumcmpt.pdf"&gt;FTC complaint&lt;/a&gt;&amp;nbsp;alleged that Millennium made inaccurate&amp;nbsp;claims about the number of minutes calling cards provided to a wide range of international locations, including Argentina, Brazil, the Dominican Republic, Ecuador, Mexico, Pakistan, Poland, Vietnam, Ghana, Nigeria, and El Salvador.&amp;nbsp; But the FTC alleged that consumers didn't receive the number of minutes advertised. Much of the FTC's case was based on test calls made by the agency, which, it claimed, showed that consumers received only 45% of the advertised minutes.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The FTC asserted that Millennium violated the FTC act by failing to provide the advertised minutes and (in a claim similar to that made by the FCC&amp;nbsp;in its section 201(b) cases) that Millennium failed to adequately disclose the fees applicable to the cards.&amp;nbsp; The FTC complaint did not explain in detail the failure to disclose claim, but its discussion of Millennium posters and cards suggested that the statements of fees were in fonts that were too small and were not prominently placed.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In the &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Settlement_Millennium.pdf"&gt;settlement agreement&lt;/a&gt;, Millennium agrees to two injunctive provisions that require it to clearly and conspicuously disclose all material fees.&amp;nbsp; It also agrees to pay a fine of $2.32 million to resolve the case.&amp;nbsp; However, Millennium pays only a $500,000 installment now, and is obligated to pay the remaining $1.82 million over ten years, in ten annual installments (plus interest).&amp;nbsp; The ten year installment is quite unusual, as is the defendants' grant of a lien on property as collateral for the installment payment.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This case serves as a reminder that prepaid calling card providers and marketers should closely review their marketing practices to ensure that all material terms are clearly and conspicuously disclosed in their marketing materials.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/KUCmUL8XBYc" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/KUCmUL8XBYc/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/prepaid-cards/prepaid-card-provider-settles-failure-to-disclose-action-for-23-million/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Calling Card Industry</category><category domain="http://www.telecomlawmonitor.com/articles">Enforcement</category><category domain="http://www.telecomlawmonitor.com/tags">FTC</category><category domain="http://www.telecomlawmonitor.com/tags">Millennium Telecard</category><category domain="http://www.telecomlawmonitor.com/articles">Prepaid cards</category>
         <pubDate>Thu, 02 Feb 2012 09:10:19 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/prepaid-cards/prepaid-card-provider-settles-failure-to-disclose-action-for-23-million/</feedburner:origLink></item>
            <item>
         <title>FCC Affirms 2008 Audio Bridging Classification Order</title>
         <description>&lt;p&gt;Back in November, we told you that the FCC&amp;nbsp;was considering an order on reconsideration in the 2008 audio bridging classification appeal brought by InterCall, Inc.&amp;nbsp; It took over two months, but the FCC last week issued an order denying in full the petitions for reconsideration of the Classification Order.&lt;/p&gt;
&lt;p&gt;The petitions were brought by two free conferencing providers, who argued that the FCC&amp;nbsp;had misinterpreted the nature of audio bridging service (or at least their audio bridging services).&amp;nbsp; In the reconsideration order, the FCC denies the petitions.&amp;nbsp; While we had hoped that the reconsideration order would provide additional explanation of the rationale for classifying audio bridging as telecommunications, except for a discussion of bundled services, the order does not provide further guidance&amp;nbsp;on the classification of bridging services.&amp;nbsp; As a result, audio conferencing providers will be left with the existing uncertainty for the foreseeable future when making classification decisions.&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The FCC &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Audio Bridging Recon Order.pdf"&gt;Reconsideration Order&amp;nbsp;&lt;/a&gt;denies in full the recon petitions submitted by&amp;nbsp;two &amp;quot;free&amp;quot; conferencing providers, Global Conferencing Partners (GCP) and A+ Conferencing.&amp;nbsp; The order affirms the conclusions in the 2008 Classification Order that audio bridging is &amp;quot;telecommunications&amp;quot; and that audio bridging providers must contribute to the USF.&amp;nbsp; With respect to the role of the conference bridge, the FCC does not classify the bridge as a switch or an intermediate point of routing.&amp;nbsp; Instead, it concludes that the bridge &lt;em&gt;facilitates&lt;/em&gt; routing, not that it performs the routing itself.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The Commission provides the most guidance in its discussion of additional features of the conference bridge.&amp;nbsp; In the Classification Order, the Commission had found that features such as recording and playback are separate from the audio bridging functionality.&amp;nbsp; In the Reconsideration Order, the FCC reiterated that the question is whether such functions are sufficiently &lt;em&gt;integrated&lt;/em&gt; with the telecommunications so as to form a single service.&amp;nbsp; If so, then the entire service can be treated as an information service; if not, then the provider must treat the offering as a bundle of services and perform an allocation of the revenues between the two services.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The Commission briefly referred to two services offered by petitioner GCP -- a &amp;quot;whiteboarding&amp;quot; feature and &amp;quot;other computing capabilities&amp;quot; made available to conference participants&amp;nbsp;-- both of which, the FCC concluded, are offered &amp;quot;simultaneously&amp;quot; with the audio bridging.&amp;nbsp; This was, in the FCC's view, not sufficiently integrated to constitute a single service.&amp;nbsp; Conferencing providers should review any similar services they offer carefully in light of this additional guidance.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/HMzunGV1yx8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/HMzunGV1yx8/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/02/articles/fcc/fcc-affirms-2008-audio-bridging-classification-order/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">FCC</category><category domain="http://www.telecomlawmonitor.com/articles">Universal Service Fund</category><category domain="http://www.telecomlawmonitor.com/tags">audio bridging</category><category domain="http://www.telecomlawmonitor.com/tags">conference calling services</category>
         <pubDate>Wed, 01 Feb 2012 09:02:19 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/02/articles/fcc/fcc-affirms-2008-audio-bridging-classification-order/</feedburner:origLink></item>
            <item>
         <title>Join us Feb. 16 for "Privacy in 2012" Seminar and Teleconference</title>
         <description>&lt;p&gt;Changes to privacy regulations, such as proposed revisions to the  Children's Online Privacy Protection Act (COPPA), and continuously  evolving technologies, including mobile apps with location-based  services, can make it difficult for businesses to ensure their privacy  practices are up to par.&lt;img hspace="5" height="107" align="right" width="187" vspace="5" alt="" src="http://www.adlawaccess.com/uploads/image/priv_2012_facebookbut_v1.jpg" /&gt;&lt;/p&gt;
&lt;p&gt;On February 16, Kelley Drye will gather government leaders from the  FTC and FCC, and thought leaders in the industry, for a discussion about  new regulations, enforcement trends, and best practices to avoid  consumer privacy risks. Please join us for &amp;quot;&lt;a href="http://www.kelleydrye.com/events/seminars/0166"&gt;Privacy in 2012: What to Watch Regarding COPPA, Mobile Apps, and Evolving Law Enforcement and Public Policy Trends&lt;/a&gt;.&amp;quot;&lt;/p&gt;
&lt;p&gt;Email &lt;a href="javascript:location.href='mailto:'+String.fromCharCode(100,99,101,118,101,110,116,115,64,107,101,108,108,101,121,100,114,121,101,46,99,111,109)+'?subject=Privacy%20Law%20Seminar%20RSVP'"&gt;dcevents@kelleydrye.com&lt;/a&gt; to register for the live seminar or teleconference.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;KEYNOTE SPEAKER&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Peter Swire&lt;/strong&gt;, Professor of Law, Ohio State  University; former Clinton Administration Chief Counselor for Privacy,  U.S. Office of Management and Budget&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;PANEL 1:&amp;nbsp; COPING WITH COPPA: CHILDREN'S PRIVACY AND PROPOSED REVISIONS TO THE COPPA RULE&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Ellen Blackler&lt;/strong&gt;, Vice President - Global Public Policy, The Walt Disney Company&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Mamie Kresses&lt;/strong&gt;, Senior Attorney, Division of Advertising Practices, Federal Trade Commission&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Saira Nayak&lt;/strong&gt;, Director of Policy, TRUSTe &lt;br /&gt;
&lt;br /&gt;
Moderated by partners &lt;strong&gt;Dana Rosenfeld &lt;/strong&gt;and &lt;strong&gt;Alysa Hutnik &lt;/strong&gt;of Kelley Drye &amp;amp; Warren LLP&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;PANEL 2:&amp;nbsp; MOBILE APPS: A PRIVACY AND CONSUMER PROTECTION HOT SPOT&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Michael Altschul&lt;/strong&gt;, Senior Vice President and General Counsel, CTIA&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Jessica Rich&lt;/strong&gt;, Associate Director, Division of Financial Practices, Federal Trade Commission&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Jennifer Tatel&lt;/strong&gt;, Associate General Counsel, Federal Communications Commission (invited)&lt;/p&gt;
&lt;p&gt;Moderated by partners &lt;strong&gt;John Heitmann &lt;/strong&gt;and &lt;strong&gt;Gonzalo Mon &lt;/strong&gt;of Kelley Drye &amp;amp; Warren LLP&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;When:&lt;/strong&gt;&lt;br /&gt;
February 16, 2012, &amp;nbsp;2:30 PM - 5:30 PM EST&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Location:&lt;br /&gt;
&lt;/strong&gt;Kelley Drye &amp;amp; Warren LLP &lt;br /&gt;
3050 K Street, NW, Suite 400 &lt;br /&gt;
Washington, DC 20007-5108&lt;/p&gt;
&lt;p&gt;And&amp;nbsp;via audio webcast&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;RSVP: &lt;br /&gt;
&lt;/strong&gt;Email &lt;a href="javascript:location.href='mailto:'+String.fromCharCode(100,99,101,118,101,110,116,115,64,107,101,108,108,101,121,100,114,121,101,46,99,111,109)+'?subject=RSVP%20for%202012%20Privacy%20Law%20Seminar%20'"&gt;dcevents@kelleydrye.com&lt;/a&gt; or contact Cassidy Russell at 202.342.8400.&lt;/p&gt;
&lt;p&gt;This seminar is free of charge, but space is limited. Reserve your place today.&lt;/p&gt;
&lt;p&gt;CLE and CPE credit may be available in certain jurisdictions.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/Nb52eXnyIv4" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/Nb52eXnyIv4/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/01/articles/kelley-drye/join-us-feb-16-for-privacy-in-2012-seminar-and-teleconference/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Kelley Drye</category>
         <pubDate>Wed, 25 Jan 2012 13:20:25 -0500</pubDate>
         <dc:creator>John Heitmann</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/01/articles/kelley-drye/join-us-feb-16-for-privacy-in-2012-seminar-and-teleconference/</feedburner:origLink></item>
            <item>
         <title>FCC Issues Enforcement Advisory on VoIP, Broadband Reporting Requirements</title>
         <description>&lt;p&gt;Here's another VoIP item from our backlog.&amp;nbsp; On December 16, the FCC's Enforcement Bureau issued an &lt;a href="http://www.telecomlawmonitor.com/uploads/file/Form 477 Enforcement Advisory.pdf"&gt;&amp;quot;Enforcement Advisory&amp;quot;&lt;/a&gt; reminding providers of their obligation to submit an FCC&amp;nbsp;Form 477 every six months.&amp;nbsp; The Form 477 collects information about broadband deployment on a Census Tract level.&amp;nbsp; All facilities-based broadband providers and all interconnected VoIP providers are required to submit the form.&lt;/p&gt;
&lt;p&gt;The Advisory lists several &amp;quot;problems&amp;quot; the Enforcement Bureau has noticed with the filings, including:&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;failing to file the form in a timely fashion, if at all;&lt;/li&gt;
    &lt;li&gt;failing to properly certify the form (and provide contact information); and&lt;/li&gt;
    &lt;li&gt;filing incomplete or inaccurate data (including failing to update data from previous submissions&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The FCC has not issued any forfeitures for failure to submit a Form 477, nor, to our knowledge, are any investigations into Form 477 compliance pending.&amp;nbsp; Nevertheless, as a reminder, below is a summary of the Form 477 filing obligations for broadband providers and VoIP service providers.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Form 477: Local Competition and Broadband Report&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
The Local Competition and Broadband Report, containing data as of December 31,&amp;nbsp;must be filed by March 1 of the following year.&amp;nbsp;&amp;nbsp; In addition, data as of June 30 of each year must be filed by September 1.&amp;nbsp; The report requires the submission of information regarding broadband connections in individual states.&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Who Must File:&lt;/em&gt;&lt;br /&gt;
(1) ILECs or CLECs that provide local exchange service to one or more end user customers; &lt;br /&gt;
(2) facilities-based providers of mobile telephony services that serve one or more mobile telephony subscribers; &lt;br /&gt;
(3) entities (including all commonly-owned or commonly-controlled affiliates) that are facilities-based providers of broadband (i.e., faster than 200 kbps, in at least one direction) connections (including both wired lines and wireless channels) to one or more end users in a state; and &lt;br /&gt;
(4) providers of interconnected VoIP services that provide interconnected VoIP service to one or more subscribers in a state.&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Reporting Basis:&lt;/em&gt;&lt;br /&gt;
In addition to specific reporting requirements contained in the Form 477 Instructions, for all broadband technologies other than terrestrial mobile wireless, filers must report broadband subscribership information by Census Tract. &lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Filing Process:&lt;/em&gt;&lt;br /&gt;
The Form 477 Report must be submitted via an FCC web-based interface and filers will need to use their Federal Registration Number (FRN) and associated password to access the system.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TelecomLawMonitor/~4/nYYVCnAdyGk" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/TelecomLawMonitor/~3/nYYVCnAdyGk/</link>
         <guid isPermaLink="false">http://www.telecomlawmonitor.com/2012/01/articles/broadband-1/fcc-issues-enforcement-advisory-on-voip-broadband-reporting-requirements/</guid>
         <category domain="http://www.telecomlawmonitor.com/articles">Broadband</category><category domain="http://www.telecomlawmonitor.com/articles">Compliance Filing</category><category domain="http://www.telecomlawmonitor.com/articles">Enforcement</category><category domain="http://www.telecomlawmonitor.com/tags">Form 477</category>
         <pubDate>Fri, 13 Jan 2012 17:15:41 -0500</pubDate>
         <dc:creator>Steve Augustino</dc:creator>
      
      <feedburner:origLink>http://www.telecomlawmonitor.com/2012/01/articles/broadband-1/fcc-issues-enforcement-advisory-on-voip-broadband-reporting-requirements/</feedburner:origLink></item>
      
   </channel>
</rss>

