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

<channel>
	<title>Ed's Telecom Alert &#187; Technology Innovations</title>
	<atom:link href="http://www.edsalert.com/category/technology-innovations/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.edsalert.com</link>
	<description>POSTS ALERTS REGARDING TRS &#38; ITS RELATED ISSUES</description>
	<lastBuildDate>Wed, 16 Nov 2011 19:25:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>FCC Proposed Rules on Text to 911</title>
		<link>http://www.edsalert.com/2011/09/26/fcc-proposed-rules-on-text-to-911/</link>
		<comments>http://www.edsalert.com/2011/09/26/fcc-proposed-rules-on-text-to-911/#comments</comments>
		<pubDate>Mon, 26 Sep 2011 19:00:43 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[Technology Innovations]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1735</guid>
		<description><![CDATA[Good People, Click to this all important NPRM (Notice of Proposed Rule Making) on text to 911. &#160;&#160; Text to 911 This quote is kinda self-explanatory:&#160; &#34;..we [FCC] seek to accelerate the development and deployment of Next Generation 911 (NG911) technology that will enable the public to send emergency communications to 911 Public Safety Answering [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Good People,</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Click to this all important NPRM (Notice of Proposed Rule Making) on text to 911. &nbsp;&nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db0922/FCC-11-134A1.pdf">Text to 911</a></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">This quote is kinda self-explanatory:&nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;..<span class="Apple-style-span">we </span></em><span class="Apple-style-span">[FCC]</span><em><span class="Apple-style-span"> seek to accelerate the development and deployment of Next Generation 911 (NG911) technology that will enable the public to send emergency communications to 911 Public Safety Answering Points (PSAPs) via text, photos, videos, and data and enhance the information available to PSAPs and first responders for assessing and responding to emergencies.&quot;</span></em></span></span></p>
<p><!--[if gte mso 9]><xml><br />
 <o:OfficeDocumentSettings><br />
  <o:AllowPNG/><br />
 </o:OfficeDocumentSettings><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:WordDocument><br />
  <w:Zoom>0</w:Zoom><br />
  <w:TrackMoves>false</w:TrackMoves><br />
  <w:TrackFormatting/><br />
  <w:PunctuationKerning/><br />
  <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing><br />
  <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing><br />
  <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery><br />
  <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery><br />
  <w:ValidateAgainstSchemas/><br />
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
  <w:Compatibility><br />
   <w:BreakWrappedTables/><br />
   <w:DontGrowAutofit/><br />
   <w:DontAutofitConstrainedTables/><br />
   <w:DontVertAlignInTxbx/><br />
  </w:Compatibility><br />
 </w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:LatentStyles DefLockedState="false" LatentStyleCount="276"><br />
 </w:LatentStyles><br />
</xml><![endif]--><!--[if gte mso 10]></p>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-ascii-font-family:Cambria;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Cambria;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
</style>
<p><![endif]--><!--StartFragment-->
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">That, I tell you, is simply GREAT! &nbsp;Text, photos, videos, and data? &nbsp;Hurzzah! &nbsp;</span></span></p>
<p><!--EndFragment--></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;<span class="Apple-style-span">While continuing to ensure reliable voice-based 911 service will always be essential as we migrate to NG911, adding these non-voice capabilities to our 911 system will significantly improve emergency response, save lives, and reduce property damage.&nbsp;&quot;</span></em></span></span></p>
<p><span class="Apple-style-span" style="font-family: tahoma, geneva, sans-serif; font-size: 14px; ">No kidding! I know many of us can think of instances. &nbsp;One example was my own experience; about 15 years ago when I lived in Austin, I witnessed a man beating up a woman on street. &nbsp;I got home and called police via 911 (supposed to be available then) a few times, and gave up and went to my neighbor to make the 911 call. &nbsp; By the time they got to the location, nothing there. &nbsp; &nbsp;To this day I wondered if the woman survived or not. &nbsp;&nbsp;</span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;..&nbsp;these 21st century communications technologies will provide PSAPs with better information that can be synthesized with existing databases to enable emergency responders to assess and respond to emergencies more quickly and effectively.&nbsp; Not only will PSAPs be able to receive text messages, photos, and video clips from the public, but also NG911 can provide them with the tools they need to quickly process and analyze the incoming information.&quot;&nbsp;</em></span></span></p>
<p><!--[if gte mso 9]><xml><br />
 <o:OfficeDocumentSettings><br />
  <o:AllowPNG/><br />
 </o:OfficeDocumentSettings><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:WordDocument><br />
  <w:Zoom>0</w:Zoom><br />
  <w:TrackMoves>false</w:TrackMoves><br />
  <w:TrackFormatting/><br />
  <w:PunctuationKerning/><br />
  <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing><br />
  <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing><br />
  <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery><br />
  <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery><br />
  <w:ValidateAgainstSchemas/><br />
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
  <w:Compatibility><br />
   <w:BreakWrappedTables/><br />
   <w:DontGrowAutofit/><br />
   <w:DontAutofitConstrainedTables/><br />
   <w:DontVertAlignInTxbx/><br />
  </w:Compatibility><br />
 </w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:LatentStyles DefLockedState="false" LatentStyleCount="276"><br />
 </w:LatentStyles><br />
</xml><![endif]--><!--[if gte mso 10]></p>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-ascii-font-family:Cambria;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Cambria;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
</style>
<p><![endif]--><!--StartFragment--><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><font class="Apple-style-span"><span class="Apple-style-span">Good thinking; clearly this is needed. &nbsp;&nbsp;</span></font><br />
	</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;<span class="Apple-style-span">In this Notice, we provide a procedural history, together with technical background, regarding three broad classes of text-capable communications, namely Short Message Service (SMS), IP-based messaging, and Real-Time Text (RTT), comparing their characteristics, strengths, and limitations in supporting emergency communications.&nbsp;This description relies largely on current industry standards, early prototypes, and the record in this proceeding.&quot;</span></em></span></span></p>
<p><!--[if gte mso 9]><xml><br />
 <o:OfficeDocumentSettings><br />
  <o:AllowPNG/><br />
 </o:OfficeDocumentSettings><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:WordDocument><br />
  <w:Zoom>0</w:Zoom><br />
  <w:TrackMoves>false</w:TrackMoves><br />
  <w:TrackFormatting/><br />
  <w:PunctuationKerning/><br />
  <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing><br />
  <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing><br />
  <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery><br />
  <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery><br />
  <w:ValidateAgainstSchemas/><br />
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
  <w:Compatibility><br />
   <w:BreakWrappedTables/><br />
   <w:DontGrowAutofit/><br />
   <w:DontAutofitConstrainedTables/><br />
   <w:DontVertAlignInTxbx/><br />
  </w:Compatibility><br />
 </w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:LatentStyles DefLockedState="false" LatentStyleCount="276"><br />
 </w:LatentStyles><br />
</xml><![endif]--><!--[if gte mso 10]></p>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-ascii-font-family:Cambria;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Cambria;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
</style>
<p><![endif]--><!--StartFragment-->
<div style="mso-element:footnote-list"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">The purposes of NPRM are the following:</span></span></div>
<div style="mso-element:footnote-list"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><br />
	</span></span></div>
<div style="mso-element:footnote-list"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;..<span class="Apple-style-span">seek comment on what role the Commission should play to facilitate &ndash; and, if necessary, accelerate &ndash; the implementation of text-to-911 capabilities by providers in the short term.&nbsp; We explore the full range of options for the FCC, including both non-regulatory and regulatory approaches, and seek to adopt the least burdensome approach that would achieve the desired result.&quot;</span></em></span></span></div>
<div style="mso-element:footnote-list">&nbsp;</div>
<div style="mso-element:footnote-list"><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;..<span class="Apple-style-span">seek comment on whether 911 traffic should be prioritized to ensure that people in need of assistance have reliable access to emergency services, especially during times of serious emergencies such as large-scale natural and manmade disasters.&quot;&nbsp;</span></em></span></span></div>
<p><!--[if gte mso 9]><xml><br />
 <o:OfficeDocumentSettings><br />
  <o:AllowPNG/><br />
 </o:OfficeDocumentSettings><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:WordDocument><br />
  <w:Zoom>0</w:Zoom><br />
  <w:TrackMoves>false</w:TrackMoves><br />
  <w:TrackFormatting/><br />
  <w:PunctuationKerning/><br />
  <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing><br />
  <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing><br />
  <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery><br />
  <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery><br />
  <w:ValidateAgainstSchemas/><br />
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
  <w:Compatibility><br />
   <w:BreakWrappedTables/><br />
   <w:DontGrowAutofit/><br />
   <w:DontAutofitConstrainedTables/><br />
   <w:DontVertAlignInTxbx/><br />
  </w:Compatibility><br />
 </w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:LatentStyles DefLockedState="false" LatentStyleCount="276"><br />
 </w:LatentStyles><br />
</xml><![endif]--><!--[if gte mso 10]></p>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-ascii-font-family:Cambria;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Cambria;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
</style>
<p><![endif]--><!--StartFragment--><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;..<span class="Apple-style-span">long-term implementation of NG911, with particular focus on IP-based alternatives for delivering text, photos, videos, and other data to 911 that would leverage the increasing percentage of mobile devices that have the ability to access the Internet.&quot;&nbsp;</span></em></span></span></p>
<p><!--[if gte mso 9]><xml><br />
 <o:OfficeDocumentSettings><br />
  <o:AllowPNG/><br />
 </o:OfficeDocumentSettings><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:WordDocument><br />
  <w:Zoom>0</w:Zoom><br />
  <w:TrackMoves>false</w:TrackMoves><br />
  <w:TrackFormatting/><br />
  <w:PunctuationKerning/><br />
  <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing><br />
  <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing><br />
  <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery><br />
  <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery><br />
  <w:ValidateAgainstSchemas/><br />
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
  <w:Compatibility><br />
   <w:BreakWrappedTables/><br />
   <w:DontGrowAutofit/><br />
   <w:DontAutofitConstrainedTables/><br />
   <w:DontVertAlignInTxbx/><br />
  </w:Compatibility><br />
 </w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:LatentStyles DefLockedState="false" LatentStyleCount="276"><br />
 </w:LatentStyles><br />
</xml><![endif]--><!--[if gte mso 10]></p>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-ascii-font-family:Cambria;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Cambria;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
</style>
<p><![endif]--><!--StartFragment--><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">The FCC identified problematic area with this remark:<br />
	</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;<span class="Apple-style-span">With over 6,800 PSAPs in the United States, spanning a wide range of sizes and resources, individual PSAPs are likely to have highly varying timetables for developing the technical and operational capability to handle incoming texts in the short term, as well as texts and other media in the longer-term implementation of NG911.&nbsp; While there are significant public safety benefits to enabling the public to send texts and other media to 911 in areas where PSAPs are capable of receiving and processing them, we seek to avoid imposing unnecessary costs on providers to implement NG911 in areas where PSAPs have not yet achieved such capability.&quot;</span></em></span></span></p>
<p><!--[if gte mso 9]><xml><br />
 <o:OfficeDocumentSettings><br />
  <o:AllowPNG/><br />
 </o:OfficeDocumentSettings><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:WordDocument><br />
  <w:Zoom>0</w:Zoom><br />
  <w:TrackMoves>false</w:TrackMoves><br />
  <w:TrackFormatting/><br />
  <w:PunctuationKerning/><br />
  <w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing><br />
  <w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing><br />
  <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery><br />
  <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery><br />
  <w:ValidateAgainstSchemas/><br />
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid><br />
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent><br />
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText><br />
  <w:Compatibility><br />
   <w:BreakWrappedTables/><br />
   <w:DontGrowAutofit/><br />
   <w:DontAutofitConstrainedTables/><br />
   <w:DontVertAlignInTxbx/><br />
  </w:Compatibility><br />
 </w:WordDocument><br />
</xml><![endif]--><!--[if gte mso 9]><xml><br />
 <w:LatentStyles DefLockedState="false" LatentStyleCount="276"><br />
 </w:LatentStyles><br />
</xml><![endif]--><!--[if gte mso 10]></p>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-ascii-font-family:Cambria;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Cambria;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
</style>
<p><![endif]--><!--StartFragment--><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">6,800 PSAPs; whew!<br />
	</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;<span class="Apple-style-span">Given that text-to-911 and other NG911 capabilities will likely not be simultaneously deployed nationwide, consumers may be uncertain where non-voice communication with 911 is available.&nbsp; Even where text-to-911 or other NG911 applications are available, the specific capabilities and operational characteristics of these applications may vary.&nbsp; We therefore seek comment on how to best educate consumers about the availability and limitations of text-to-911 and other NG911 solutions, particularly during the transition from legacy 911 to full implementation of NG911, without imposing an undue burden on providers.&quot;</span></em></span></span></p>
<p><!--EndFragment--><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Maybe that&#39;s where we Deaf/HH can comment?</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">The rest of document goes into specific outline of various technical, service, operation, etc. &nbsp; The very least reading all of them will certainly give you insight. &nbsp;What I did was simply highlight important ones; there are more important comments so read on, dear readers.</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><span class="Apple-style-span">&nbsp;</span>eyes open &amp; thumbs up</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Ed Bosson</p>
<p>	</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Long Link:&nbsp;http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db0922/FCC-11-134A1.pdf</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/09/26/fcc-proposed-rules-on-text-to-911/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cochlear Implants Recall</title>
		<link>http://www.edsalert.com/2011/09/13/cochlear-implants-recall/</link>
		<comments>http://www.edsalert.com/2011/09/13/cochlear-implants-recall/#comments</comments>
		<pubDate>Tue, 13 Sep 2011 16:05:30 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[Digress to Other Issues]]></category>
		<category><![CDATA[Technology Innovations]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1698</guid>
		<description><![CDATA[Folks, We all know cochlear implant is controversial. &#160;I acknowledge that it worked very well for many people, and I also am aware that it did not work too well for many people as well. &#160; &#160;As the cochlear technology keeps improving, it should present less problem; however, I do not think we&#39;re there yet. [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">Folks,</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">We all know cochlear implant is controversial. &nbsp;I acknowledge that it worked very well for many people, and I also am aware that it did not work too well for many people as well. &nbsp; &nbsp;As the cochlear technology keeps improving, it should present less problem; however, I do not think we&#39;re there yet. &nbsp; &nbsp;It really is dependent on the individual&#39;s past history and nature of his/her losing hearing of whether this works or not. &nbsp;I won&#39;t go into this, though, as this is a recall blog. &nbsp;&nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">This is a recall to a specific cochlear implant model.</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;"><a href="http://www.suntimes.com/business/7627305-420/bionic-ear-maker-cochlear-recalls-hearing-implants.html">Cochlear Recall Article</a></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">Quotable quotes:</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;"><em>&quot;<span class="Apple-style-span" style="color: rgb(61, 60, 60); line-height: 18px; ">Bionic ear maker Cochlear has been forced to begin a global recall of the world&rsquo;s thinnest hearing implants after some stopped working.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">Model type:</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;"><em>&quot;<span class="Apple-style-span" style="color: rgb(61, 60, 60); line-height: 18px; ">The company has begun recalling its entire Nucleus CI500 range, which makes up the bulk of its sales, from shelves after a rise in the number of faults with the CI512 model.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;"><em>&quot;<span class="Apple-style-span" style="color: rgb(61, 60, 60); line-height: 18px; ">While Cochlear believes the faults are unlikely to cause any health problems for people with defective implants, they are offering replacement models for re-implantation.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;"><em>&quot;<span class="Apple-style-span" style="color: rgb(61, 60, 60); line-height: 18px; ">Cochlear chief executive Chris Roberts said he was unable to say how many of the &ldquo;very reliable&rdquo; titanium-based devices were faulty.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">eyes open &amp; thumbs up,</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">Ed</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:arial,helvetica,sans-serif;">Long LInk:&nbsp;http://www.suntimes.com/business/7627305-420/bionic-ear-maker-cochlear-recalls-hearing-implants.html</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/09/13/cochlear-implants-recall/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Landline Converted to VoIP?</title>
		<link>http://www.edsalert.com/2011/08/18/landline-converted-to-voip/</link>
		<comments>http://www.edsalert.com/2011/08/18/landline-converted-to-voip/#comments</comments>
		<pubDate>Thu, 18 Aug 2011 20:44:16 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[Digress to Other Issues]]></category>
		<category><![CDATA[Technology Innovations]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1685</guid>
		<description><![CDATA[Folks, Check this out. SprintLandLine &#34;The service, which will offer unlimited domestic calling for $19.99 per month, lets home or small business customers use a landline phone to connect to Sprint&#8217;s wireless network.&#34; Landline to connect to wireless network? &#160;Cool! &#160;But note this: &#34;Verizon Wireless launched a service highly similar to Sprint Phone Connect back [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Folks,</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Check this out.</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><a href="http://www.telecompetitor.com/sprint-targets-landline-voice-customers-with-new-wireless-offering/">SprintLandLine</a></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;<span class="Apple-style-span" style="color: rgb(51, 51, 51); line-height: 17px; ">The service, which will offer unlimited domestic calling for $19.99 per month, lets home or small business customers use a landline phone to connect to Sprint&rsquo;s wireless network.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Landline to connect to wireless network? &nbsp;Cool! &nbsp;But note this:</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;"><em>&quot;<span class="Apple-style-span" style="color: rgb(51, 51, 51); line-height: 17px; ">Verizon Wireless launched a service highly similar to Sprint Phone Connect back in February. Verizon calls its offering Home Phone Connect and it, too, offers unlimited calling for $20 a month by using a device similar to the one from Axesstel that is free with a two-year contract.&quot;</span></em></span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">I still have landline as I do occasionally use landline for TTY Relay Service and to communicate with relatives as our Internet does have high speed broadband Internet. &nbsp; This is something I may check into if it is really cheaper and reliable. &nbsp;Any of you used that? &nbsp;If so, your feedback, please? &nbsp; &nbsp;</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">eyes open &amp; thumbs up,</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Ed Bosson</span></span></p>
<p><span style="font-size:14px;"><span style="font-family:tahoma,geneva,sans-serif;">Long Link:&nbsp;http://www.telecompetitor.com/sprint-targets-landline-voice-customers-with-new-wireless-offering/</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/08/18/landline-converted-to-voip/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RERC-IT &amp; RERC-TA Comments</title>
		<link>http://www.edsalert.com/2011/04/28/rerc-it-rerc-ta-comments/</link>
		<comments>http://www.edsalert.com/2011/04/28/rerc-it-rerc-ta-comments/#comments</comments>
		<pubDate>Thu, 28 Apr 2011 17:31:31 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[Technology Innovations]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1613</guid>
		<description><![CDATA[Folks.. Don&#8217;t y&#8217;all hate these acronyms?&#160;&#160;&#160;&#160; RERC stands for Rehabilition Engineering Research Center, and IT = Information Technology Access, and TA = Telecommunications Access What caught my eyes is that TA is from Gallaudet University.&#160; RERC Link: https://prodnet.www.neca.org/publicationsdocs/wwpdf/42511rerc2.pdf (Note: I am having problem with Word Press in adding the link to one word, so my [...]]]></description>
			<content:encoded><![CDATA[<p>Folks..</p>
<p>Don&#8217;t y&#8217;all hate these acronyms?&nbsp;&nbsp;&nbsp;&nbsp; RERC stands for Rehabilition Engineering Research Center, and IT = Information Technology Access, and TA = Telecommunications Access</p>
<p>What caught my eyes is that TA is from Gallaudet University.&nbsp; </p>
<p>RERC Link: https://prodnet.www.neca.org/publicationsdocs/wwpdf/42511rerc2.pdf</p>
<p>(Note: I am having problem with Word Press in adding the link to one word, so my apologies until that is fixed, you all will have to put up with long link.)</p>
<p>Quotable quotes:</p>
<p><em>&quot;Gallaudet and the Trace Center have collaborated on research and development related to cross-disability access to telecommunication since 1995.&quot;</em></p>
<p>hmm &#8211; good to know.&nbsp; </p>
<p><em>&quot;We agree that the meaning of the term &#8220;manufacturer&#8221; should be the same as in the rules implementing section 255 as &#8220;an entity that makes or produces a product.&#8221; However, it should be made clear that many &ldquo;products&rdquo; will be software only. Such Advanced Communication software products must be clearly covered.&quot;</em></p>
<p>Uh, yeah good idea to include that.&nbsp;&nbsp; More and more future &quot;advanced communication software&quot; likely will become the standard especially with advent of tablets, and mobile devices that relay on these software.&nbsp; </p>
<p><em>&quot;..if a manufacturer requires, prefers, or incentivizes (e.g., by providing increased speed) a purchaser to use a particular third-party application in order to use all the features or get all of the benefits of the device/service, then the manufacturer, rather than the user is making the choice and the manufacturer should be responsible. Finally, if the manufacturer markets its device or service in conjunction with the third-party add- on or identifies the third-party application as a reason to purchase its product, the manufacturer should be responsible.&quot;</em></p>
<p>Lot of statements similar to above quote on the responsibility of manufacturers that that they should be held responsible for full accessibility.&nbsp;&nbsp; </p>
<p>The comments also indicate that ALL products/softwares should be tied to telephone number so everyone else can call each other and suggests to the FCC on wording for that.&nbsp; </p>
<p>Comments offer rewording on various issues: one example:</p>
<p><em>&quot;Instead of excluding &ldquo;blog posts, online publishing, or messages posted on social networking websites&rdquo; the commission should use language like &ldquo;information that is posted to a location where it is expected to be found and read by many people over an extended period of time, rather than information directed to specific individuals or expected to be read and responded to or acted upon immediately after posting&rdquo;</em></p>
<p>Now to &quot;video conference service&quot; comments by RERC.</p>
<p><em>&quot;Video conferencing service should be interpreted to include the broadest range possible because none of the listed services is likely to exist in its current form in 20 years, but the legislation will still need to be meaningful. The definition should be wide in order to prevent new technologies from defining themselves out of the requirements.&quot;</em></p>
<p><strong>AMEN!</strong>&nbsp; One only have to look back at Baudot Syndrome (locked to TTY machines and not able to grow out of it to a newer technologies).</p>
<p><em>&quot;We agree with the consumer groups that VRS services are covered &#8211; the video leg of the VRS meets the definition. Further, individuals who are deaf have unfortunately not been given a get-out-of-jail-free card for other types of disabilities, nor from the effects of aging. To say that a system for the deaf should be exempt from other types of accessibility would be to deny the human condition or to claim that deaf people are exempt from it.&quot;</em></p>
<p><strong>YES!</strong>&nbsp; In other words, VRS to be integrated into mainstream video conference for everyone including hearing persons.&nbsp;&nbsp; </p>
<p>The next comment touches on &quot;Interoperability&quot;.&nbsp; RERC had right idea.&nbsp; Read the following comments and breathe a sigh of relief and hope that the FCC agrees.<br /><em><br />&quot;The fact that video relay service wasn&rsquo;t always interoperable from the beginning was an unfortunate anomaly. All progress in this area is toward interoperable VRS, including both interoperability among VRS services and interoperability with the public communication system. Purely for economic reasons, it is important that deaf people be able to make point-to-point calls with each other and with other members of the public, (rather than having to always rely on publicly funded relay services because of incompatible videophones).&quot;</em></p>
<p><em>&quot;It makes no sense to build next-generation emergency systems that need to support a variety of different incompatible video communication systems in order to be able to accept emergency calls from different deaf callers. Nor should we have an emergency system that is different from the system used for mainstream video communication calls. Videophone interoperability is particularly essential in a disaster, because the emergency systems will be overwhelmed and people who are deaf will need to turn to anyone who can help them. So their video systems need to work with mainstream video systems as well as that of other deaf people &ndash; point to point. Video communication services, therefore, should be required to be interoperable with each other and with other ACS (mainstream and special).&quot;</em></p>
<p>Duh, that&#8217;s really no brainer.&nbsp;&nbsp; </p>
<p>Other comments focused on &quot;waiver&quot; and how the FCC should and should not allow waiver for manufacturers/providers to &quot;get away from it&quot;.&nbsp;&nbsp;&nbsp; </p>
<p>One example of above is the following comment:</p>
<p><em>&quot;We agree with the Commission that there should not be a blanket exemption for small business. There are many ways that accessibility can be incorporated even in the work of a small business.&quot;</em></p>
<p>Love that!&nbsp;&nbsp;&nbsp; Often small business will try to &quot;get away with it&quot; by saying they&#8217;re a small company and cannot meet the disability access criteria.&nbsp; Duh, with this rule if passed, they can&#8217;t use that.&nbsp;&nbsp; </p>
<p>I just realized that I&#8217;m half way.&nbsp;&nbsp;&nbsp; If you&#8217;re intrigued, read the link.&nbsp; Sometimes not easy to read and understand, but good suggestions from RERC.&nbsp; </p>
<p>eyes open &amp; thumbs up,</p>
<p>Ed</p>
<p>Long Link: https://prodnet.www.neca.org/publicationsdocs/wwpdf/42511rerc2.pdf</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/04/28/rerc-it-rerc-ta-comments/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Apple IPAD 2: AT&amp;T and Verizon Rates</title>
		<link>http://www.edsalert.com/2011/03/11/apple-ipad-2-att-and-verizon-rates/</link>
		<comments>http://www.edsalert.com/2011/03/11/apple-ipad-2-att-and-verizon-rates/#comments</comments>
		<pubDate>Fri, 11 Mar 2011 19:45:13 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[Digress to Other Issues]]></category>
		<category><![CDATA[Technology Innovations]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1564</guid>
		<description><![CDATA[Folks, Did a little research myself on IPAD 2 as I wanted to purchase 2 iPAD 2 for myself and wife. I was thinking of getting the WiFi + 3G plan. The fact there is no &#34;unlimited plan&#34; and AT&#38;T and Verizon only offer usage rates gave me a pause so am holding back until [...]]]></description>
			<content:encoded><![CDATA[<p>Folks,</p>
<p>Did a little research myself on IPAD 2 as I wanted to purchase 2 iPAD 2 for myself and wife. I was thinking of getting the WiFi + 3G plan. The fact there is no &quot;unlimited plan&quot; and AT&amp;T and Verizon only offer usage rates gave me a pause so am holding back until I hear more on this and would love to hear your thoughts/analysis.&nbsp;&nbsp; Here is the information I have found out.&nbsp;&nbsp; </p>
<p>Keep in mind that if you get WiFi product, then you do not need to worry about this.&nbsp; If you plan to get WiFi + 3G product, then it could become worrisome.&nbsp;&nbsp; Here&#8217;s why.&nbsp; Before I go on, keep in mind, signing with either AT&amp;T or Verizon does NOT lock you to a two-year term.&nbsp;&nbsp; So you can switch to other if u think other is cheaper in the long run.&nbsp; </p>
<p>First check out Money&#8217;s analysis the link below.</p>
<p><a href="http://money.cnn.com/2011/03/11/technology/ipad_plan_cost/index.htm">MoneyAnalysis</a></p>
<p>Quotable quotes:<br /><em><br />&quot;..there are a total of eight different AT&amp;T and Verizon plans that you can choose from, each with a different set of data caps and overage charges.&quot;</em></p>
<p>Yikes..</p>
<p><em>&quot;A data plan with a 250 megabyte cap gets you about 1,300 Web pages, 400 photo downloads, 60 songs, 14 YouTube videos, or about an hour of Netflix videos. A 1 gigabyte plan gets you 6,500 Web pages, 2,000 photos, 300 songs, 65 YouTube videos or between three and six hours of Netflix viewing.&quot;<br /></em><br />3 to 5 hours of Netflix movie uses up 1 GB, so don&#8217;t watch too many movies using the 3G network &#8211; better with WiFi if you can find it.&nbsp; </p>
<p>Now more to our needs.&nbsp;&nbsp; Why not simply just stay with WiFi only?&nbsp; Can do that, but the problem is if later you see 3G turning into 4G or 6G, and would be lot faster than WiFi.&nbsp; WiFi product can&#8217;t change over to WiFi + 3G; that&#8217;s why they are selling separately.&nbsp;&nbsp; Darn.&nbsp;&nbsp; I would love just to test WiFi, and if that does not meet my need, then upgrade to WiFi + 3G.&nbsp; Nope, can&#8217;t do that &#8211; at least that&#8217;s my understanding.&nbsp; If me wrong, feel free to correct me.&nbsp;&nbsp; Also, some large cities have abundance of WiFi, then the choice would be easy.&nbsp; Other cities not so plentiful so choice should be WiFi + 3G product?&nbsp;&nbsp;&nbsp; If you stay home all the time, then WiFi alone should suffice if u already have wireless network at home/work.&nbsp; </p>
<p>Sorry to digress..but here are some interesting and a bit bothersome analysis.</p>
<p>Let&#8217;s say you want 2 GB plan for $25 a month with AT&amp;T.&nbsp; <br /><em><br />&quot;A video conversation consuming 320kbps in each direction &ndash; 640kbps total &ndash; will run into the 5gb cap in 18 hours 38 minutes. That&#8217;s an average of 36 minutes per day over a 31 day month.&quot;</em>&nbsp; This one is from a Convo staff&#8217;s analysis.&nbsp;&nbsp; </p>
<p>To hit the 2 GB cap, it would only take 7 hours 27 minutes. That&#8217;s a little less than 15 minutes a day. Hmm&nbsp; we have 30 days a month.&nbsp; AT&amp;T and Verizon must think a day equals a month.&nbsp; </p>
<p>Now keep in mind that is for 3G product.&nbsp;  Also, note 320 kbps is the low end of speed; many video phones are  higher like 512 kbps which means will gobble up even more memory.&nbsp; </p>
<p>Remember if you have access to WiFi, usage won&#8217;t count against you.&nbsp;&nbsp; </p>
<p>Anyway, so if you use 3G product for browsing, viewing You Tube (just watch 10 minutes of HD video clip will use up 2 GB right there), email, texting, and watching movie, you will pay a penny more than you want to.&nbsp;&nbsp; </p>
<p>Minimal use of 3G, AT&amp;T plan is better, use lot of 3G, Verizon is better with $80 a month per 10 GB.&nbsp; Yike, that may still not be enough for us deafies who will use lot of video chats.&nbsp;&nbsp; </p>
<p>So what do you think, folks?&nbsp;&nbsp;&nbsp; Be prolific in your thoughts.&nbsp;&nbsp;&nbsp; </p>
<p>eyes open &amp; thumbs up,</p>
<p>Ed</p>
<p>Long Link:&nbsp; </p>
<p>MoneyAnalysis: <br />http://money.cnn.com/2011/03/11/technology/ipad_plan_cost/index.htm</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2011/03/11/apple-ipad-2-att-and-verizon-rates/feed/</wfw:commentRss>
		<slash:comments>29</slash:comments>
		</item>
		<item>
		<title>9-1-1 Accessible by text and video?</title>
		<link>http://www.edsalert.com/2010/11/23/1446/</link>
		<comments>http://www.edsalert.com/2010/11/23/1446/#comments</comments>
		<pubDate>Tue, 23 Nov 2010 16:40:52 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[Digress to Other Issues]]></category>
		<category><![CDATA[Technology Innovations]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1446</guid>
		<description><![CDATA[Folks.. In the near future Emergency 9-1-1 to allow texting and video streaming?&#160; It would be way cool to be able to do that.&#160;&#160; More Accessible 911? Quotable quotes:&#34;In a bid to bring the life-saving emergency service 911 into the 21st century, the FCC is looking at letting citizens report crimes through text messages and [...]]]></description>
			<content:encoded><![CDATA[<p>Folks..</p>
<p>In the near future Emergency 9-1-1 to allow texting and video streaming?&nbsp; It would be way cool to be able to do that.&nbsp;&nbsp; </p>
<p><a href="http://www.wired.com/epicenter/2010/11/fcc-911-texting/">More Accessible 911?</a></p>
<p>Quotable quotes:<br /><em><br />&quot;In a bid to bring the life-saving emergency service 911 into the 21st century, the FCC is looking at letting citizens report crimes through text messages and even stream video from their mobile phones to emergency centers.&quot;</em></p>
<p><em>&quot;..911 handles more than 230 million calls a year &mdash; 70 percent of which now come from mobile phones.&quot;</em><br /><em><br />&quot;It&rsquo;s not clear yet where the money will come from for the upgrades, whether they will be federal requirements states and cities must carry out or if they will simply be suggestions.&quot;</em></p>
<p>I am aware that NENA is already discussing how to utilize VRS into the infrastructure of emergency dispatch&#8217;s ability to receive emergency calls.&nbsp; Whether it be from VRS providers, or create a national emergency call center just for the emergency VRS calls?&nbsp; What do you think, my dear friends?&nbsp;&nbsp; </p>
<p>eyes open &amp; thumbs up,</p>
<p>Ed</p>
<p>Long Link:<br />http://www.wired.com/epicenter/2010/11/fcc-911-texting/</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2010/11/23/1446/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Insatiable Hunger for Broadband Speeds</title>
		<link>http://www.edsalert.com/2010/10/11/insatiable-hunger-for-broadband-speeds/</link>
		<comments>http://www.edsalert.com/2010/10/11/insatiable-hunger-for-broadband-speeds/#comments</comments>
		<pubDate>Mon, 11 Oct 2010 19:38:48 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[Digress to Other Issues]]></category>
		<category><![CDATA[Technology Innovations]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1424</guid>
		<description><![CDATA[Folks&#8230; This is non-TRS issue, but this article is interesting and it is about the technology innovations that continually tries to sate the appetite for faster and faster-still broadband speeds. Insatiable Hunger Quotable quotes:&#34;OUR taste for the Internet is insatiable &#8212; traffic is growing so fast that its transmission systems may soon be filled to [...]]]></description>
			<content:encoded><![CDATA[<p>Folks&#8230;</p>
<p>This is non-TRS issue, but this article is interesting and it is about the technology innovations that continually tries to sate the appetite for faster and faster-still broadband speeds.</p>
<p><a href="http://www.nytimes.com/2010/10/10/business/10novel.html">Insatiable Hunger</a></p>
<p>Quotable quotes:<br /><em><br />&quot;OUR taste for the Internet is insatiable &mdash; traffic is growing so fast that its transmission systems may soon be filled to capacity. But scientists are coping, finding ingenious ways to satisfy our deep bandwidth hunger.&quot;</em></p>
<p><em>&quot;A fiber is no thicker than human hair, but can carry many wavelengths of laser light, with each wavelength adding to the bits transmitted per second. The bit rates now attainable are in the billions (gigabits) per second or even trillions (terabits) per second.&quot;</em><br /><em><br />&quot;..in the new system from Alcatel-Lucent, two binary digits or bits can be encoded by using four phases of light. And the polarized light can vibrate up and down or sideways. In this way, four bits of data can be transmitted per time slot instead of one..&quot;</em></p>
<p>I really do not fully understand the last two statements, but they look impressive and innovative.&nbsp;&nbsp; To think that bit rates can do as much terabits per second is really mind-boggling.&nbsp;&nbsp; </p>
<p>eyes open &amp; thumbs up,<br />&nbsp; <br />Ed</p>
<p>Insatiable Hunger Long Link: http://www.nytimes.com/2010/10/10/business/10novel.html</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2010/10/11/insatiable-hunger-for-broadband-speeds/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>FCC Workshop On Expanding Disability Access</title>
		<link>http://www.edsalert.com/2010/04/27/fcc-workshop-on-expanding-disability-access/</link>
		<comments>http://www.edsalert.com/2010/04/27/fcc-workshop-on-expanding-disability-access/#comments</comments>
		<pubDate>Tue, 27 Apr 2010 19:00:57 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[FCC Issues]]></category>
		<category><![CDATA[Technology Innovations]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/2010/04/27/fcc-workshop-on-expanding-disability-access/</guid>
		<description><![CDATA[Folks.. The title of workshop is &#34;EXPANDING DISABILITY ACCESS WITH WIRELESS TECHNOLOGIES&#34;. http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-297706A1.pdf Quotes: *&#160; Mobile communications access issues facing people with disabilities and the disparities in technology access.*&#160; Ways in which new technologies can offer opportunities to meet the communications access needs of people with disabilities.*&#160; Technology demonstrations of advanced mobile communications. Workshop to [...]]]></description>
			<content:encoded><![CDATA[<p><font size="2" face="Tahoma">Folks..</p>
<p>The title of workshop is &quot;EXPANDING DISABILITY ACCESS WITH WIRELESS TECHNOLOGIES&quot;. </p>
<p>http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-297706A1.pdf</p>
<p>Quotes: </p>
<p>*&nbsp; <em>Mobile communications access issues facing people with disabilities and the disparities in technology access.<br />*&nbsp; Ways in which new technologies can offer opportunities to meet the communications access needs of people with disabilities.<br />*&nbsp; Technology demonstrations of advanced mobile communications.</p>
<p></em>Workshop to be held on May 13, 2010, from 10:30 am to 4:00 pm.&nbsp; </p>
<p>Encourage your Mover and Shakers of the Deaf/HOH World to attend this.&nbsp;&nbsp; </p>
<p>Should be interesting&#8230;</p>
<p>eyes open &amp; thumbs up,</p>
<p>Ed<em></em></font></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2010/04/27/fcc-workshop-on-expanding-disability-access/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Captioning on BlackBerry?</title>
		<link>http://www.edsalert.com/2010/03/29/captioning-on-blackberry/</link>
		<comments>http://www.edsalert.com/2010/03/29/captioning-on-blackberry/#comments</comments>
		<pubDate>Mon, 29 Mar 2010 13:15:22 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[Technology Innovations]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=1197</guid>
		<description><![CDATA[Folks.. And it is free.&#160; So media folks have no excuse to say technology problems.&#160;&#160; &#34;..today announced a new version of its popular do-it-yourself caption-authoring tool for digital media..&#34; &#34;..which can be used to create closed-captioned videos formatted for playback on BlackBerry&#174; smartphones. As before, authors can continue to write captions once and export them [...]]]></description>
			<content:encoded><![CDATA[<p>Folks..</p>
<p>And it is free.&nbsp; So media folks have no excuse to say technology problems.&nbsp;&nbsp; </p>
<p><em>&quot;..today announced a new version of its popular do-it-yourself caption-authoring tool for digital media..&quot;</p>
<p>&quot;..which can be used to create closed-captioned videos formatted for playback on BlackBerry&reg; smartphones. As before, authors can continue to write captions once and export them to formats compatible with QuickTime, Windows Media, RealPlayer and Flash.&quot;</em></p>
<p><a href="http://ncam.wgbh.org/about/news/ncam-and-research-in-motion-en">WGBH</a></p>
<p>eyes open &amp; thumbs up,</p>
<p>Ed</p>
<p>Long Link: http://ncam.wgbh.org/about/news/ncam-and-research-in-motion-en</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2010/03/29/captioning-on-blackberry/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>In-Flight WiFi Becoming More Widespread</title>
		<link>http://www.edsalert.com/2009/03/16/in-flight-wifi-becoming-more-widespread/</link>
		<comments>http://www.edsalert.com/2009/03/16/in-flight-wifi-becoming-more-widespread/#comments</comments>
		<pubDate>Mon, 16 Mar 2009 14:59:54 +0000</pubDate>
		<dc:creator>edsalert</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[Digress to Other Issues]]></category>
		<category><![CDATA[Technology Innovations]]></category>

		<guid isPermaLink="false">http://www.edsalert.com/?p=851</guid>
		<description><![CDATA[Folks, Having Internet connections while flying on a plane is way cool!&#160;&#160;&#160; Makes me wonder if video chats would be possible?&#160;&#160; Hope so, but this article did not say anything about video conference, though.&#160; Talks about having access to Internet while flying.&#160; Article WIFI on Plane Not free, though.&#160; eyes open &#38; thumbs up, Ed]]></description>
			<content:encoded><![CDATA[<p><font face="Tahoma" size="3">Folks,</font></p>
<p><font face="Tahoma" size="3">Having Internet connections while flying on a plane is way cool!&nbsp;&nbsp;&nbsp; Makes me wonder if video chats would be possible?&nbsp;&nbsp; Hope so, but this article did not say anything about video conference, though.&nbsp; Talks about having access to Internet while flying.&nbsp; </font></p>
<p><a href="http://www.statesman.com/business/content/business/stories/other/03/16/0316airwifi.html"><font face="Tahoma" size="3">Article WIFI on Plane</font></a></p>
<p><font face="Tahoma" size="3">Not free, though.&nbsp; </font></p>
<p><font face="Tahoma" size="3">eyes open &amp; thumbs up,</font></p>
<p><font face="Tahoma" size="3">Ed</font></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edsalert.com/2009/03/16/in-flight-wifi-becoming-more-widespread/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>

