<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ed's Telecom Alert &#187; VRS</title>
	<atom:link href="http://www.edsalert.com/category/vrs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.edsalert.com</link>
	<description>POSTS ALERTS REGARDING TRS &#38; ITS RELATED ISSUES</description>
	<lastBuildDate>Wed, 16 Nov 2011 19:25:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>The FCC Grants Conditional Certification of VRS to Convo Communications LLC</title>
		<link>http://www.edsalert.com/2011/11/16/the-fcc-grants-conditional-certification-of-vrs-to-convo-communications-llc/</link>
		<comments>http://www.edsalert.com/2011/11/16/the-fcc-grants-conditional-certification-of-vrs-to-convo-communications-llc/#comments</comments>
		<pubDate>Wed, 16 Nov 2011 19:02:45 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[VRS]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1807</guid>
		<description><![CDATA[Good People, The FCC has released a public notice announcing that the FCC has conditionally certified Convo for provision of VRS. &#160; This is a GREAT news as Convo is a deaf-owned video relay service provider that is certified to provide VRS. &#160; I can tell you that this is because of tireless and hard [...]]]></description>
			<content:encoded><![CDATA[<p>Good People,</p>
<p>The FCC has released a public notice announcing that the FCC has conditionally certified Convo for provision of VRS. &nbsp; This is a GREAT news as Convo is a deaf-owned video relay service provider that is certified to provide VRS. &nbsp;</p>
<p>I can tell you that this is because of tireless and hard teamwork from Convo employees and owners that made it possible. &nbsp;There were lot of challenges as the FCC released number of Orders, Clarifications, and Rulings on what VRS providers should do. &nbsp; Convo was able to follow the FCC rules to the letter because many people were involved and they kept track of items that need to be followed. &nbsp; From legal, regulatory, technical, funding, and frequent visits to DC contributed to achieving the goal of being certified; truth be told, though, that it is following the FCC to the letter and not overlooking any commas, and periods that made it possible for Convo to get to where it is. &nbsp;Check out the link:</p>
<p><a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1115/DA-11-1901A1.pdf">Convo Certification</a></p>
<p>Quotable quote:</p>
<p><em>&quot;..<span class="Apple-style-span" style="color: rgb(1, 1, 1); font-family: TimesNewRoman; font-size: 15px; ">the Consumer and Governmental Affairs Bureau (Bureau) hereby grants Convo&rsquo;s application on a conditional basis, pending inspection of Convo&rsquo;s facilities and confirmation of Convo&rsquo;s compliance with all applicable rules and orders.&quot;</span></em></p>
<p>The FCC conditions are onsite visit by the FCC, and ensuring transition to fully certified VRS provider is done according to the VRS regulations. &nbsp;&nbsp;</p>
<p>eyes wide open &amp; thumbs way up,</p>
<p>Ed Bosson</p>
<p>Long Link:&nbsp;</p>
<p>Convo Certification:&nbsp;http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1115/DA-11-1901A1.pdf</p>
<p>PS: This is an acknowledgement that I have ownership of Convo so take this post for what it is. &nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/11/16/the-fcc-grants-conditional-certification-of-vrs-to-convo-communications-llc/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>FCC Memo Opinion &amp; Order, Order, and FNPRM on Sprint, AT&amp;T &amp; SVRS</title>
		<link>http://www.edsalert.com/2011/10/21/fcc-memo-opinion-order-order-and-fnprm-on-sprint-att-svrs/</link>
		<comments>http://www.edsalert.com/2011/10/21/fcc-memo-opinion-order-order-and-fnprm-on-sprint-att-svrs/#comments</comments>
		<pubDate>Fri, 21 Oct 2011 18:01:11 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[VRS]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1780</guid>
		<description><![CDATA[Folks, This is an interesting and vital information mainly for VRS providers, but impacts deaf/hh as well. &#160; FCC at beginning postulates that: &#34;..we grant in part and deny in part the Sprint Petition, grant the Sorenson Petition, and deny the AT&#38;T Petition..&#34; Here is the link: FCC Responses Sprint&#39;s request for &#34;definition of employee&#34;: [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Folks,</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">This is an interesting and vital information mainly for VRS providers, but impacts deaf/hh as well. &nbsp;<br />
	</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">FCC at beginning postulates that:<em> &quot;..<span class="Apple-style-span" style="color: rgb(1, 1, 1); ">we grant in part and deny in part the Sprint Petition, grant the Sorenson Petition, and deny the AT&amp;T Petition..&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Here is the link:</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><a href="http://www.edsalert.com/wp-content/uploads/2011/10/727121-.-1-New-FCC-Certification-Order.pdf">FCC Responses</a></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Sprint&#39;s request for &quot;definition of employee&quot;: </span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;<span class="Apple-style-span" style="color: rgb(1, 1, 1); ">Sprint requests that the Commission clarify that CAs who are trained by the provider, who are stationed at the facilities of the provider and who are directly under the provider&rsquo;s supervision should be deemed to be employees of the provider, in satisfaction of this requirement, regardless of whether or not they are hired directly by the provider.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Reason for that is: <em>&quot;..<span style="color: rgb(1, 1, 1); ">that VRS providers with </span><span style="color: rgb(1, 1, 1); ">de minimis </span><span style="color: rgb(1, 1, 1); ">market shares will need flexibility in the way they develop their CA workforce, including being able to obtain the services of CAs on a temporary basis or pursuant to a&nbsp;</span><span class="Apple-style-span" style="color: rgb(1, 1, 1); ">contract of short duration with an interpreting agency, and that such arrangements would be consistent with Commission requirements.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="color: rgb(1, 1, 1); ">FCC responded: <em>&quot;</em></span><span class="Apple-style-span" style="color: rgb(1, 1, 1); "><em>We deny Sprint&rsquo;s requested clarification.&quot;</em> and this: <em>&quot;..we disagree with Sprint&rsquo;s assertion that allowing applicants to obtain the services of CAs on a temporary, contractual basis, or pursuant to a contract of short duration with an interpreting agency, would be consistent with Commission requirements, given our consistent distinction between such workers and employees.&quot;</em></span></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">FCC&#39;s rationale is: <em>&quot;..<span style="color: rgb(1, 1, 1); ">we determined that it was necessary for eligible VRS providers to </span><span style="color: rgb(1, 1, 1); ">employ </span><span style="color: rgb(1, 1, 1); ">their own CAs (rather than contract out for CA services) to &ldquo;ensure that certified providers exercise necessary oversight of their own operations and compliance with Commission rules,&rdquo; and we further recognized that requiring that CAs be employed by each eligible VRS provider would &ldquo;enable the Commission to better oversee the core operations of these providers.&rdquo;&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><font class="Apple-style-span" color="#010101">Sprint also requested &quot;roll-over VRS minutes&quot; to other VRS providers. &nbsp;FCC permitted that only if the VRS provider(s) themselves already have core call centers of their own that provide full service and only during emergency situations (hurricane, earthquake, etc).</font><br />
	</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Sprint&#39;s final clarification request on ACD (Automatic Call Distribution) platform that ACD platform need not to be on its own premises or use its own employees to manage it. &nbsp; FCC granted that however reiterated that &nbsp;</span></span><em><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">&quot;<span class="Apple-style-span" style="color: rgb(1, 1, 1); ">However, regardless of the location of the ACD, each provider is responsible for the oversight of all the core operations associated&nbsp;</span><span class="Apple-style-span" style="color: rgb(1, 1, 1); ">with such ACD platform, and shall be held accountable for compliance with all pertinent Commission rules and policies.&quot;</span></span></span></em></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="color: rgb(1, 1, 1); ">Sorenson Petition: &nbsp;basically Sorenson maintains that required reports on call centers as cited by the FCC is overburdensome due to SVRS large size. &nbsp; FCC agreed and modified that reporting will be limited to 5 call centers, but will ask VRS providers to keep copy of the lease arrangements on all call centers to be available in case the FCC chose to review them. </span></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="color: rgb(1, 1, 1); ">AT&amp;T&#39;s petition for reconsideration: </span></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="color: rgb(1, 1, 1); ">&quot;.. </span><span style="color: rgb(1, 1, 1); ">AT&amp;T generally seeks reconsideration of the requirements in the </span><span style="color: rgb(1, 1, 1); ">iTRS Certification Order </span><span style="color: rgb(1, 1, 1); ">that applicants for certification operate their own call centers and employ their own CAs.63 In addition, AT&amp;T seeks reconsideration of the prohibition against VRS providers subcontracting these core VRS functions to another certified VRS provider.&quot; then followed up with its arguments.</span></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">FCC responded:<em>&quot;<span style="color: rgb(1, 1, 1); ">We were not persuaded by these arguments at that time, and we concluded in the </span><span style="color: rgb(1, 1, 1); ">iTRS Certification Order </span><span style="color: rgb(1, 1, 1); ">that requiring VRS providers to lease, license, or acquire and operate their own facilities and employ their own CAs would better ensure compliance with our rules and reduce fraud.68 We see no reason to revisit that conclusion here.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">FNPRM (Further Notice of Proposed Rulemaking): &nbsp;Basically what the FCC opined on &quot;Roll Over&quot; issue above, and is asking public and companies for opinion on this. &nbsp;Bottom line: &nbsp;the proposed rulemaking is that VRS providers must own and operate call centers and that VRS providers have &quot;core&quot; call centers to handle all calls. &nbsp;The exception is when there are disasters such as hurricanes, tornadoes, earthquakes, etc, can the VRS calls be passed on to another VRS providers. &nbsp; FCC is asking for opinion from public on this. &nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Now I wanted to comment that I love this. &nbsp; A frank dialogue between the FCC and VRS providers. &nbsp; &nbsp;I applaud AT&amp;T, FCC SorensonVRS, and Sprint taking the initiative to clarify issues. &nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">eyes open &amp; thumbs up,</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Ed Bosson</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Long Link:</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">http://www.edsalert.com/wp-content/uploads/2011/10/727121-.-1-New-FCC-Certification-Order.pdf</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/10/21/fcc-memo-opinion-order-order-and-fnprm-on-sprint-att-svrs/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>SVRS Petition to Review FCC&#8217;s Ruling Rejected by US Court of Appeals</title>
		<link>http://www.edsalert.com/2011/10/19/svrs-petition-to-review-fccs-ruling-rejected-by-us-court-of-appeals/</link>
		<comments>http://www.edsalert.com/2011/10/19/svrs-petition-to-review-fccs-ruling-rejected-by-us-court-of-appeals/#comments</comments>
		<pubDate>Wed, 19 Oct 2011 18:01:34 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[VRS]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1766</guid>
		<description><![CDATA[Folks.. SorensonVRS had challenged the FCC of various rulings and the Court rendered its decision. &#160;Bottom line was that SorensonVRS challenged the FCC on 2010-2011 rates and offered rationales why. &#160; Court Decision The court came out fairly strong and the language was blunt. &#160; The document by the Court was fairly easy albeit bit [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Folks..</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">SorensonVRS had challenged the FCC of various rulings and the Court rendered its decision. &nbsp;Bottom line was that SorensonVRS challenged the FCC on 2010-2011 rates and offered rationales why. &nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1018/DOC-310452A1.pdf">Court Decision</a></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">The court came out fairly strong and the language was blunt. &nbsp; The document by the Court was fairly easy albeit bit long to follow as they were very clear on their positions. &nbsp;Suggest you click and read. &nbsp;Here are the highlights.</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Cost issues:<em>&nbsp;&quot;<span class="Apple-style-span">Allowable costs include, for example, labor costs, directly attributable overhead, startup expenses, executive compensation, and an 11.25% fixed rate of return on investment.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Note that video products are not allowable cost as the following quote illustrate:<em> &quot;<span class="Apple-style-span">Disallowed costs include a profit mark-up on expenses, research and development costs for enhancements that exceed mandatory minimum requirements, and the cost of providing videophones, software, and technical assistance to VRS users.&quot;</span></em>&nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;<span class="Apple-style-span">According to Sorenson, the increased wait times that may result from the lower&nbsp;rates will compromise the functional equivalence required of VRS.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Court observed that: &nbsp;&quot;<em><span class="Apple-style-span">Notably, Sorenson does not claim that it will be unable to satisfy the mandatory 80/120 speed-of-answer requirement under the interim rates. Instead, it only claims that its average wait times may increase from ten seconds to twenty seconds.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">&nbsp;<span class="Apple-style-span">Court notes that:<em> &quot;This&nbsp;<span class="Apple-style-span">regulation [TRS] requires VRS providers to &ldquo;answer 80% of all calls within 120 seconds.&rdquo;</span></em></span></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">&nbsp;Court concludes with: <em>&nbsp;&quot;<span class="Apple-style-span">Even under Sorenson&rsquo;s doomsday scenario, its increased wait times fall well-below the 120-second threshold set by the FCC for functional equivalence. Sorenson has failed to show the FCC&rsquo;s interpretation of &ldquo;functionally equivalent&rdquo; is impermissible under the statute. Consequently, it has not established that the interim rates violate the functional equivalence requirement of &sect; 225.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">On Availability Mandate: <em>&quot;Sorenson argues the <span style="font-style: italic; ">2010 Order </span>violates this availability mandate because the lower interim rates will undermine its ability to serve its current users and will prevent additional training and outreach to extend VRS to even more hearing and speech impaired individuals.&quot;</em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">&nbsp;Court responded?<em> &quot;We are not persuaded.&quot;</em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">On Technology: <em>&quot;Sorenson claims the interim rates violate this provision because they do not compensate providers for the cost of customer equipment, such as videophones, which discourages the deployment of new technology.&quot;</em><br />
	</span></span></p>
<p><span style="font-family:tahoma,geneva,sans-serif;"><span style="font-size:14px;"><font class="Apple-style-span"><span class="Apple-style-span">Court responded: </span></font><em style="font-family: TimesNewRomanPSMT; font-size: 13pt; ">&quot;<span style="font-size:16px;">Again, Sorenson&rsquo;s argument fails to persuade us.</span>&quot; &nbsp;&nbsp;</em><br />
	</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Court reiterated:</span></span><em><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"> &quot;<span class="Apple-style-span">As we have already discussed, providing free customer equipment was not an allowable cost for compensation from the TRS Fund even under earlier Orders.&quot;</span></span></span></em></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;<span class="Apple-style-span">Just as users of traditional telephone service do not receive their telephones for free, &sect; 225 does not require that VRS users receive free videophones.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">SVRS claims: &nbsp;<em>&quot;Sorenson also claims the <span style="font-style: italic; ">2010 Order </span>is arbitrary and capricious in violation&nbsp;<span class="Apple-style-span">of the Administrative Procedure Act. First, it argues the ratemaking method was irrational because NECA&rsquo;s proposed rates are unreliable and were nevertheless averaged by the Commission with the prior rates. Second, it contends the tiered structure is irrational.&quot;</span></em></span><br />
	</span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><span class="Apple-style-span">After a long treatise by the Court of how the FCC did its job well and concluded with <em>&quot;</em></span><em><span class="Apple-style-span">Moreover, the FCC is entitled to substantial deference when adopting interim rates.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Final conclusion by the Court:</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;Because the <span style="font-style: italic; ">2010 Order&rsquo;s </span>interim rate plan for VRS neither violates 47 U.S.C. &sect; 225 nor is an arbitrary and capricious exercise of the FCC&rsquo;s authority, we <span style="font-weight: 700; ">DENY </span>Sorenson&rsquo;s petition for review.&quot;</em></span></span></p>
<p><span class="Apple-style-span" style="font-family: tahoma, geneva, sans-serif; font-size: 14px; ">eyes open &amp; thumbs up,</span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Ed Bosson</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Long Link:</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1018/DOC-310452A1.pdf</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/10/19/svrs-petition-to-review-fccs-ruling-rejected-by-us-court-of-appeals/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Waiver by White Label Providers Denied by the FCC</title>
		<link>http://www.edsalert.com/2011/09/14/waiver-by-white-label-providers-denied-by-the-fcc/</link>
		<comments>http://www.edsalert.com/2011/09/14/waiver-by-white-label-providers-denied-by-the-fcc/#comments</comments>
		<pubDate>Wed, 14 Sep 2011 22:00:22 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[VRS]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1704</guid>
		<description><![CDATA[&#160; Folks, An ongoing chronicle of certification procedure is coming to an end soon. &#160;This post is long, but revealing! First there is a certification procedure that dates way back to 1992. &#160;When Internet Relay started (IP Relay and VRS), the FCC took hard look at the certification procedure and the FCC has made series [...]]]></description>
			<content:encoded><![CDATA[<p><span _fck_bookmark="1" style="display: none; ">&nbsp;</span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">Folks,</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">An ongoing chronicle of certification procedure is coming to an end soon. &nbsp;This post is long, but revealing!</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">First there is a certification procedure that dates way back to 1992. &nbsp;When Internet Relay started (IP Relay and VRS), the FCC took hard look at the certification procedure and the FCC has made series of changes to the certification procedure. &nbsp; I won&#39;t go into gritty detail on this, but do want to call your attention to two links and resulting decision as result of the Orders by the FCC. &nbsp;It will show what is happening with those non-certified VRS providers. &nbsp;</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">First this order:</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;"><a href="http://fjallfoss.fcc.gov/ecfs/document/view?id=7021688064">May 31 Order</a></span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;"><em>&quot;We&nbsp;<span class="Apple-style-span">find good cause to stay the effective date of<span style="font: 11.0px Times">&nbsp;</span>this rule because the Commission is undergoing a review of</span><font class="Apple-style-span"><span class="Apple-style-span">&nbsp;</span></font><font class="Apple-style-span"><span class="Apple-style-span">the certification requirements for IP-enabled TRS providers.&quot;</span></font></em></span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">Basically that order mooted the waiver procedure which means the previous &quot;new&quot; rule now are no longer in effect because the FCC is reviewing certification procedure so the waivers that non-certification providers submitted are no good except for four providers that were asterisked (go to the exhibit on this link and you will see four providers with asterisk) along with LONG list of waiver requests. &nbsp;It meant four asked more than one waiver so the FCC put these aside. &nbsp;</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">If understood it right, all others that were not asterisked will not be certified.&nbsp;</span></span><span class="Apple-style-span" style="font-family: arial, helvetica, sans-serif; font-size: 14px; ">Basically the white label providers who had their waivers mooted, they did not come into compliance with other rules (the ones they did not ask for waiver on) so they failed in meeting compliance. &nbsp;</span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">Now yesterday&#39;s order was the decision making order. &nbsp; <br />
	</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;"><a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db0913/DA-11-1542A1.pdf">Denied&nbsp;</a></span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">Remember above four were asterisked, but three were denied the waiver requests. &nbsp;</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;"><em>&quot;<span class="Apple-style-span" style="color: rgb(27, 26, 26); ">In this Order, the Consumer and Governmental Affairs Bureau (Bureau), on delegated authority, denies three waiver requests filed separately by: (1) Deaf Link, Inc. (&ldquo;Deaf Link&rdquo;);<span style="font: 7.0px 'Times New Roman'">1 </span>(2) NorthStar Relay, LLC (&ldquo;NorthStar&rdquo;);<span style="font: 7.0px 'Times New Roman'">2 </span>and (3) ONE Technologies LLC (&ldquo;ONE Technologies&rdquo;)<span style="font: 7.0px 'Times New Roman'">3 </span>(collectively &ldquo;Petitioners&rdquo;).&quot;</span></em></span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">FCC stated: <em>&quot;..<span class="Apple-style-span" style="color: rgb(27, 26, 26); ">a waiver applicant &ldquo;will have the burden of showing that the waiver is in the public interest, that grant of the waiver request will not undermine the purposes of the rules that we adopt today, and that it will come into compliance with those rules within a short period of time.&rdquo;<span style="font: 7.0px 'Times New Roman'">21<span class="Apple-tab-span" style="white-space:pre"> </span></span>In addition, the Commission required each waiver applicant &ldquo;to provide, in writing, a description of the specific requirement(s) for which it is seeking a waiver, along with documentation demonstrating the applicant&rsquo;s plan and ability to come into compliance with all of these requirements (other than the certification requirement)&rdquo; within three months after the rules become effective, and elaborated that &ldquo;[e]vidence of the applicant&rsquo;s plan and ability to come into compliance with the new rules shall include the applicant&rsquo;s detailed plan for modifying its business structure and operations in order to meet the new requirements.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">And this: <em>&quot;<span class="Apple-style-span" style="color: rgb(27, 26, 26); ">The Commission further specified that it would grant waivers &ldquo;only after a rigorous showing that the applicant has workable plans and the ability to continue providing VRS in a manner that will not undermine the measures adopted in [the VRS Practices&nbsp;R&amp;O] to eliminate the fraud and abuse that have plagued the VRS program.&rdquo;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">Wow. &nbsp; The FCC obviously meant business. &nbsp;Funny Zero!</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">NorthStar: I know many of you want to know who each providers are: &nbsp; Here is one good quote on who is involved with NorthStar:</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">&quot;<span class="Apple-style-span" style="color: rgb(27, 26, 26); ">NorthStar was formed on May 18, 2011 as a combination of the Communications Access Center for the Deaf and Hard of Hearing (CAC), CP&amp;J Investments, LLC d/b/a PAH! Relay (PAH), Interpretel LLC (Interpretel), Sign Language Access, Inc., d/b/a CallVRS (CallVRS), and URrelay, Inc. (URrelay).&quot;</span></span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">DeafLink: &nbsp;I was given to understand that DeafLink absorbed number of white label providers, but did not mention in this order.&nbsp;</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">One Technology: &nbsp;OneVRS</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">All these three non-certified providers were denied the waiver means they can no longer provide VRS; more specifically they were denied waiver between June 1st and Sept 1. &nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">The certification procedure is by no means over; there will likely be still changes and more rule/orders from the FCC. &nbsp;How many non-certified providers (white label) ultimately will be certified, I can&#39;t say, but it will be low.&nbsp;</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">eyes open &amp; thumbs up,</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">Ed Bosson</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">Long Link:</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">May 31 Order:&nbsp;http://fjallfoss.fcc.gov/ecfs/document/view?id=7021688064</span></span></p>
<p><span style="font-family:arial,helvetica,sans-serif;"><span style="font-size:14px;">Denied:&nbsp;http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db0913/DA-11-1542A1.pdf</span></span></p>
<p><span _fck_bookmark="1" style="display: none; ">&nbsp;</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/09/14/waiver-by-white-label-providers-denied-by-the-fcc/feed/</wfw:commentRss>
		<slash:comments>23</slash:comments>
		</item>
		<item>
		<title>New FCC Certification Procedure</title>
		<link>http://www.edsalert.com/2011/08/09/new-fcc-certification-procedure/</link>
		<comments>http://www.edsalert.com/2011/08/09/new-fcc-certification-procedure/#comments</comments>
		<pubDate>Tue, 09 Aug 2011 14:57:16 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[VRS]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1649</guid>
		<description><![CDATA[Folks.. Here is what VRS industry, deaf/hoh leaders, lawyers, and persons/companies wishing to go into VRS business have been waiting for: a new procedure for certifying companies wishing to become a certified VRS provider. &#160;The FCC has taken on a route that, in their opinion, will eliminate frauds, abuses as well as eliminate fly-by night [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="background-color:#fff;">Folks..</span></span></span></p>
<p><span style="background-color:#fff;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="font-size:14px;">Here is what VRS industry, deaf/hoh leaders, lawyers, and persons/companies wishing to go into VRS business have been waiting for: a new procedure for certifying companies wishing to become a certified VRS provider. &nbsp;The FCC has taken on a route that, in their opinion, will eliminate frauds, abuses as well as eliminate fly-by night operators that just want to pump minutes and make quick buck. &nbsp;</span></span></span></p>
<p><span style="background-color:#fff;"><span class="Apple-style-span" style="font-family: tahoma, geneva, sans-serif; font-size: 14px; "><a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db0728/FCC-11-118A1.pdf">NewFCCProcedure</a></span></span></p>
<p><span style="background-color:#fff;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="font-size:14px;">Here is the FCC&#39;s summarization of the new FCC certification procedure (from that link &#8211; see section 2):</span></span></span></p>
<p><span style="background-color:#fff;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="color:#4b0082;"><em><span style="font-size:16px;">&quot;..<span class="Apple-style-span">we require all iTRS providers to obtain certification from the Commission in order to be eligible to receive compensation from the Fund; </span></span></em></span><br />
	</span></span></p>
<ul>
<li><span style="background-color:#fff;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="color:#4b0082;"><em><span style="font-size:16px;"><span class="Apple-style-span">require all VRS applicants for Commission certification to lease, license or own, as well as operate, essential facilities associated with TRS call centers and to employ interpreters to staff those centers at the date of the application; </span></span></em></span><br />
		</span></span></li>
<li><span style="background-color:#fff;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="color:#4b0082;"><em><span style="font-size:16px;"><span class="Apple-style-span">and require each iTRS applicant for certification to submit specific types of documentary evidence of its ability to comply with all of the Commission&rsquo;s rules, including those newly adopted in the VRS Practices R&amp;O. </span></span></em></span><br />
		</span></span></li>
<li><span style="background-color:#fff;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="color:#4b0082;"><em><span style="font-size:16px;"><span class="Apple-style-span">In addition, we adopt rules governing on-site visits by Commission staff to the premises of applicants for certification, as well as to iTRS providers&rsquo; premises after they are certified. </span></span></em></span><br />
		</span></span></li>
<li><span style="background-color:#fff;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="color:#4b0082;"><em><span style="font-size:16px;"><span class="Apple-style-span">We also revise our rules governing annual compliance reports filed by certified providers, and substantive TRS program changes that must be reported to the Commission. </span></span></em></span><br />
		</span></span></li>
<li><span style="background-color:#fff;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="color:#4b0082;"><em><span style="font-size:16px;"><span class="Apple-style-span">Finally, we require prior approval for planned cessations of VRS service of 30 minutes or longer.&quot;</span></span></em></span></span></span></li>
</ul>
<p><span _fck_bookmark="1" style="display: none; ">&nbsp;</span></p>
<p><span style="background-color:#fff;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="font-size:14px;">Bottom line is that it will not be easy to be certified by the FCC and it will be expensive to form a VRS provider. High investment that very well could approach minimum of 1 million dollars to make it possible to meet all the criteria to be certified. &nbsp;Disclaimer, this is my guess. &nbsp; We&#39;ll know more when the certification procedures take place and how companies will handle that. &nbsp;</span></span></span></p>
<p><span style="background-color:#fff;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="font-size:14px;">More of quotable quotes:</span></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;..<span class="Apple-style-span" style="color: rgb(27, 26, 26); ">although VRS has proven to be extremely popular, this service has become vulnerable to fraud and abuse, which in turn has threatened its long-term sustainability.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;..<span class="Apple-style-span" style="color: rgb(27, 26, 26); ">In an effort to curb such illicit activities, and ensure that VRS remains a valuable communication tool for Americans who rely on this service for their daily communications, the Commission adopted a number of changes to the VRS program, some of which apply to all iTRS providers.&quot;</span></em></span></span></p>
<p><font class="Apple-style-span" face="tahoma, geneva, sans-serif"><span class="Apple-style-span" style="font-size: 14px;">The following quote is an interesting one because many of white label VRS providers are already licensed as &quot;interstate common carrier&quot;, and AT&amp;T asked the FCC to exempt those VRS providers with Interstate Common Carrier status, and this quote is the response. </span></font></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;..<span class="Apple-style-span" style="color: rgb(27, 26, 26); ">the certification requirement is a critical tool that is designed to help ensure the integrity of the iTRS programs, ensure that iTRS services conform to our rules, ensure that only qualified providers receive compensation from the Fund, and help combat waste, fraud and abuse. We will therefore not exempt interstate common carriers or any other class of providers from the iTRS certification requirement. <span style="background-color:#ffff00;">Existing iTRS providers who are currently eligible for compensation from the Fund by virtue of their interstate common carrier status, and who seek to continue to receive compensation from the Fund, must apply for certification under the new process</span>.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">The following analysis focuses on the yellow highlight above. &nbsp;The fact white label providers are licensed by state(s) as Interstate Common Carrier is not enough to be certified as VRS provider. &nbsp;Not only this, if I understand the rule right, it meant even the certified VRS providers who got certified on the sole purpose of licensing of states as an interstate common carrier or similar labeling will need to re-apply for certification. &nbsp;If my interpretation is right, that means ALL of certified providers will need to re-apply. &nbsp;What we will likely see is flurry of VRS providers finding loopholes to circumvent this rule. &nbsp;It will be interesting to see how the FCC will respond to these if any. &nbsp;&nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">The order did say only apply to iTRS (&quot;i&quot;) which means only applies to certified providers who provide Internet Relay Service (IP and VRS).</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">I strongly suggest you read the criteria for becoming certified iTRS provider. &nbsp; &nbsp;It will give you a much insight of what the FCC intends to do. &nbsp; Bottom line, if you want to form a VRS provider, you gotta have lots of bucks to do it. &nbsp; Won&#39;t be cheap. &nbsp;You must have technology know how, and must understand regulations for TRS as well as the current new ones to fully understand how to become a VRS provider. &nbsp;&nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">That said, I would not be surprised to see less than ethical companies trying to find loopholes and stay in business. &nbsp;I just hope that the oversight responsibility of the FCC will now be enough to prevent unsavory companies from becoming a provider.&nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">eyes open &amp; thumbs up,</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Ed Bosson</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><br />
	</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Long URL:&nbsp;http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db0728/FCC-11-118A1.pdf</span></span></p>
<p><span _fck_bookmark="1" style="display: none; ">&nbsp;</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/08/09/new-fcc-certification-procedure/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Genachowski&#8217;s Report</title>
		<link>http://www.edsalert.com/2011/07/08/genachowskis-report/</link>
		<comments>http://www.edsalert.com/2011/07/08/genachowskis-report/#comments</comments>
		<pubDate>Fri, 08 Jul 2011 20:55:12 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[VRS]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1645</guid>
		<description><![CDATA[Hi Dear Friends, Hearing on &#34;FCC Process Reform&#34; before the Subcommittee on Communications and Technology Committee on Energy and Commerce U.S. House of Representatives. &#160;Chair Genachowski gave a report on what the FCC has done on improving the FCC&#39;s infrastructure system. &#160; REPORT One thing that caught my eyes was Chair&#39;s comment on VRS which [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Hi Dear Friends,</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Hearing on &quot;FCC Process Reform&quot; b<span class="Apple-style-span">efore the Subcommittee on Communications and Technology Committee on Energy and Commerce U.S. House of Representatives. &nbsp;Chair Genachowski gave a report on what the FCC has done on improving the FCC&#39;s infrastructure system. &nbsp;</span></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><a href="https://prodnet.www.neca.org/publicationsdocs/wwpdf/7711gen.pdf"><strong>REPORT</strong></a></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">One thing that caught my eyes was Chair&#39;s comment on VRS which is the below:</span></span></p>
<p>&nbsp;</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Times"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><span style="background-color:#fff;"><em>&quot;We have also initiated a series of programmatic reforms to ensure efficiency, accountability, and fiscal responsibility. For example, our Video Relay Service program, which provides vital communications for people who are deaf or hard-of-hearing, suffered from significant instances of fraud and abuse. We have worked with the Department of Justice to prosecute wrongdoers and instituted other reforms to this program that have already saved taxpayers approximately $250 million.&quot;<br />
	</em></span></span></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Times">&nbsp;</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Times"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">hmm &#8211; I did not realize as result of minimizing fraud and abuse, saved approx $250 million. &nbsp;FCC has many, many issues yet VRS was important enough to make it to the 5 page report. &nbsp; &nbsp;</span></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Times"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><br />
	</span></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Times"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Rest of the report is standard reporting on various issues that the Chair has undertook to improve the FCC. &nbsp; Worth reading? &nbsp;Yes, if you are interested in what kind of changes the FCC has done.</span></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Times"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><br />
	</span></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Times"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">eyes open &amp; thumbs up,</span></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Times"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><br />
	</span></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Times"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Ed</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/07/08/genachowskis-report/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Waiver Request and Follow Up Suspension</title>
		<link>http://www.edsalert.com/2011/06/13/waiver-request-and-follow-up-suspension/</link>
		<comments>http://www.edsalert.com/2011/06/13/waiver-request-and-follow-up-suspension/#comments</comments>
		<pubDate>Mon, 13 Jun 2011 22:25:15 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[VRS]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1632</guid>
		<description><![CDATA[Folks,&#160; When the FCC released the order (a couple posts back on Edsalert), the FCC had in mind a way to minimize number of non-certified VRS providers down to manageable size. &#160;However, there is a clause where it indicate those already providing VRS, but not certified may submit waiver if the non-certified providers show that [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Folks,&nbsp;</span></span></p>
<p><span style="font-size:14px;">When the FCC released the order (a couple posts back on Edsalert), the FCC had in mind a way to minimize number of non-certified VRS providers down to manageable size. &nbsp;However, there is a clause where it indicate those already providing VRS, but not certified may submit waiver if the non-certified providers show that they will be in compliance with the TRS regulations. &nbsp; &nbsp;The deadline to submit that was May 31. &nbsp;</span></p>
<p><span style="font-size:14px;">Basically the order said:</span></p>
<p><span style="font-size:14px;"><em><span style="font-family:tahoma,geneva,sans-serif;">&quot;<span class="Apple-style-span" style="color: rgb(27, 26, 26); ">A company requesting a waiver of the rules adopted in this Order will have the burden of showing that the waiver is in the public interest, that grant of the waiver request will not undermine the purposes of the rules that we adopt today, and that it will come into compliance with those rules within a short period of time.&quot;</span></span></em></span></p>
<p><span style="font-size:14px;">Okay.</span></p>
<p><span style="font-size:14px;">A few non-certified providers including Convo submitted waiver reports to the FCC. &nbsp;Quite a few of them. &nbsp;</span></p>
<p><span style="font-size:14px;">On May 31, the FCC releases a suspension of the Waiver clause and render the waiver requests as moot. &nbsp;All the work that non-certified providers did are now &quot;moot&quot;. &nbsp;Ouch! It meant lot of times and funds spend on that may now go down the drain. &nbsp;</span></p>
<p><span style="font-size:14px;">The link below is about the suspension of the order. &nbsp;</span></p>
<p><span style="font-size:14px;"><a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db0531/FCC-11-86A1.pdf">Suspension</a></span></p>
<p><span style="font-size:14px;">The FCC&#39;s rationale is:&nbsp;</span></p>
<p><span style="font-size:14px;"><em><span style="font-family:tahoma,geneva,sans-serif;">&quot;<span class="Apple-style-span" style="color: rgb(27, 26, 26); ">We find good cause to stay the effective date of this rule because the Commission is undergoing a review of the certification requirements for IP-enabled TRS providers.&quot;</span></span></em></span></p>
<p><span style="font-size:14px;">and</span></p>
<p><span style="font-size:14px;"><em><span style="font-family:tahoma,geneva,sans-serif;">&quot;<span class="Apple-style-span" style="color: rgb(27, 26, 26); ">We anticipate releasing an order adopting a new certification process for Internet-based TRS services based on the record in the FNRPM within the stay period. Entities will be then given the opportunity to apply for certification prior to the expiration of the stay on October 1, 2011, in order to become eligible for compensation from the Interstate TRS Fund under the new process.&quot;</span></span></em></span></p>
<p><font class="Apple-style-span" face="tahoma, geneva, sans-serif" size="4"><span class="Apple-style-span" style="font-size: 14px;">It does beg a question what will the non-certified providers do in the meantime? &nbsp; Are there options? &nbsp;Yes, a few but not to the best interest of non-certified providers themselves. &nbsp;Perhaps that is what the FCC wants.&nbsp;</span></font></p>
<p>Your thoughts, Readers?</p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">eyes open &amp; thumbs up,</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Ed Bosson</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/06/13/waiver-request-and-follow-up-suspension/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>FCC Releases News, Order, and FNPRM</title>
		<link>http://www.edsalert.com/2011/04/09/fcc-releases-news-order-and-fnprm/</link>
		<comments>http://www.edsalert.com/2011/04/09/fcc-releases-news-order-and-fnprm/#comments</comments>
		<pubDate>Sat, 09 Apr 2011 13:23:44 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[VRS]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1591</guid>
		<description><![CDATA[People, This is the FCC actions that VRS industry, Sophisticated VRS Users, and Mover &#38; Shakers of Deaf/HOH have been waiting for! New Order and FNPRM promise to shake things up in VRS world. &#160; Before I go on, it is important to remember that TRS/VRS providers are paid from a public fund; in other [...]]]></description>
			<content:encoded><![CDATA[<p><font size="2" face="Tahoma">People,</p>
<p><strong>This is the FCC actions that VRS industry, Sophisticated VRS Users, and Mover &amp; Shakers of Deaf/HOH have been waiting for!</p>
<p></strong>New Order and FNPRM promise to shake things up in VRS world.<strong> &nbsp; </p>
<p></strong>Before I go on, it is important to remember that TRS/VRS providers are paid from a public fund; in other words, a federal subsidy of which government have oversight over.&nbsp; Not exactly the same as free-for-all commercial type of venture with no government oversight.&nbsp;&nbsp; <br /><strong><br /></strong>Exactly what is &quot;Order&quot; and what the heck is &quot;FNPRM&quot;?&nbsp;&nbsp; Order is self-explanatory:&nbsp; Any regulations from Order means that is the  regulation now.&nbsp; In this case, the FCC Order for VRS is now the &quot;law&quot; of VRS industry.&nbsp; </p>
<p>FNPRM means  &quot;Further Notice of Proposed Rulemaking&quot; which means FCC proposes modified regulation from a previous NPRM (original one) and is asking the world for comments on the newly modified proposed rules. Typically VRS industry, sophisticated users, and national advocates comment to the FNPRM.&nbsp; Anyone can comment, though.&nbsp;&nbsp; </p>
<p>Starting with FCC News:&nbsp; </p>
<p><a href="http://www.fcc.gov/Daily_Releases/Daily_Business/2011/db0406/DOC-305586A1.pdf">FCC News</a></p>
<p>Above link is a good summary of the Order and FNPRM.&nbsp;&nbsp; Mere two pages.&nbsp; </p>
<p>Quotable quotes from Report &amp; Order:</p>
<p></font></p>
<ul>
<li><font size="2" face="Tahoma"><em>Require that VRS providers submit a statement describing the location and staffing of their call centers twice a year, and a notification at least 30 days prior to any change in the location of such centers;</em></font></li>
<li><font size="2" face="Tahoma"><em>Prohibit VRS CAs from relaying calls from their homes and prohibit VRS providers from tying minutes or calls processed by a CA to compensation provided;</em></font></li>
<li><font size="2" face="Tahoma"><em>Prohibit compensation for VRS calls that originate from IP addresses that indicate the individual initiating the call is located outside of the United States, with the exception of callers who pre- register with their default provider for a specified time and location of travel;</em></font></li>
<li><font size="2" face="Tahoma"><em>Prohibit compensation for VRS calls for remote training when the service provider is involved in any way with such training (e.g., sponsors, promotes or hosts such training);</em></font></li>
<li><font size="2" face="Tahoma"><em>Prohibit VRS CAs from using visual privacy screens, and requires that CAs terminate a VRS call, after providing a warning announcement, if either party to the call: (1) enables a privacy screen or similar feature for more than five minutes, or (2) is unresponsive or unengaged for more than five minutes, unless the call is to 9-1-1 or one of the parties is on hold;</em></font></li>
<li><font size="2" face="Tahoma"><em>Require automated recordkeeping of TRS minutes submitted to the Fund;</em></font></li>
<li><font size="2" face="Tahoma"><em>Require that VRS be offered to the public only in the name of the provider eligible for compensation from the Fund and, when sub-brands are used, that these identify such eligible provider; requires that calls to any brand or sub-brand of VRS be routed through a single URL address for that brand or sub-brand;</em></font></li>
<li><font size="2" face="Tahoma"><em>Prohibit revenue sharing agreements for CA or call center functions between entities eligible for compensation from the Fund and non-eligible entities;</em></font></li>
<li><font size="2" face="Tahoma"><em>Prohibit compensation on a per-minute basis for marketing and outreach costs performed through a subcontractor where such services utilize VRS;</em></font></li>
<li><font size="2" face="Tahoma"><em>Adopt whistleblower protection rules for current and former employees and contractors of TRS providers;</em></font></li>
</ul>
<p><font size="2" face="Tahoma">The following is from NPRM:</p>
<p>Mainly on certification procedure.&nbsp; <br /></font></p>
<ul>
<li><font size="2" face="Tahoma"><em>Require that all Internet-based TRS providers be certified by the Commission to become eligible to receive compensation from the TRS Fund;</em></font></li>
<li><font size="2" face="Tahoma"><em>Require new and renewing certification applicant providers to provide specific documentary evidence of their ability to comply with the TRS rules; The Commission may choose to conduct on-site visits as part of the certification process;</em></font></li>
<li><font size="2" face="Tahoma"><em>Revise the provider&rsquo;s annual report filings to the Commission to require further documentation that providers are in compliance with the Commission&rsquo;s TRS rules;</em></font></li>
<li><font size="2" face="Tahoma"><em>Clarify what types of changes trigger a provider&rsquo;s obligation to notify the Commission that substantive changes in its TRS program have occurred;</em></font></li>
<li><font size="2" face="Tahoma"><em>Require providers to seek approval from the Commission for voluntary interruption of their Internet-enabled relay service and to promptly notify the Commission after-the-fact when unforeseen service interruptions occur.</em><br /></font></li>
</ul>
<p><font size="2" face="Tahoma">The following link is the full-blown description of the above; 69 pages long. </p>
<p><a href="http://www.fcc.gov/Daily_Releases/Daily_Business/2011/db0406/FCC-11-54A1.pdf">Order and FNPRM</a></p>
<p>As always, give me your thoughts on this very important one.&nbsp;&nbsp; </p>
<p>eyes open &amp; thumbs up,</p>
<p>Ed</p>
<p>Long Link:</p>
<p>FCC News: http://www.fcc.gov/Daily_Releases/Daily_Business/2011/db0406/DOC-305586A1.pdf</p>
<p>Order and FNPRM: http://www.fcc.gov/Daily_Releases/Daily_Business/2011/db0406/FCC-11-54A1.pdf</font></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/04/09/fcc-releases-news-order-and-fnprm/feed/</wfw:commentRss>
		<slash:comments>38</slash:comments>
		</item>
		<item>
		<title>SVRS Ex-Parte Comments..</title>
		<link>http://www.edsalert.com/2011/03/22/svrs-ex-parte-comments/</link>
		<comments>http://www.edsalert.com/2011/03/22/svrs-ex-parte-comments/#comments</comments>
		<pubDate>Tue, 22 Mar 2011 20:56:35 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[VRS]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1581</guid>
		<description><![CDATA[All.. Check out the link. SVRS Comments SorensonVRS reiterates on the following.&#160; &#34;..in Sorenson&#8217;s comments stating that (1) the Commission should not prohibit VRS providers from operating call centers in Canada; (2) so-called &#8220;white label&#8221; operators should not be permitted to provide service; and (3) interpreters should be required to work in supervised call centers. [...]]]></description>
			<content:encoded><![CDATA[<p><font size="2" face="Tahoma">All..</p>
<p>Check out the link.</p>
<p><a href="https://prodnet.www.neca.org/publicationsdocs/wwpdf/32111sorenson.pdf">SVRS Comments</a></p>
<p>SorensonVRS reiterates on the following.&nbsp; <br /><em><br />&quot;..in Sorenson&rsquo;s comments stating that <br />(1) the Commission should not prohibit VRS providers from operating call centers in Canada; <br />(2) so-called &ldquo;white label&rdquo; operators should not be permitted to provide service; and <br />(3) interpreters should be required to work in supervised call centers. I also pointed out that the Commission needs to consider additional steps to prohibit slamming and to ensure that VRS providers do not interfere with valid attempts to change their default provider.&quot;</em></p>
<p>I do not agree on call centers in Canada being provided for USA, unless call centers in Canada provide services for Canadians.&nbsp; There are too many variables that need to be addressed first; fluency in sign language, familiarity of USA culture, etc. etc. so no not at this time.&nbsp; Maybe in future?&nbsp; </p>
<p>&quot;White label&quot; I would say that pending the FCC&#8217;s new regulations (hopefully within a few months), that issue will be resolved once and for all.&nbsp; FCC will likely do it in a professional and humanitarian manner where it will weed out the ones that do not deserve to continue, and keep the ones that actually provide a true VRS.&nbsp; So I agree, but <strong>do</strong> a due process that is fair for all.&nbsp; </p>
<p>Interpreters work in supervised call centers; that I agree.&nbsp;&nbsp; The issue is how to define &quot;supervised&quot;.&nbsp; Are overhead surveillance cameras that watch the entry/exit door as well as Video Interpreter station and that these cameras are at another location sufficient as &quot;supervised&quot;; in other words, remotely watched?&nbsp; ZVRS believe it does.&nbsp;&nbsp; </p>
<p>Prohibit slamming? Hmmm &#8211; that is an interesting comment.&nbsp; Allow me to explain why:&nbsp; <em>&ldquo;Slamming&rdquo; is the illegal practice of switching a consumer&#8217;s traditional wireline telephone company for local, local toll, or long distance service without permission.&quot;&nbsp; </em>In hearing telephone industry, that is no brainer. <em>&nbsp; </em>In VRS industry, that&#8217;s tough to do because practically all of deaf/hoh VRS users I know have more than one phone numbers; many of them have 10 digit phone numbers from each different VRS providers. Many of them use several VRS providers.&nbsp; </p>
<p>Porting is a way where deaf/hoh who wishes to port his/her phone number to a different VRS provider.&nbsp; That is permitted and allowed by the FCC. &nbsp;&nbsp; Is SVRS trying to stop porting the phone numbers to a different provider? &nbsp; I am not sure why SVRS made that statement. &nbsp;&nbsp; </p>
<p><em>&quot;VRS providers do not interfere with valid attempts to change their default provider&quot;.</em>&nbsp;&nbsp; Here, I think, the FCC needs to define what are the &quot;valid attempts&quot;; in other words, define that.&nbsp;&nbsp; Valid attempts can be considered same as &quot;pestering&quot; if the VRS representatives actually call and bother VRS users with other VRS providers for <font color="#993300">no reasons at all.</font>&nbsp;&nbsp; So need to be careful on how to define that and what is permissible and what is not permissible.&nbsp; Unfortunately this is a tough one as it touches on outreach/marketing issues.&nbsp; Outreach/marketing issues within the VRS is an ongoing issue for VRS industry and the FCC.&nbsp;&nbsp; Eventually, the FCC will need to address that.&nbsp;&nbsp; Why?&nbsp; VRS industry is funded from federal fund (even though telephone companies, etc. contribute the money to this fund; FCC does have oversight over fund) so public fund needs to be distributed fairly.&nbsp; </p>
<p>Now my dear edsalert readers, I&#8217;ll like to hear your thoughts/rants/raves/analysis/whatever.</p>
<p>eyes open &amp; thumbs up,</p>
<p>Ed</p>
<p>Long Link: https://prodnet.www.neca.org/publicationsdocs/wwpdf/32111sorenson.pdf</font></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/03/22/svrs-ex-parte-comments/feed/</wfw:commentRss>
		<slash:comments>32</slash:comments>
		</item>
		<item>
		<title>April 7 Agenda for FCC Commissioners Open Meeting</title>
		<link>http://www.edsalert.com/2011/03/18/april-7-agenda-for-fcc-commissioners-open-meeting/</link>
		<comments>http://www.edsalert.com/2011/03/18/april-7-agenda-for-fcc-commissioners-open-meeting/#comments</comments>
		<pubDate>Fri, 18 Mar 2011 16:43:25 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[VRS]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1573</guid>
		<description><![CDATA[Folks.. There are several items for the Open Meeting on April 7, but what caught my eye was this one item.&#160;&#160; &#160; Structure and Practices of Video Relay Service Program:&#160; Report and Order will adopt rules to detect and prevent fraud and abuse in the provision of video relay service (&#8220;VRS&#8221;).&#160; Also, a Further Notice [...]]]></description>
			<content:encoded><![CDATA[<p><font size="2" face="Verdana">Folks..</p>
<p>There are several items for the Open Meeting on April 7, but what caught my eye was this one item.&nbsp;&nbsp; </font><br />&nbsp;<br />
<style type="text/css">@font-face {
  font-family: "Arial";
}@font-face {
  font-family: "Courier New";
}@font-face {
  font-family: "Wingdings";
}p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman"; }div.Section1 { page: Section1; }ol { margin-bottom: 0in; }ul { margin-bottom: 0in; }</style>
<ul type="disc" style="margin-top: 0in;">
<li style="" class="MsoNormal"><font color="#800080"><strong><span style="font-size: 11pt; font-family: &quot;Times New Roman&quot;;">Structure and      Practices of Video Relay Service Program:</span></strong><span style="font-size: 11pt; font-family: &quot;Times New Roman&quot;;">&nbsp; Report and      Order<strong style=""> </strong>will adopt rules to      detect and prevent fraud and abuse in the provision of video relay service      (&ldquo;VRS&rdquo;).&nbsp; Also, a Further Notice of Proposed Rulemaking proposes to      require all VRS providers to obtain certification from the FCC under new,      tighter certification procedures in order to receive compensation from the      TRS Fund.</span></font></li>
</ul>
<p><font size="2" face="Verdana">The language on <font color="#800080">&quot;Report and Order to adopt rules to detect and prevent fraud and abuse&quot;</font>.&nbsp;&nbsp; That&#8217;s simply GREAT and about time.&nbsp; I am already visualizing a tall, sturdy Oak tree with strong branch, and noose hanging loose from the branch waiting for the guilty ones.&nbsp;&nbsp; </p>
<p>Another language that was intriguing is <font color="#800080">&quot;..to require all VRS providers to obtain certification..&quot; and this &quot;..under new, tighter certification procedures..&quot;</font>. &nbsp;&nbsp; This to me seems to mean ALL VRS providers including certified and possibly non-certified providers.&nbsp; That, too, is good. This could very well help FCC whittle down number of VRS providers out there now.&nbsp;&nbsp; Visualization here is the guillitone block &#8211; it will be interesting to note which VRS provider&#8217;s head will be chopped off. </p>
<p>This Open Meeting will be available for viewing via Internet.&nbsp; <font color="#800080">&quot;..</font></font><font color="#800080">           </font><br />
<style type="text/css">@font-face {
  font-family: "Arial";
}p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman"; }a:link, span.MsoHyperlink { font-family: "Times New Roman"; color: blue; text-decoration: underline; }a:visited, span.MsoHyperlinkFollowed { color: purple; text-decoration: underline; }div.Section1 { page: Section1; }</style>
<p>   <span style="font-size: 11pt; font-family: &quot;Times New Roman&quot;;"><font color="#800080">watch the live stream at <a href="http://www.fcc.gov/live">www.fcc.gov/live</a>.&quot;. </font>&nbsp;</span> </p>
<p><font size="2" face="Verdana">Gentle Readers, this is one live stream I will be watching and you all should, too.&nbsp;&nbsp; I hope it will be captioned, though.</p>
<p>eyes open &amp; thumbs up..</p>
<p>Ed B</font></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/03/18/april-7-agenda-for-fcc-commissioners-open-meeting/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

