<?xml version="1.0" encoding="iso-8859-1"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Ryan Croke is learning.</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/" />
    <link rel="self" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/atom.xml" />
   <id>tag:pactlab.spcomm.uiuc.edu,2008:/blog/ryancroke//33</id>
    <link rel="service.post" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33" title="Ryan Croke is learning." />
    <updated>2007-06-12T06:06:41Z</updated>
    <subtitle>Ideas about videophone technology, especially as it affects the American Deaf community.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2</generator>
 
<entry>
    <title>Slideshow</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2007/06/slideshow.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1715" title="Slideshow" />
    <id>tag:pactlab.spcomm.uiuc.edu,2007:/blog/ryancroke//33.1715</id>
    
    <published>2007-06-12T01:27:21Z</published>
    <updated>2007-06-12T06:06:41Z</updated>
    
    <summary>Download file...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/Deaf%2BBB%2BAccess.ppt">Download file</a></p>]]>
        
    </content>
</entry>
<entry>
    <title>The iSight mystery revealed</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/09/the_isight_mystery_revealed.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1698" title="The iSight mystery revealed" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1698</id>
    
    <published>2006-09-16T14:18:38Z</published>
    <updated>2006-09-16T18:23:52Z</updated>
    
    <summary>In response to my two questions** posted earlier this week, I have confirmed (thanks to the help of your comments) that there are at least 2 companies through which VRS calls can be completed using the Apple iSight web cam....</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p>In response to my two questions** posted earlier this week, I have confirmed (thanks to the help of your comments) that there are at least 2 companies through which VRS calls can be completed using the Apple iSight web cam. </p>

<p><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/HOVRS%20on%20IM.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/HOVRS%20on%20IM.html','popup','width=980,height=707,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/HOVRS%20on%20IM-thumb.png" width="277" height="200" alt="" /></a><br />
<font color=red><b>Hands-On VRS (HOVRS) -- through AOL Instant Messenger (IM) video chat.</b></font><br />
(Plus, check out this video about the <a href="http://video.google.com/videoplay?docid=-3854013475407316896&q=deaf">HOVRS Mac-only widget.</a>)<br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/LLVRS-SIGHTSPEED.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/LLVRS-SIGHTSPEED.html','popup','width=693,height=522,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/LLVRS-SIGHTSPEED-thumb.png" width="265" height="200" alt="" /></a><br />
<font color=red><b>LifeLinks VRS -- through <a href="www.sightspeed.com">SightSpeed</a>.</b></font></p>

<p>With both options, you have to add VRS interpreter "addresses" to your buddy list/phone book. The process for doing that in LifeLinks is more time consuming.<br />
For non-Mac lovers, IM and SightSpeed do support some non-iSight web cams and are fully compatible on PCs.</p>

<p>As for my second question (about calling IP-based videophones like the VP-100 or i2eye with an iSight), I have not found a way to do it, but I am holding out hope that it's possible. </p>

<p>**<br />
1. Are any Video Relay Services available to those with the Apple iSight?<br />
2. Can the iSight be used to place a call to an IP-based videophone?</p>]]>
        
    </content>
</entry>
<entry>
    <title>Polycom Via Video II</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/09/polycom_via_video_ii.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1697" title="Polycom Via Video II" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1697</id>
    
    <published>2006-09-16T00:34:12Z</published>
    <updated>2006-09-16T18:28:00Z</updated>
    
    <summary>Does anyone out there use this product, or know someone who does? How is it? I&apos;d love to know more about it from a consumer&apos;s perspective. It retails for $480 here, but I found it for less (though not by...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p>Does anyone out there use this product, or know someone who does? How is it? I'd love to know more about it from a consumer's perspective.</p>

<p><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/0%2C1444%2C807%2C00.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/0%2C1444%2C807%2C00.html','popup','width=394,height=194,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/0%2C1444%2C807%2C00-thumb.jpg" width="203" height="100" alt="" /></a></p>

<p>It retails for $480 <a href="http://www.picturephone.com/products/polycom_viavideo_2.htm">here</a>, but I found it for less (though not by much) on <a href="http://froogle.google.com/froogle?q=%22Via+Video+II%22&btnG=Search&lmode=online&scoring=">Froogle</a>. <br />
If it's stable and compatible with the VP-100/200, there just might be a market for it among residential video telephone consumers.</p>

<p><br />
</p>]]>
        
    </content>
</entry>
<entry>
    <title>Calling all Mac lovers...</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/09/calling_all_mac_lovers_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1696" title="Calling all Mac lovers..." />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1696</id>
    
    <published>2006-09-13T03:48:19Z</published>
    <updated>2006-09-14T03:56:58Z</updated>
    
    <summary>(No, not Mac &amp; Cheese ... Macintosh!) 2 questions: 1. Are any Video Relay Services available to those with the Apple iSight? &amp; ??? 2. Can the iSight be used to place a call to an IP-based videophone? &amp; ???...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p>(No, not <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/mac_cheese_small.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/mac_cheese_small.html','popup','width=319,height=236,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false">Mac & Cheese</a> ... Macintosh!)<br />
2 questions: </p>

<p>1. Are any Video Relay Services available to those with the Apple iSight?</p>

<p><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/isightanim061303.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/isightanim061303.html','popup','width=141,height=141,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/isightanim061303-thumb.gif" width="100" height="100" alt="" /></a>     &     <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/vrs_diagram2.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/vrs_diagram2.html','popup','width=424,height=218,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/vrs_diagram2-thumb.jpg" width="194" height="100" alt="" /></a>       ???</p>

<p>2. Can the iSight be used to place a call to an IP-based videophone?</p>

<p><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/isightanim061303.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/isightanim061303.html','popup','width=141,height=141,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/isightanim061303-thumb.gif" width="100" height="100" alt="" /></a>      &     <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/i2eye%21.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/i2eye%21.html','popup','width=400,height=266,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/i2eye%21-thumb.jpg" width="150" height="100" alt="" /></a>      ???</p>

<p>I will post the answers when I find out! First one to solve this mystery for me has my total respect, and maybe a prize.</p>]]>
        
    </content>
</entry>
<entry>
    <title>VRS choices!</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/09/vrs_provider_list_update.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1676" title="VRS choices!" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1676</id>
    
    <published>2006-09-12T07:45:23Z</published>
    <updated>2006-10-06T20:17:16Z</updated>
    
    <summary>I&apos;d like this list to become a helpful resource for VRS users. Your ideas are appreciated. Service ProviderNotes on numbering protocols, etc.Deaf/HoH-initiatedHearing-initiated Users can call from videophones or webcams (by using Microsoft NetMeeting or VSoft&apos;s AT&amp;T XpressVRS software)ATTVRS.TV888-877-9998 HQ in...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<b><font color=red>I'd like this list to become a helpful resource for VRS users. <br>Your ideas are appreciated.</b></font>
<TABLE BORDER="1" CELLSPACING="2" WIDTH="100%" style="border-style: solid;">
<tr><td><strong>Service Provider</strong></td><td><strong>Notes on numbering protocols, etc.</strong></td><td><strong>Deaf/HoH-initiated</strong></td><td><strong>Hearing-initiated</strong></td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/at%26t.html" onclick="window.open('http://www.attvrs.com/help/faqs.asp'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/at%26t-thumb.jpg" width="80" height="40" alt="" /></a></td><td>Users can call from videophones or webcams (by using Microsoft NetMeeting or VSoft's AT&T XpressVRS software)</td><td>ATTVRS.TV</td><td>888-877-9998</td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/CAC.html" onclick="window.open('http://www.cacvrs.org/faq.html'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/CAC-thumb.png" width="80" height="38" alt="" /></a>
</td><td>HQ in Flint, MI </td><td>CACVRS.TV</td><td>866-500-9662</td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/CSD.html" onclick="window.open('http://www.c-s-d.org/Default.aspx?tabid=56'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/CSD-thumb.png" width="80" height="33" alt="" /></a></td><td>Offers customers personal "1-800" numbers to route hearing-initiated calls directly (through CSD VRS)  to deaf users; also offers 5-digit extension numbers, usable with CSD VRS.</td><td>CSDVRS.TV</td><td>866-410-5787</td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/GOAMERICA.html" onclick="window.open('http://www.goamerica.com/company/'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/GOAMERICA-thumb.png" width="80" height="29" alt="" /></a></td><td>Not yet in service, but approved for VRS by the FCC; runs i711.com (IP-based text relay)</td><td>N/A</td><td>N/A</td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/HAMILTON2.html" onclick="window.open('http://www.hamiltonrelay.com/support/faq/videorelay/index.htm'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/HAMILTON2-thumb.png" width="80" height="35" alt="" /></a></td><td>Uses Birnbaum Interpreting Service</td><td>CALL.HIPVRS.COM</td><td>866-498-4777</td></tr>

<tr><td> <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/HOVRS.html" onclick="window.open('http://www.hovrs.com'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/HOVRS-thumb.png" width="80" height="23" alt="" /></a>
</td><td>HQ in CA, Corporate HQ in DE; Users can register for HOVRS extension numbers; VRS contractor for AT&T and Washington state TRS since 2002</td><td>HOVRS.TV</td><td>877-467-4877</td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/MCI-VERIZON.html" onclick="window.open('http://ip-vrs.com/faq/faq_using.html'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/MCI-VERIZON-thumb.png" width="80" height="33" alt="" /></a></td><td>Owned by MCI-Verizon; hearing-initiated calls not permitted</td><td>TV.IPVRS.COM</td><td>N/A</td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/LL%20Logo.html" onclick="window.open('http://www.lifelinksvrs.com/aboutus.html'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/LL%20Logo-thumb.png" width="80" height="25" alt="" /></a></td><td>Started as Healinc Telecom; HQ in NY</td><td>69.18.207.166</td><td>877-744-6111</td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/NORDIA.html" onclick="window.open('http://www.myrelay.com/video-relay/faq.en.html?filter=Faq_Filter'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/NORDIA-thumb.png" width="80" height="18" alt="" /></a>
</td><td>Canadian company; runs myrelay.com; contractor for California state VRS</td><td>N/A</td><td>800-423-1642</td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SNAP.html" onclick="window.open('http://snapvrs.ubaccess.com/index.php@option=com_content&task=blogsection&id=3&Itemid=49.html'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SNAP-thumb.png" width="80" height="32" alt="" /></a>
</td><td>Uses Motorola Ojo</td><td>N/A</td><td>N/A</td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SORENSON.html" onclick="window.open('http://www.sorensonvrs.com/what/faq.php'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SORENSON-thumb.png" width="80" height="27" alt="" /></a></td><td>GTCR Golder Rauner, LLC <a href="http://www.tmcnet.com/scripts/print-page.aspx?PagePrint=http%3a%2f%2fwww.tmcnet.com%2fusubmit%2f2005%2fsep%2f1185317.htm">became Sorenson's majority shareholder</a> in Sept. '05; offers customers 10-digit proxy numbers for p2p VP-100 calls and hearing-initiated Sorenson VRS calls; Partnership with Gallaudet Interpreting Service; Users can call from VPs or webcams (by using Microsoft NetMeeting or Sorenson EnVision software)</td><td>VP-100/200 only</td><td>866-327-8877</td></tr>

<tr><td><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SPRINT.html" onclick="window.open('http://www.sprintvrs.com/support-info.asp#'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SPRINT-thumb.png" width="80" height="32" alt="" /></a></td><td>Under contract with GSA for to provide <a href="www.fedvrs.us">VRS for Federal employees</a>; CSD provides interpreters and call centers</td><td>SPRINTVRS.TV</td><td>866-410-5787</td></tr>

</TABLE>]]>
        <![CDATA[<br>
<br>
One can only wonder how each provider fares in terms of video relay services rendered. Federal law (47 CFR Sec. 64.604 (c)(5)(iii) prohibits the TRS Fund Administrator --NECA-- from disclosing such data in company specific form "unless directed to do so by the commission."
<br>
<br>
A similar listing is available at <a href="http://www.tdi-online.org/tdi/fs_videorelayservices.asp">TDI Online</a>.]]>
    </content>
</entry>
<entry>
    <title>Thesis ...</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/09/introduction_and_lit_review_un.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1693" title="Thesis ..." />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1693</id>
    
    <published>2006-09-12T05:01:10Z</published>
    <updated>2008-01-11T05:05:39Z</updated>
    
    <summary>FINAL.doc THESIS.31.doc THESIS.30.doc THESIS.29.doc THESIS.28.doc THESIS.27.doc THESIS.26.doc THESIS.25.doc THESIS.24.doc THESIS.23.doc THESIS.22.doc THESIS.21.doc THESIS.19.doc THESIS.18.doc THESIS.17.doc THESIS.16.doc THESIS.15.doc THESIS.14.doc THESIS.13.doc THESIS.12.doc THESIS.11.doc THESIS.10.doc THESIS.9.doc THESIS.8.doc&quot; THESIS.7.doc THESIS.6.doc THESIS.5.doc THESIS.4.doc THESIS.3.doc THESIS.2.doc THESIS.doc...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/thesisryancrokeFINAL.doc">FINAL.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/5.THESIS.31.doc">THESIS.31.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.30.doc">THESIS.30.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.29.doc">THESIS.29.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.28.doc">THESIS.28.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.27.doc">THESIS.27.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.26.doc">THESIS.26.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.25.doc">THESIS.25.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.24.doc">THESIS.24.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.23.doc">THESIS.23.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.22.doc">THESIS.22.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.21.doc">THESIS.21.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.19.doc">THESIS.19.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.18.doc">THESIS.18.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.17.doc">THESIS.17.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.16.doc">THESIS.16.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.15.doc">THESIS.15.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.14.doc">THESIS.14.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.13.doc">THESIS.13.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.12.doc">THESIS.12.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.11.doc">THESIS.11.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.10.doc">THESIS.10.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.9.doc">THESIS.9.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.8.doc">THESIS.8.doc"</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.7.doc">THESIS.7.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.6.doc">THESIS.6.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.5.doc">THESIS.5.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.4.doc">THESIS.4.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.3.doc">THESIS.3.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.2.doc">THESIS.2.doc</a><br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/THESIS.doc">THESIS.doc</a><br />
</p>]]>
        
    </content>
</entry>
<entry>
    <title>need for speed</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/09/need_for_speed.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1694" title="need for speed" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1694</id>
    
    <published>2006-09-10T07:43:52Z</published>
    <updated>2006-09-12T07:46:50Z</updated>
    
    <summary>If you use a videophone, what kind of internet connection do you have? What is the minimum frame rate *you* need for a clear conversation? Minimum frames per second required for understanding sign language or lipreading:...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p>If you use a videophone, what kind of internet connection do you have?<br />
What is the minimum frame rate *you* need for a clear conversation?</p>

<p>Minimum frames per second required for understanding sign language or lipreading:<br />
</p>]]>
        <![CDATA[<p>"An actual frame rate of 10-12 frames per second is required for a person to perceive smooth biological movement. This defines the lower limit of frame rate for a video teleconferencing system useful to deaf signers."</p>

<p>Compression Analysis<br />
ISDN …provide[s] 128 kilobits per second bandwidth. Since videoconferencing is bidirectional, 64 kilobits per second or 8,000 kilobytes per second are available for each video stream. Therefore, at an acceptable ate of 10 frames per second, an average of 800 bytes are available to code each frame. …video sequences compressed using MPEG-1 alone exceed this average and would only allow a transmission rate of 6 fps.<br />
</p>]]>
    </content>
</entry>
<entry>
    <title>NAD taking action on numbering</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/07/nad_taking_action_on_numbering.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1683" title="NAD taking action on numbering" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1683</id>
    
    <published>2006-07-26T21:37:54Z</published>
    <updated>2006-07-27T00:29:31Z</updated>
    
    <summary>3 videos with Kelby Brick, NAD&apos;s Director of Law &amp; Advocacy: (The fourth image is a link to the NAD Videophone Numbering Web page.)...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p>3 videos with Kelby Brick, NAD's Director of Law & Advocacy:</p>

<p><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/KB1.html" onclick="window.open('http://www.accessibilityconsulting.net/NADClips/intro.mov'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/KB1-thumb.png" width="100" height="78" alt="" /></a> <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/KB2.html" onclick="window.open('http://www.accessibilityconsulting.net/NADClips/explanation.mov'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/KB2-thumb.png" width="100" height="79" alt="" /></a> <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/KB3.html" onclick="window.open('http://www.accessibilityconsulting.net/NADClips/action.mov'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/KB3-thumb.png" width="100" height="80" alt="" /></a> <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/KB3.2.html" onclick="window.open('http://www.nad.org/site/pp.asp?c=foINKQMBF&b=1977809'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/KB3.2-thumb.png" width="100" height="80" alt="" /></a></p>

<p>(The fourth image is a link to the NAD Videophone Numbering Web page.)</p>]]>
        
    </content>
</entry>
<entry>
    <title>Another VRS provider?</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/07/another_vrs_provider.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1682" title="Another VRS provider?" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1682</id>
    
    <published>2006-07-26T06:29:49Z</published>
    <updated>2006-07-26T06:34:01Z</updated>
    
    <summary>What&apos;s the story on LifeLinks? Is their service approved by the FCC? (Click the pic below to visit their site.)...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p>What's the story on LifeLinks? Is their service approved by the FCC? (Click the pic below to visit their site.)<br />
<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/LifeLinks.html" onclick="window.open('http://www.lifelinksvrs.com/'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/LifeLinks-thumb.png" width="400" height="253" alt="" /></a></p>]]>
        
    </content>
</entry>
<entry>
    <title>&quot;...used by only 10 percent to 15 percent of deaf people.&quot;</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/07/used_by_only_10_percent_to_15.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1681" title="&quot;...used by only 10 percent to 15 percent of deaf people.&quot;" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1681</id>
    
    <published>2006-07-26T06:13:11Z</published>
    <updated>2006-07-26T06:29:34Z</updated>
    
    <summary>Popular video relays for deaf raise some concerns Greg Livadas, Staff writer June 6, 2006...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p><a href="http://www.democratandchronicle.com/apps/pbcs.dll/article?AID=/20060606/NEWS01/606060338/1002/NEWS">Popular video relays for deaf raise some concerns</a><br />
Greg Livadas, Staff writer<br />
June 6, 2006<br />
</p>]]>
        <![CDATA[<p>When Kris Frei wants to talk to a friend across the country, she simply sits in front of a Web camera and begins using sign language.</p>

<p>Thousands of Americans who are deaf are finding video relay to be an easier and cheaper alternative to making calls via text telephones, or TTYs. Like many deaf people sold on video conversations, Frei doesn't have use for a telephone anymore.</p>

<p>"It's easier," said Frei, of Henrietta. "We can sign. We can communicate with our native language. And I like to see the facial expressions."</p>

<p>When Frei needs to call someone who doesn't know sign language, she uses a video relay center with sign language interpreters who make the calls for her.</p>

<p>The popularity of video relay services has exploded in the past four years. About 7,200 minutes of video relay were used per month when video relay began in January 2002, according to the Federal Communications Commission, which regulates the service. By December 2005, more than 3 million minutes of video relay were used per month, with eight companies providing the service.</p>

<p>It's a booming business, with two video relay centers in Henrietta and more companies expected nationwide.</p>

<p>The potential for growth is tremendous because the service is used by only 10 percent to 15 percent of deaf people.</p>

<p>While the service is a boon for deaf users, its explosion carries ramifications:</p>

<p><br />
Shortages of interpreters available to work in the community.<br />
Millions raised from every U.S. phone bill to help pay for the services.</p>

<p>A discontinuation of some 24-hour video relay services if companies aren't reimbursed as needed to provide the service.<br />
In Henrietta, dozens of sign language interpreters convey messages to and from deaf and hearing people nationwide. The companies opened centers here, where they could draw qualified interpreters from the area and other upstate communities.</p>

<p>The Rochester area has about 300 professional sign language interpreters; more than 100 are on staff at Rochester Institute of Technology's National Technical Institute for the Deaf.</p>

<p>"We have to go where there's a pool of interpreters," said Pat Nola, president and CEO of Sorenson Communications, a Salt Lake City-based company that opened a relay center here in February.</p>

<p>Communication Services for the Deaf, based in Sioux Falls, S.D., opened a video relay center in Henrietta in 2003.</p>

<p>Interpreter need</p>

<p>Some think that the dozens of interpreters working in the call centers are draining the local pool of interpreters available to work in the community. Each center relies on more than 30 interpreters who work full or part time. They travel from as far away as Syracuse, Buffalo, Ithaca, Elmira and Binghamton to work at the centers, which has caused interpreter shortages in those communities as well.</p>

<p>Nancy Berlove, who owns Sign Language Connection, one of several local companies that hire interpreters for community needs, said there was a shortage of interpreters locally even before the relay centers opened.</p>

<p>"Requests are not being met, the interpreting pool has dwindled, so you end up pushing the noncertified people a little more," she said. "You can't substitute for skill and experience."</p>

<p>Berlove said the rates paid to community interpreters — currently ranging from $35 to $45 an hour, although they don't work 40-hour weeks — may have to rise to keep them working in the community rather than in the video relay centers, which can provide a more attractive work setting.</p>

<p>"You don't have to drive, park, pay tolls. ... I can schedule myself for five hours in a row with VRS, and you have the support of other interpreters. ... It's really a nice environment," Berlove said. "It's so variable in the community."</p>

<p>Funding source</p>

<p>Video relay calls are free for the users, paid for with funds from phone companies and a small charge on land and cell phone bills. TTY users who opt to place calls through traditional relay centers have to pay for long-distance calls, although the rates are adjusted to reflect the longer times needed to have a typed conversation.</p>

<p>Fina Perez of Henrietta said video relay calls are much faster than traditional text telephone calls. Some deaf people may be uncomfortable using English, which may not be their first language.</p>

<p>"Before video relay, there were a lot of misunderstandings," Perez said.</p>

<p>Video relay consumers don't pay to use the service per minute as they would a long-distance TTY relay call "because there is no geographical correlation with the Internet," said Gregory Hlibok, a lawyer with the Disability Rights Office at the FCC.</p>

<p>The relay providers don't have the technological means to identify the caller's originating location, so no billing mechanism is in place.</p>

<p>Like many deaf people, Anthony Di Giovanni, 35, of Rochester keeps a text pager on his hip; his thumbs can type an e-mail or instant message in no time.</p>

<p>"When I'm fishing in a boat out on the water, who am I going to call if I need help? I'll use this," he said. "Thank you, America! It's a wonderful country!"</p>

<p>He can thank every person who pays a phone bill in the United States. The FCC has $441.5 million to pay relay providers this year for their services. About half of that goes to video relay services, with the rest going to more traditional TTY centers. The money is obtained either through a fee of 10 or 15 cents collected on every phone bill, or as a telephone company's overhead expenses.</p>

<p>The Americans with Disabilities Act says relay services must be available at no extra cost to the user, but video relay could be viewed as a luxury, Nola said.</p>

<p>Hlibok, himself deaf, said video relay is considered a necessity to many users of American Sign Language because of its quickness, as opposed to traditional TTY relay. An insurance claim through TTY relay could take up to an hour, whereas video relay could take as little as 15 minutes, he said.</p>

<p>Video relay companies used to get paid $17 a minute for each call they relayed. But that figure is now set at $6.11 a minute, a low figure that may jeopardize the current services provided, Nola said.</p>

<p>The FCC has received from the National Exchange Carrier Association, which oversees the fund, a proposal of $386.3 million for relay funding through June 2007, with plans to reimburse video relay firms $6.13 a minute for their services. Traditional relay centers, using TTYs, would be reimbursed $1.26 per minute.</p>

<p>"I'm a bit nervous that companies like ours might not be able to offer an effective service for the future," Nola told a room full of video relay users during an open house at the new center in Henrietta recently. "We don't care in the long run which company you use. We need to be able to protect the service as a whole."</p>

<p>Other news accounts of VRS:<br />
http://www.wired.com/news/technology/1,70585-0.html<br />
http://www.sorenson.com/press/reviews.php</p>]]>
    </content>
</entry>
<entry>
    <title>Critical meeting on videophone numbering</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/07/critical_issues_in_videophone.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1680" title="Critical meeting on videophone numbering" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1680</id>
    
    <published>2006-07-25T19:52:47Z</published>
    <updated>2006-07-25T20:30:25Z</updated>
    
    <summary> The ATIS VoIP subcommittee met July 13 to discuss ways to deploy a centralized videophone numbering network for VRS users. Sprint and Sorenson have contributed technical proposals to this subcommittee (similar to their numbering comments to the FCC), but...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/atis-logo.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/atis-logo.html','popup','width=187,height=80,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/atis-logo-thumb.jpg" width="187" height="80" alt="" /></a></p>

<p>The ATIS VoIP subcommittee met July 13 to discuss ways to deploy a centralized videophone numbering network for VRS users. Sprint and Sorenson have contributed technical proposals to this subcommittee (similar to their <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/07/vrs_numbering_fnpr_replies.html#more">numbering comments to the FCC</a>), but mostly Sprint's proposal was discussed.</p>

<p>"Points noted" at the meeting:</p>]]>
        <![CDATA[<p>1.  TRS is a service that connects those who are hearing to those who are deaf.  It is currently available in fifty states.  There are no costs to the end users, with the possible exception to toll service for some calls.  </p>

<p>2.  It was noted that there are three challenges to Internet Based Calling which needs to be worked out by the Industry, they are: Personal Telephone Numbers, Access to Emergency 9-1-1 Services, National Directory Services.</p>

<p>3.  It was noted that in the contribution the term “Deaf” refers to any person who is deaf, hard of hearing, has a speech disability, or other need that requires them to use TRS services.  Currently, deaf people using Internet-based relay services rely on the relay provider to make and receive calls. Sprint-Nextel laid out several problems and solutions for relay provider services in order to become equivalent to hearing users as it relates to numbering.</p>

<p>4.  It was noted that a number can only be assigned where service providers agree to set an AIN [Advanced Intelligent Network] to handle the routing of the relay services.  A similar program is being used in California.  Remote Call Forwarding would be another option that wouldn’t require an AIN application that LECs could provide to support this.</p>

<p>5.  It was noted that for both local and long distance calls a hearing user chooses their service provider; this contribution will allow those using a relay service to also choose the service provider.</p>

<p>6.  It was noted that a more sophisticated solution would be to allow a user to change VRS providers depending on a per call basis. </p>

<p>7.  It was noted that in order to assign numbers in a rate center, interconnection between local services will be needed so that these services are similar to national carriers.  It was further noted that this will allow deaf users to have indistinguishable numbers to hearing users.  </p>

<p>8.  It was noted that in order ensure that the best interest of the customer is met, the relay providers should be allowed to provide the full service to their customers; therefore it does make sense for those providers to incur those costs and then receive reimbursement from the FCC.</p>

<p>9.  It was noted that this contribution largely addresses policy, and INC may not be the forum to address these policy questions or issues related to cost.  It was noted in response that the discussion around cost is not specific costs that the INC is trying to solve; should policy issues be identified they will be forwarded to the correct agency responsible for policy decisions.</p>

<p>10.  It was noted that phone numbers used by deaf customers should be involved with the reimbursement process similar to hearing customers.  These numbers will be allowed to be forwarded to the service provider of choice.  </p>

<p>11. It was noted that the FCC does want interoperability between carriers, and these numbering issues will need to be provided.   In addition a database should be administered that would meet the needs of these calls, so that from a numbering prospective, calls for both deaf and hearing customers are equivalent.</p>

<p>12.  It was noted that there are potential choices to be looked into. One is a customer selecting a VRS service provider to make and receive calls. When a VRS end user wants to change service providers it might be difficult for the customer to change service providers.  Another option would be to go through a centralized approach, whereby a customer would go through a third party when obtaining numbers.  If a neutral third party controlled these types of changes it might ensure fair competition between service providers.</p>

<p>13.  It was noted that INC Members should decide what areas of interest/concern are important to be addressed regarding this issue.  Brainstorming ideas were captured and will be attached to the Minutes.</p>

<p>Action Item:</p>

<p>1.  The VoIP Co-Chair will prepare a matrix based on the brainstorming ideas noted above ...</p>

<p>HERE IS THAT MATRIX:</p>

<p>Centralized (Neutral Third Party) or Distributed Number and VRS SP Selection</p>

<p>10-Digit Destination Decision Based on New Database of Existing SSS-7</p>

<p>VRS Selection Based upon End-User or Originating Caller<br />
-	process for changing VRS provider<br />
-	out-going vs. in-coming calls</p>

<p>Business-relationship between VRS Providers with LEC/VoIP Providers when obtaining telephone numbers</p>

<p>Directory information mechanisms (4-1-1)</p>

<p>9-1-1 Considerations</p>

<p>Number Assignment Reporting Guideline requirements</p>

<p>IP-IP interconnection utility (dynamic database look-up)<br />
-	National Database<br />
-	TNs assignable for net to net and non-PSTN calls only?<br />
</p>]]>
    </content>
</entry>
<entry>
    <title>Comments on Snap&apos;s waiver request</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/07/comments_on_snaps_waiver_reque.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1679" title="Comments on Snap's waiver request" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1679</id>
    
    <published>2006-07-25T18:28:55Z</published>
    <updated>2006-07-25T18:35:10Z</updated>
    
    <summary>From WASHINGTON WATCH (A publication of the NECA Washington DC Office) Edited By Deborah Long and Robert Falkner The following oppositions have been filed in response to the request of Snap Telecommunications for a limited waiver of the [FCC&apos;s] Video...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p>From WASHINGTON WATCH (A publication of the NECA Washington DC Office)<br />
Edited By Deborah Long and Robert Falkner</p>

<p>The following oppositions have been filed in response to the request of Snap Telecommunications for a limited waiver of the [FCC's] Video Relay Service interoperability requirements. </p>

<p><a href="http://www.neca.org/wawatch/wwpdf/072506_3.pdf">CSDVRS</a> <br />
<a href="http://www.neca.org/wawatch/wwpdf/072506_4.pdf">HOVRS</a><br />
<a href="http://www.neca.org/wawatch/wwpdf/072506_5.pdf">Sorenson VRS</a><br />
<a href="http://www.neca.org/wawatch/wwpdf/072506_6.pdf">Telecommunications for the Deaf</a></p>]]>
        
    </content>
</entry>
<entry>
    <title>Interoperability&apos;s consequences</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/07/interoperabilitys_consequences.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1678" title="Interoperability's consequences" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1678</id>
    
    <published>2006-07-25T18:00:41Z</published>
    <updated>2006-08-02T20:02:17Z</updated>
    
    <summary> In response to this message, which is programmed to appear when VP-100 users dial non-Sorenson relay providers, Hands-On VRS filed this complaint with the FCC. It draws the following comparison: &quot;...Imagine if AT&amp;T distributed a telephone to the public...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SorenAlert.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SorenAlert.html','popup','width=868,height=366,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SorenAlert-thumb.png" width="300" height="126" alt="" /></a></p>

<p>In response to this message, which is programmed to appear when VP-100 users dial non-Sorenson relay providers, Hands-On VRS filed <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/HOVRScomplaint.pdf">this complaint</a> with the FCC. It draws the following comparison:</p>

<blockquote><i>"...Imagine if AT&T distributed a telephone to the public which intercepted calls destined for other long distance providers, stated that AT&T could not vouch for the quality of the telephone transmission, and asked if the caller still desired to make the call. The Commission would not stand for this. Yet, that is exactly what Sorenson is doing here..."</i></blockquote>

<p>In response, Sorenson filed <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SorensonInteropReply.pdf">these comments</a>.</p>

<p>As always, your comments are welcome.</p>]]>
        <![CDATA[<p><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SorensonInteropPR.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SorensonInteropPR.html','popup','width=584,height=544,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/SorensonInteropPR-thumb.png" width="400" height="373" alt="" /></a></p>]]>
    </content>
</entry>
<entry>
    <title>Mandatory minimum requirements</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/07/mandatory_minimum_requirements.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1675" title="Mandatory minimum requirements" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1675</id>
    
    <published>2006-07-21T01:12:06Z</published>
    <updated>2006-07-24T16:55:20Z</updated>
    
    <summary> 7/24 UPDATE: VRS... Standards are part of the FCC&apos;s regs promulgated for TRS and are available at 47 C.F.R. § 64.601 - 64.605. The Minimum Standards are set forth at section 604. These regs are subject of course to...</summary>
    <author>
        <name>croke</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<p><font color=red> 7/24 UPDATE: </font></p>

<p>VRS<font color=blue>... Standards are part of the FCC's regs promulgated for TRS and are available at 47 C.F.R. § 64.601 - 64.605.  The Minimum Standards are set forth at section 604.  These regs are subject of course to FCC and court interpretation and supplementation through various orders ...</p>

<p>You can get copies of the regs (and any other federal regs) pretty easily at <a href="http://www.findlaw.com/casecode/cfr.html">this website</a>: </font></p>

<p>47 C.F.R. § 64.604 after the fold...</p>]]>
        <![CDATA[<p>Does anyone know where I can find a list of the FCC's mandatory minimum requirements for VRS providers?  OHH YEAH:</p>

<p>[Code of Federal Regulations]<br />
[Title 47, Volume 3]<br />
[Revised as of October 1, 2005]<br />
From the U.S. Government Printing Office via GPO Access<br />
[CITE: 47CFR64.604]</p>

<p>[Page 265-273]<br />
 <br />
                       TITLE 47--TELECOMMUNICATION<br />
 <br />
        CHAPTER I--FEDERAL COMMUNICATIONS COMMISSION (CONTINUED)<br />
 <br />
PART 64_MISCELLANEOUS RULES RELATING TO COMMON CARRIERS--Table of Contents<br />
 <br />
    Subpart F_Telecommunications Relay Services and Related Customer <br />
            Premises Equipment for Persons With Disabilities<br />
 <br />
Sec. 64.604  Mandatory minimum standards.</p>

<p>    The standards in this section are applicable December 18, 2000, <br />
except as stated in paragraphs (c)(2) and (c)(7) of this section.<br />
    (a) Operational standards--(1) Communications assistant (CA). (i) <br />
TRS providers are responsible for requiring that all CAs be sufficiently <br />
trained to effectively meet the specialized communications needs of <br />
individuals with hearing and speech disabilities.<br />
    (ii) CAs must have competent skills in typing, grammar, spelling, <br />
interpretation of typewritten ASL, and familiarity with hearing and <br />
speech disability cultures, languages and etiquette. CAs must possess <br />
clear and articulate voice communications.<br />
    (iii) CAs must provide a typing speed of a minimum of 60 words per <br />
minute. Technological aids may be used to</p>

<p>[[Page 266]]</p>

<p>reach the required typing speed. Providers must give oral-to-type tests <br />
of CA speed.<br />
    (iv) TRS providers are responsible for requiring that VRS CAs are <br />
qualified interpreters. A ``qualified interpreter'' is able to interpret <br />
effectively, accurately, and impartially, both receptively and <br />
expressively, using any necessary specialized vocabulary.<br />
    (v) CAs answering and placing a TTY-based TRS or VRS call must stay <br />
with the call for a minimum of ten minutes. CAs answering and placing an <br />
STS call must stay with the call for a minimum of fifteen minutes.<br />
    (vi) TRS providers must make best efforts to accommodate a TRS <br />
user's requested CA gender when a call is initiated and, if a transfer <br />
occurs, at the time the call is transferred to another CA.<br />
    (vii) TRS shall transmit conversations between TTY and voice callers <br />
in real time.<br />
    (2) Confidentiality and conversation content. (i) Except as <br />
authorized by section 705 of the Communications Act, 47 U.S.C. 605, CAs <br />
are prohibited from disclosing the content of any relayed conversation <br />
regardless of content, and with a limited exception for STS CAs, from <br />
keeping records of the content of any conversation beyond the duration <br />
of a call, even if to do so would be inconsistent with state or local <br />
law. STS CAs may retain information from a particular call in order to <br />
facilitate the completion of consecutive calls, at the request of the <br />
user. The caller may request the STS CA to retain such information, or <br />
the CA may ask the caller if he wants the CA to repeat the same <br />
information during subsequent calls. The CA may retain the information <br />
only for as long as it takes to complete the subsequent calls.<br />
    (ii) CAs are prohibited from intentionally altering a relayed <br />
conversation and, to the extent that it is not inconsistent with <br />
federal, state or local law regarding use of telephone company <br />
facilities for illegal purposes, must relay all conversation verbatim <br />
unless the relay user specifically requests summarization, or if the <br />
user requests interpretation of an ASL call. An STS CA may facilitate <br />
the call of an STS user with a speech disability so long as the CA does <br />
not interfere with the independence of the user, the user maintains <br />
control of the conversation, and the user does not object. Appropriate <br />
measures must be taken by relay providers to ensure that confidentiality <br />
of VRS users is maintained.<br />
    (3) Types of calls. (i) Consistent with the obligations of <br />
telecommunications carrier operators, CAs are prohibited from refusing <br />
single or sequential calls or limiting the length of calls utilizing <br />
relay services.<br />
    (ii) Relay services shall be capable of handling any type of call <br />
normally provided by telecommunications carriers unless the Commission <br />
determines that it is not technologically feasible to do so. Relay <br />
service providers have the burden of proving the infeasibility of <br />
handling any type of call.<br />
    (iii) Relay service providers are permitted to decline to complete a <br />
call because credit authorization is denied.<br />
    (iv) Relay services shall be capable of handling pay-per-call calls.<br />
    (v) TRS providers are required to provide the following types of TRS <br />
calls: (1) Text-to-voice and voice-to-text; (2) VCO, two-line VCO, VCO-<br />
to-TTY, and VCO-to-VCO; (3) HCO, two-line HCO, HCO-to-TTY, HCO-to-HCO.<br />
    (vi) TRS providers are required to provide the following features: <br />
(1) Call releasefunctionality; (2) speed dialing functionality; and (3) <br />
three-way calling functionality.<br />
    (vii) Voice mail and interactive menus. CAs must alert the TRS user <br />
to the presence of a recorded message and interactive menu through a hot <br />
key on the CA's terminal. The hot key will send text from the CA to the <br />
consumer's TTY indicating that a recording or interactive menu has been <br />
encountered. Relay providers shall electronically capture recorded <br />
messages and retain them for the length of the call. Relay providers may <br />
not impose any charges for additional calls, which must be made by the <br />
relay user in order to complete calls involving recorded or interactive <br />
messages.<br />
    (viii) TRS providers shall provide, as TRS features, answering <br />
machine and voice mail retrieval.<br />
    (4) Handling of emergency calls. Providers must use a system for <br />
incoming</p>

<p>[[Page 267]]</p>

<p>emergency calls that, at a minimum, automatically and immediately <br />
transfers the caller to an appropriate Public Safety Answering Point <br />
(PSAP). An appropriate PSAP is either a PSAP that the caller would have <br />
reached if he had dialed 911 directly, or a PSAP that is capable of <br />
enabling the dispatch of emergency services to the caller in an <br />
expeditious manner.<br />
    (5) STS called numbers. Relay providers must offer STS users the <br />
option to maintain at the relay center a list of names and telephone <br />
numbers which the STS user calls. When the STS user requests one of <br />
these names, the CA must repeat the name and state the telephone number <br />
to the STS user. This information must be transferred to any new STS <br />
provider.<br />
    (b) Technical standards--(1) ASCII and Baudot. TRS shall be capable <br />
of communicating with ASCII and Baudot format, at any speed generally in <br />
use.<br />
    (2) Speed of answer. (i) TRS providers shall ensure adequate TRS <br />
facility staffing to provide callers with efficient access under <br />
projected calling volumes, so that the probability of a busy response <br />
due to CA unavailability shall be functionally equivalent to what a <br />
voice caller would experience in attempting to reach a party through the <br />
voice telephone network.<br />
    (ii) TRS facilities shall, except during network failure, answer 85% <br />
of all calls within 10 seconds by any method which results in the <br />
caller's call immediately being placed, not put in a queue or on hold. <br />
The ten seconds begins at the time the call is delivered to the TRS <br />
facility's network. A TRS facility shall ensure that adequate network <br />
facilities shall be used in conjunction with TRS so that under projected <br />
calling volume the probability of a busy response due to loop trunk <br />
congestion shall be functionally equivalent to what a voice caller would <br />
experience in attempting to reach a party through the voice telephone <br />
network.<br />
    (A) The call is considered delivered when the TRS facility's <br />
equipment accepts the call from the local exchange carrier (LEC) and the <br />
public switched network actually delivers the call to the TRS facility.<br />
    (B) Abandoned calls shall be included in the speed-of-answer <br />
calculation.<br />
    (C) A TRS provider's compliance with this rule shall be measured on <br />
a daily basis.<br />
    (D) The system shall be designed to a P.01 standard.<br />
    (E) A LEC shall provide the call attempt rates and the rates of <br />
calls blocked between the LEC and the TRS facility to relay <br />
administrators and TRS providers upon request.<br />
    (iii) Speed of answer requirements for VRS providers are phased-in <br />
as follows: by January 1, 2006, VRS providers must answer 80% of all <br />
calls within 180 seconds, measured on a monthly basis; by July 1, 2006, <br />
VRS providers must answer 80% of all calls within 150 seconds, measured <br />
on a monthly basis; and by Janury 1, 2007, VRS providers must answer 80% <br />
of all calls within 120 seconds, measured on a monthly basis. Abandoned <br />
calls shall be included in the VRS speed of answer calculation.<br />
    (3) Equal access to interexchange carriers. TRS users shall have <br />
access to their chosen interexchange carrier through the TRS, and to all <br />
other operator services, to the same extent that such access is provided <br />
to voice users.<br />
    (4) TRS facilities. (i) TRS shall operate every day, 24 hours a day. <br />
Relay services that are not mandated by this Commission need not be <br />
provided every day, 24 hours a day, except VRS.<br />
    (ii) TRS shall have redundancy features functionally equivalent to <br />
the equipment in normal central offices, including uninterruptible power <br />
for emergency use.<br />
    (5) Technology. No regulation set forth in this subpart is intended <br />
to discourage or impair the development of improved technology that <br />
fosters the availability of telecommunications to person with <br />
disabilities. TRS facilities are permitted to use SS7 technology or any <br />
other type of similar technology to enhance the functional equivalency <br />
and quality of TRS. TRS facilities that utilize SS7 technology shall be <br />
subject to the Calling Party Telephone Number rules set forth at 47 CFR <br />
64.1600 et seq.<br />
    (6) Caller ID. When a TRS facility is able to transmit any calling <br />
party identifying information to the public network, the TRS facility <br />
must pass through, to the called party, at least one of the following: <br />
the number of the</p>

<p>[[Page 268]]</p>

<p>TRS facility, 711, or the 10-digit number of the calling party.<br />
    (c) Functional standards--(1) Consumer complaint logs.(i) States and <br />
interstate providers must maintain a log of consumer complaints <br />
including all complaints about TRS in the state, whether filed with the <br />
TRS provider or the State, and must retain the log until the next <br />
application for certification is granted. The log shall include, at a <br />
minimum, the date the complaint was filed, the nature of the complaint, <br />
the date of resolution, and an explanation of the resolution.<br />
    (ii) Beginning July 1, 2002, states and TRS providers shall submit <br />
summaries of logs indicating the number of complaints received for the <br />
12-month period ending May 31 to the Commission by July 1 of each year. <br />
Summaries of logs submitted to the Commission on July 1, 2001 shall <br />
indicate the number of complaints received from the date of OMB approval <br />
through May 31, 2001.<br />
    (2) Contact persons. Beginning on June 30, 2000, State TRS Programs, <br />
interstate TRS providers, and TRS providers that have state contracts <br />
must submit to the Commission a contact person and/or office for TRS <br />
consumer information and complaints about a certified State TRS <br />
Program's provision of intrastate TRS, or, as appropriate, about the TRS <br />
provider's service. This submission must include, at a minimum, the <br />
following:<br />
    (i) The name and address of the office that receives complaints, <br />
grievances, inquiries, and suggestions;<br />
    (ii) Voice and TTY telephone numbers, fax number, e-mail address, <br />
and web address; and<br />
    (iii) The physical address to which correspondence should be sent.<br />
    (3) Public access to information. Carriers, through publication in <br />
their directories, periodic billing inserts, placement of TRS <br />
instructions in telephone directories, through directory assistance <br />
services, and incorporation of TTY numbers in telephone directories, <br />
shall assure that callers in their service areas are aware of the <br />
availability and use of all forms of TRS. Efforts to educate the public <br />
about TRS should extend to all segments of the public, including <br />
individuals who are hard of hearing, speech disabled, and senior <br />
citizens as well as members of the general population. In addition, each <br />
common carrier providing telephone voice transmission services shall <br />
conduct, not later than October 1, 2001, ongoing education and outreach <br />
programs that publicize the availability of 711 access to TRS in a <br />
manner reasonably designed to reach the largest number of consumers <br />
possible.<br />
    (4) Rates. TRS users shall pay rates no greater than the rates paid <br />
for functionally equivalent voice communication services with respect to <br />
such factors as the duration of the call, the time of day, and the <br />
distance from the point of origination to the point of termination.<br />
    (5) Jurisdictional separation of costs--(i) General. Where <br />
appropriate, costs of providing TRS shall be separated in accordance <br />
with the jurisdictional separation procedures and standards set forth in <br />
the Commission's regulations adopted pursuant to section 410 of the <br />
Communications Act of 1934, as amended.<br />
    (ii) Cost recovery. Costs caused by interstate TRS shall be <br />
recovered from all subscribers for every interstate service, utilizing a <br />
shared-funding cost recovery mechanism. Except as noted in this <br />
paragraph, with respect to VRS, costs caused by intrastate TRS shall be <br />
recovered from the intrastate jurisdiction. In a state that has a <br />
certified program under Sec. 64.605, the state agency providing TRS <br />
shall, through the state's regulatory agency, permit a common carrier to <br />
recover costs incurred in providing TRS by a method consistent with the <br />
requirements of this section. Costs caused by the provision of <br />
interstate and intrastate VRS shall be recovered from all subscribers <br />
for every interstate service, utilizing a shared-funding cost recovery <br />
mechanism.<br />
    (iii) Telecommunications Relay Services Fund. Effective July 26, <br />
1993, an Interstate Cost Recovery Plan, hereinafter referred to as the <br />
TRS Fund, shall be administered by an entity selected by the Commission <br />
(administrator). The initial administrator, for an interim period, will <br />
be the National Exchange Carrier Association, Inc.<br />
    (A) Contributions. Every carrier providing interstate <br />
telecommunications</p>

<p>[[Page 269]]</p>

<p>services shall contribute to the TRS Fund on the basis of interstate <br />
end-user telecommunications revenues as described herein. Contributions <br />
shall be made by all carriers who provide interstate services, <br />
including, but not limited to, cellular telephone and paging, mobile <br />
radio, operator services, personal communications service (PCS), access <br />
(including subscriber line charges), alternative access and special <br />
access, packet-switched, WATS, 800, 900, message telephone service <br />
(MTS), private line, telex, telegraph, video, satellite, intraLATA, <br />
international and resale services.<br />
    (B) Contribution computations. Contributors' contribution to the TRS <br />
fund shall be the product of their subject revenues for the prior <br />
calendar year and a contribution factor determined annually by the <br />
Commission. The contribution factor shall be based on the ratio between <br />
expected TRS Fund expenses to interstate end-user telecommunications <br />
revenues. In the event that contributions exceed TRS payments and <br />
administrative costs, the contribution factor for the following year <br />
will be adjusted by an appropriate amount, taking into consideration <br />
projected cost and usage changes. In the event that contributions are <br />
inadequate, the fund administrator may request authority from the <br />
Commission to borrow funds commercially, with such debt secured by <br />
future years' contributions. Each subject carrier must contribute at <br />
least $25 per year. Carriers whose annual contributions total less than <br />
$1,200 must pay the entire contribution at the beginning of the <br />
contribution period. Service providers whose contributions total $1,200 <br />
or more may divide their contributions into equal monthly payments. <br />
Carriers shall complete and submit, and contributions shall be based on, <br />
a ``Telecommunications Reporting Worksheet'' (as published by the <br />
Commission in the Federal Register). The worksheet shall be certified to <br />
by an officer of the contributor, and subject to verification by the <br />
Commission or the administrator at the discretion of the Commission. <br />
Contributors' statements in the worksheet shall be subject to the <br />
provisions of section 220 of the Communications Act of 1934, as amended. <br />
The fund administrator may bill contributors a separate assessment for <br />
reasonable administrative expenses and interest resulting from improper <br />
filing or overdue contributions. The Chief of the Consumer & <br />
Governmental Affairs Bureau may waive, reduce, modify or eliminate <br />
contributor reporting requirements that prove unnecessary and require <br />
additional reporting requirements that the Bureau deems necessary to the <br />
sound and efficient administration of the TRS Fund.<br />
    (C) Data collection from TRS Providers. TRS providers shall provide <br />
the administrator with true and adequate data necessary to determine TRS <br />
fund revenue requirements and payments. TRS providers shall provide the <br />
administrator with the following: total TRS minutes of use, total <br />
interstate TRS minutes of use, total TRS operating expenses and total <br />
TRS investment in general accordance with part 32 of the Communications <br />
Act, and other historical or projected information reasonably requested <br />
by the administrator for purposes of computing payments and revenue <br />
requirements. The administrator and the Commission shall have the <br />
authority to examine, verify and audit data received from TRS providers <br />
as necessary to assure the accuracy and integrity of fund payments.<br />
    (D) [Reserved]<br />
    (E) Payments to TRS providers. TRS Fund payments shall be <br />
distributed to TRS providers based on formulas approved or modified by <br />
the Commission. The administrator shall file schedules of payment <br />
formulas with the Commission. Such formulas shall be designed to <br />
compensate TRS providers for reasonable costs of providing interstate <br />
TRS, and shall be subject to Commission approval. Such formulas shall be <br />
based on total monthly interstate TRS minutes of use. TRS minutes of use <br />
for purposes of interstate cost recovery under the TRS Fund are defined <br />
as the minutes of use for completed interstate TRS calls placed through <br />
the TRS center beginning after call set-up and concluding after the last <br />
message call unit. In addition to the data required under paragraph <br />
(c)(5)(iii)(C) of this section, all TRS providers, including providers <br />
who are not interexchange carriers, local exchange carriers, or</p>

<p>[[Page 270]]</p>

<p>certified state relay providers, must submit reports of interstate TRS <br />
minutes of use to the administrator in order to receive payments. The <br />
administrator shall establish procedures to verify payment claims, and <br />
may suspend or delay payments to a TRS provider if the TRS provider <br />
fails to provide adequate verification of payment upon reasonable <br />
request, or if directed by the Commission to do so. The TRS Fund <br />
administrator shall make payments only to eligible TRS providers <br />
operating pursuant to the mandatory minimum standards as required in <br />
Sec. 64.604, and after disbursements to the administrator for <br />
reasonable expenses incurred by it in connection with TRS Fund <br />
administration. TRS providers receiving payments shall file a form <br />
prescribed by the administrator. The administrator shall fashion a form <br />
that is consistent with parts 32 and 36 procedures reasonably tailored <br />
to meet the needs of TRS providers. The Commission shall have authority <br />
to audit providers and have access to all data, including carrier <br />
specific data, collected by the fund administrator. The fund <br />
administrator shall have authority to audit TRS providers reporting data <br />
to the administrator. The formulas should appropriately compensate <br />
interstate providers for the provision of VRS, whether intrastate or <br />
interstate.<br />
    (F) TRS providers eligible for receiving payments from the TRS Fund <br />
are:<br />
    (1) TRS facilities operated under contract with and/or by certified <br />
state TRS programs pursuant to Sec. 64.605; or<br />
    (2) TRS facilities owned by or operated under contract with a common <br />
carrier providing interstate services operated pursuant to Sec. 64.604; <br />
or<br />
    (3) Interstate common carriers offering TRS pursuant to Sec. <br />
64.604.<br />
    (G) Any eligible TRS provider as defined in paragraph (c)(5)(iii)(F) <br />
of this section shall notify the administrator of its intent to <br />
participate in the TRS Fund thirty (30) days prior to submitting reports <br />
of TRS interstate minutes of use in order to receive payment settlements <br />
for interstate TRS, and failure to file may exclude the TRS provider <br />
from eligibility for the year.<br />
    (H) Administrator reporting, monitoring, and filing requirements. <br />
The administrator shall perform all filing and reporting functions <br />
required in paragraphs (c)(5)(iii)(A) through (c)(5)(iii)(J) of this <br />
section. TRS payment formulas and revenue requirements shall be filed <br />
with the Commission on May 1 of each year, to be effective the following <br />
July 1. The administrator shall report annually to the Commission an <br />
itemization of monthly administrative costs which shall consist of all <br />
expenses, receipts, and payments associated with the administration of <br />
the TRS Fund. The administrator is required to keep the TRS Fund <br />
separate from all other funds administered by the administrator, shall <br />
file a cost allocation manual (CAM) and shall provide the Commission <br />
full access to all data collected pursuant to the administration of the <br />
TRS Fund. The administrator shall account for the financial transactions <br />
of the TRS Fund in accordance with generally accepted accounting <br />
principles for federal agencies and maintain the accounts of the TRS <br />
Fund in accordance with the United States Government Standard General <br />
Ledger. When the administrator, or any independent auditor hired by the <br />
administrator, conducts audits of providers of services under the TRS <br />
program or contributors to the TRS Fund, such audits shall be conducted <br />
in accordance with generally accepted government auditing standards. In <br />
administering the TRS Fund, the administrator shall also comply with all <br />
relevant and applicable federal financial management and reporting <br />
statutes. The administrator shall establish a non-paid voluntary <br />
advisory committee of persons from the hearing and speech disability <br />
community, TRS users (voice and text telephone), interstate service <br />
providers, state representatives, and TRS providers, which will meet at <br />
reasonable intervals (at least semi-annually) in order to monitor TRS <br />
cost recovery matters. Each group shall select its own representative to <br />
the committee. The administrator's annual report shall include a <br />
discussion of the advisory committee deliberations.<br />
    (I) Information filed with the administrator. The administrator <br />
shall keep all data obtained from contributors and TRS providers <br />
confidential and shall</p>

<p>[[Page 271]]</p>

<p>not disclose such data in company-specific form unless directed to do so <br />
by the Commission. Subject to any restrictions imposed by the Chief of <br />
the Consumer & Governmental Affairs Bureau, the TRS Fund administrator <br />
may share data obtained from carriers with the administrators of the <br />
universal support mechanisms (See 47 CFR 54.701 of this chapter), the <br />
North American Numbering Plan administration cost recovery (See 47 CFR <br />
52.16 of this chapter), and the long-term local number portability cost <br />
recovery (See 47 CFR 52.32 of this chapter). The TRS Fund administrator <br />
shall keep confidential all data obtained from other administrators. The <br />
administrator shall not use such data except for purposes of <br />
administering the TRS Fund, calculating the regulatory fees of <br />
interstate common carriers, and aggregating such fee payments for <br />
submission to the Commission. The Commission shall have access to all <br />
data reported to the administrator, and authority to audit TRS <br />
providers. Contributors may make requests for Commission nondisclosure <br />
of company-specific revenue information under Sec. 0.459 of this <br />
chapter by so indicating on the Telecommunications Reporting Worksheet <br />
at the time that the subject data are submitted. The Commission shall <br />
make all decisions regarding nondisclosure of company-specific <br />
information.<br />
    (J) The administrator's performance and this plan shall be reviewed <br />
by the Commission after two years.<br />
    (K) All parties providing services or contributions or receiving <br />
payments under this section are subject to the enforcement provisions <br />
specified in the Communications Act, the Americans with Disabilities <br />
Act, and the Commission's rules.<br />
    (6) Complaints--(i) Referral of complaint. If a complaint to the <br />
Commission alleges a violation of this subpart with respect to <br />
intrastate TRS within a state and certification of the program of such <br />
state under Sec. 64.605 is in effect, the Commission shall refer such <br />
complaint to such state expeditiously.<br />
    (ii) Intrastate complaints shall be resolved by the state within 180 <br />
days after the complaint is first filed with a state entity, regardless <br />
of whether it is filed with the state relay administrator, a state PUC, <br />
the relay provider, or with any other state entity.<br />
    (iii) Jurisdiction of Commission. After referring a complaint to a <br />
state entity under paragraph (c)(6)(i) of this section, or if a <br />
complaint is filed directly with a state entity, the Commission shall <br />
exercise jurisdiction over such complaint only if:<br />
    (A) Final action under such state program has not been taken within:<br />
    (1) 180 days after the complaint is filed with such state entity; or<br />
    (2) A shorter period as prescribed by the regulations of such state; <br />
or<br />
    (B) The Commission determines that such state program is no longer <br />
qualified for certification under Sec. 64.605.<br />
    (iv) The Commission shall resolve within 180 days after the <br />
complaint is filed with the Commission any interstate TRS complaint <br />
alleging a violation of section 225 of the Act or any complaint <br />
involving intrastate relay services in states without a certified <br />
program. The Commission shall resolve intrastate complaints over which <br />
it exercises jurisdiction under paragraph (c)(6)(iii) of this section <br />
within 180 days.<br />
    (v) Complaint procedures. Complaints against TRS providers for <br />
alleged violations of this subpart may be either informal or formal.<br />
    (A) Informal complaints--(1) Form. An informal complaint may be <br />
transmitted to the Consumer & Governmental Affairs Bureau by any <br />
reasonable means, such as letter, facsimile transmission, telephone <br />
(voice/TRS/TTY), Internet e-mail, or some other method that would best <br />
accommodate a complainant's hearing or speech disability.<br />
    (2) Content. An informal complaint shall include the name and <br />
address of the complainant; the name and address of the TRS provider <br />
against whom the complaint is made; a statement of facts supporting the <br />
complainant's allegation that the TRS provided it has violated or is <br />
violating section 225 of the Act and/or requirements under the <br />
Commission's rules; the specific relief or satisfaction sought by the <br />
complainant; and the complainant's preferred format or method of <br />
response to the complaint by the Commission and the defendant TRS <br />
provider (such as letter,</p>

<p>[[Page 272]]</p>

<p>facsimile transmission, telephone (voice/TRS/TTY), Internet e-mail, or <br />
some other method that would best accommodate the complainant's hearing <br />
or speech disability).<br />
    (3) Service; designation of agents. The Commission shall promptly <br />
forward any complaint meeting the requirements of this subsection to the <br />
TRS provider named in the complaint. Such TRS provider shall be called <br />
upon to satisfy or answer the complaint within the time specified by the <br />
Commission. Every TRS provider shall file with the Commission a <br />
statement designating an agent or agents whose principal responsibility <br />
will be to receive all complaints, inquiries, orders, decisions, and <br />
notices and other pronouncements forwarded by the Commission. Such <br />
designation shall include a name or department designation, business <br />
address, telephone number (voice and TTY), facsimile number and, if <br />
available, internet e-mail address.<br />
    (B) Review and disposition of informal complaints. (1) Where it <br />
appears from the TRS provider's answer, or from other communications <br />
with the parties, that an informal complaint has been satisfied, the <br />
Commission may, in its discretion, consider the matter closed without <br />
response to the complainant or defendant. In all other cases, the <br />
Commission shall inform the parties of its review and disposition of a <br />
complaint filed under this subpart. Where practicable, this information <br />
shall be transmitted to the complainant and defendant in the manner <br />
requested by the complainant (e.g., letter, facsmile transmission, <br />
telephone (voice/TRS/TTY) or Internet e-mail.<br />
    (2) A complainant unsatisfied with the defendant's response to the <br />
informal complaint and the staff's decision to terminate action on the <br />
informal complaint may file a formal complaint with the Commission <br />
pursuant to paragraph (c)(6)(v)(C) of this section.<br />
    (C) Formal complaints. A formal complaint shall be in writing, <br />
addressed to the Federal Communications Commission, Enforcement Bureau, <br />
Telecommunications Consumer Division, Washington, DC 20554 and shall <br />
contain:<br />
    (1) The name and address of the complainant,<br />
    (2) The name and address of the defendant against whom the complaint <br />
is made,<br />
    (3) A complete statement of the facts, including supporting data, <br />
where available, showing that such defendant did or omitted to do <br />
anything in contravention of this subpart, and<br />
    (4) The relief sought.<br />
    (D) Amended complaints. An amended complaint setting forth <br />
transactions, occurrences or events which have happened since the filing <br />
of the original complaint and which relate to the original cause of <br />
action may be filed with the Commission.<br />
    (E) Number of copies. An original and two copies of all pleadings <br />
shall be filed.<br />
    (F) Service. (1) Except where a complaint is referred to a state <br />
pursuant to Sec. 64.604(c)(6)(i), or where a complaint is filed <br />
directly with a state entity, the Commission will serve on the named <br />
party a copy of any complaint or amended complaint filed with it, <br />
together with a notice of the filing of the complaint. Such notice shall <br />
call upon the defendant to satisfy or answer the complaint in writing <br />
within the time specified in said notice of complaint.<br />
    (2) All subsequent pleadings and briefs shall be served by the <br />
filing party on all other parties to the proceeding in accordance with <br />
the requirements of Sec. 1.47 of this chapter. Proof of such service <br />
shall also be made in accordance with the requirements of said section.<br />
    (G) Answers to complaints and amended complaints. Any party upon <br />
whom a copy of a complaint or amended complaint is served under this <br />
subpart shall serve an answer within the time specified by the <br />
Commission in its notice of complaint. The answer shall advise the <br />
parties and the Commission fully and completely of the nature of the <br />
defense and shall respond specifically to all material allegations of <br />
the complaint. In cases involving allegations of harm, the answer shall <br />
indicate what action has been taken or is proposed to be taken to stop <br />
the occurrence of such harm. Collateral or immaterial issues shall be <br />
avoided in answers and every effort should be made to narrow the issues. <br />
Matters alleged</p>

<p>[[Page 273]]</p>

<p>as affirmative defenses shall be separately stated and numbered. Any <br />
defendant failing to file and serve an answer within the time and in the <br />
manner prescribed may be deemed in default.<br />
    (H) Replies to answers or amended answers. Within 10 days after <br />
service of an answer or an amended answer, a complainant may file and <br />
serve a reply which shall be responsive to matters contained in such <br />
answer or amended answer and shall not contain new matter. Failure to <br />
reply will not be deemed an admission of any allegation contained in <br />
such answer or amended answer.<br />
    (I) Defective pleadings. Any pleading filed in a complaint <br />
proceeding that is not in substantial conformity with the requirements <br />
of the applicable rules in this subpart may be dismissed.<br />
    (7) Treatment of TRS customer information. Beginning on July 21, <br />
2000, all future contracts between the TRS administrator and the TRS <br />
vendor shall provide for the transfer of TRS customer profile data from <br />
the outgoing TRS vendor to the incoming TRS vendor. Such data must be <br />
disclosed in usable form at least 60 days prior to the provider's last <br />
day of service provision. Such data may not be used for any purpose <br />
other than to connect the TRS user with the called parties desired by <br />
that TRS user. Such information shall not be sold, distributed, shared <br />
or revealed in any other way by the relay center or its employees, <br />
unless compelled to do so by lawful order.</p>

<p>[65 FR 38436, June 21, 2000, as amended at 65 FR 54804, Sept. 11, 2000; <br />
67 FR 13229, Mar. 21, 2002; 68 FR 50977, Aug. 25, 2003; 69 FR 5719, Feb. <br />
6, 2004; 69 FR 53351, Sept. 1, 2004; 69 FR 55985, Sept. 17, 2004; 69 FR <br />
57231, Sept. 24, 2004; 70 FR 51658, Aug. 31, 2005]</p>]]>
    </content>
</entry>
<entry>
    <title>VRS Numbering FNPR comments</title>
    <link rel="alternate" type="text/html" href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006/07/vrs_numbering_fnpr_replies.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://pactlab.spcomm.uiuc.edu/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=33/entry_id=1674" title="VRS Numbering FNPR comments" />
    <id>tag:pactlab.spcomm.uiuc.edu,2006:/blog/ryancroke//33.1674</id>
    
    <published>2006-07-18T20:48:44Z</published>
    <updated>2006-07-25T18:23:39Z</updated>
    
    <summary>[BRIEF REVIEW OF VIDEOPHONE NUMBERING AS A REGULATORY ISSUE] In response to the California Coalition of Agencies Serving the Deaf &amp; Hard-of-Hearing&apos;s Feb. 15, 2005 Petition for Declaratory Ruling on Interoperability, the FCC released this Declaratory ruling &amp; Further Notice...</summary>
    <author>
        <name>croke</name>
        
    </author>
            <category term="Numbering" />
    
    <content type="html" xml:lang="en" xml:base="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/">
        <![CDATA[<font color=orange><strong>[BRIEF REVIEW OF VIDEOPHONE NUMBERING AS A REGULATORY ISSUE]</STRONG></font>
<br>
In response to the California Coalition of Agencies Serving the Deaf & Hard-of-Hearing's Feb. 15, 2005 <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2005%20-%20Feb%20-%20CaliPetition.pdf">Petition for Declaratory Ruling on Interoperability</a>, the FCC released this <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/FCC%20Latest%20VRS%20ruling.doc"> Declaratory ruling & Further Notice of Proposed Rulemaking (FNPR)</a> on May 3, 2006. (Click <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/FCC%20%23ing%20FNPR%20Anncmnt.doc">here</a> for the FCC press release.) 
<br>
<br>
The "Declaratory ruling" part forbids video relay service equipment providers from blocking user access to competing service providers (effective July 1, 2006). 
<br>
<br>
In the "FNPR" part, the FCC requests comments about two topics: <li>1. the feasibility of a national videophone number database; and <li>2. whether video protocol standards (e.g. H.323, SIP) should be required for VRS providers.</li> 
<br>
<font color=orange><strong>[VIDEOPHONE NUMBERING UPDATE!]</STRONG></font><br>
On Monday (July 17), seven VRS providers, one advocacy organization (TDI) and one consumer had responded directly to the numbering component of the FNPR. Here they are:
<br>
<br>
<TABLE BORDER="1" CELLSPACING="2" WIDTH="100%" style="border-style: solid;">
<TR><TD><strong>CLICK BELOW FOR THE COMMENTS OF...</strong></TD><TD><strong>...SUBMITTED BY...</strong></TD><TD><b>SWEET MUGS</strong></TR>
<TR><TD><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006-7%20AT%26T%20Reply.pdf">AT&T</a></TD><TD>Davida Grant</TD><TD ALIGN="CENTER"><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/no%20photo%20available.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/no%20photo%20available.html','popup','width=334,height=419,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/no%20photo%20available-thumb.gif" width="39" height="50" alt="" /></a></TD></TR>
<TR><TD><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006-7%20CSD%20Reply.pdf">CSD</a></TD><TD>Karen Peltz-Strauss</TD><TD ALIGN="CENTER"><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/cmip112255274.html" onclick="window.open('http://www.von.com/fall05/bios.html#eokp1120643957'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/cmip112255274-thumb.jpg" width="41" height="50" alt="" /></a></TD></TR>

<TR><TD><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006-7%20HOVRS%20Reply.pdf">Hands-On (HOVRS)</a></TD><TD>George Lyon</TD><TD ALIGN="CENTER"><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/Glyon.html" onclick="window.open('http://www.fcclaw.com/keypros.html#Anchor-George-27280'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/Glyon-thumb.jpg" width="36" height="50" alt="" /></a>
</TD></TR>
<TR><TD><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006-7%20Sorenson%20Reply.pdf">Sorenson</a></TD><TD>Gil Strobel</TD><TD ALIGN="CENTER"><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/photo8.html" onclick="window.open('http://www.lmmk.com/attorney/attorney9.html'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/photo8-thumb.jpg" width="46" height="50" alt="" /></a></TD></TR>
<TR><TD><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006-7%20Sprint%20Nextel%20Reply.pdf">Sprint-Nextel</a></TD><TD>Michael B. Fingerhut</TD><TD ALIGN="CENTER"><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/no%20photo%20available.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/no%20photo%20available.html','popup','width=334,height=419,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/no%20photo%20available-thumb.gif" width="39" height="50" alt="" /></a></TD></TR>
<TR><TD><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006-7%20TDI%20Reply.pdf">TDI</a></TD><TD>Eliot Greenwald</TD><TD ALIGN="CENTER"><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/Greenwald.html" onclick="window.open('http://www.bingham.com/bingham/attorneys_bios.asp?aid=2781'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/Greenwald-thumb.jpg" width="33" height="50" alt="" /></a>
</TD></TR>
<TR><TD><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006-7%20Verizon%20Reply.pdf">Verizon</a></TD><TD>Sherry Ingram</TD><TD ALIGN="CENTER"><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/no%20photo%20available.html" onclick="window.open('http://pactlab.spcomm.uiuc.edu/blog/ryancroke/no%20photo%20available.html','popup','width=334,height=419,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/no%20photo%20available-thumb.gif" width="39" height="50" alt="" /></a></TD></TR>
</TABLE>

<a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006-7%20User%20%28Kent%20Munro%29%20Reply.pdf">User (Kent Munro)</a>]]>
        <![CDATA[Kent Munro's comments:
<br>
<br>
"Dear FCC,
<br>
<br>
As a deaf VRS user, I am responding to your request for comments on CG 03-
123; FCC 06-57, which refers to the idea of creating a system that would
allow VRS users to contact one another in a functionally equivalent manner
to hearing people contacting one another via a telephone number. As we
now know, VRS is a phenomenal telecommunications service that, from a
performance perspective, is truly functionally equivalent. However, I don’t
think anyone disputes that, from a practical standpoint, the current
dialing/contact methodologies fall far short of functional equivalence.
In order to make VRS truly functionally equivalent from a practical
standpoint, it is necessary to set up a system to make VRS user-friendly,
especially for hearing consumers. Unfortunately, the case today is that far
more calls are made by deaf VRS users than are made by hearing VRS users.
The reasons are pretty simple: Hearing people are required to keep track of
multiple VRS provider phone numbers, along with an IP address that will not
always work. My hearing mother gets confused by all this and I frequently
have to call her to help her figure out how to contact me. As a result, she has
not attempted to contact me on a regular basis because it can be frustrating
for her. I’m sure she’s not the only one.
<br>
<br>
The last thing deaf VRS users need or should be required to do is to ask (and
even beg) hearing people to try to make VRS calls when it’s already confusing
in the first place. Because of these experiences, I don’t even bother leaving
VRS phone numbers and IP addresses on hearing peoples’ voice mails
because they will not understand how it works. I just have to hope I can call
back and get them when they are available to answer the phone, or I have to
leave an email address and explain I don’t have a convenient telephone
number available.
<br>
<br>
I applaud the FCC for bringing VRS to the forefront as a functionally
equivalent technology as far as call performance goes. I encourage the FCC
to make VRS fully functionally equivalent in every sense of the term by
making it just as easy for hearing and deaf VRS users to contact other deaf
VRS users as it already is for hearing people to contact other hearing users."
<br>
<br>
------------------------------------
<br>
<br>
The Commission also wrote a <a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/FCC%20Numbering%20FNPR%20supporting%20statement.doc">Supporting Statement</a> about VRS numbering with even more detail about the purported need and feasibility of a national (VRS) videophone user directory in June 2006.
<br>
<br>
Hamilton Comments about relay misuse:
<br>
<br>
<TABLE BORDER="1" CELLSPACING="2" WIDTH="100%" style="border-style: solid;">
<TR><TD><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006-7%20Hamilton%20Reply.pdf">Hamilton</a></TD><TD>David A. O'Connor</TD><TD ALIGN="CENTER"><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/106341.html" onclick="window.open('http://www.hklaw.com/Biographies/Bio.asp?ID=106341'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/106341-thumb.gif" width="35" height="50" alt="" /></a>
</TD></TR><table>
Snap Telecommunication's comments about VRS video protocols (H.323, SIP, H.263, H.264):
<br>
<br>
<TABLE BORDER="1" CELLSPACING="2" WIDTH="100%" style="border-style: solid;"><TR><TD><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/2006-7%20Snap%20Reply.pdf">Snap</a></TD><TD>Francis Buono</TD><TD ALIGN="CENTER"><a href="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/fbuono.html" onclick="window.open('http://www.willkie.com/FrancisBuono'); return false"><img src="http://pactlab.spcomm.uiuc.edu/blog/ryancroke/fbuono-thumb.jpg" width="40" height="50" alt="" /></a>
</TD></TR></table>
]]>
    </content>
</entry>

</feed> 

