<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Working around Google Voice number portability concerns</title>
	<atom:link href="http://www.waded.org/2009/08/working-around-google-voice-number-portability-concerns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.waded.org/2009/08/working-around-google-voice-number-portability-concerns/</link>
	<description>A tech &#38; arts blog from the Idaho high desert • By Wade Dorrell</description>
	<lastBuildDate>Tue, 23 Feb 2010 21:46:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jesse</title>
		<link>http://www.waded.org/2009/08/working-around-google-voice-number-portability-concerns/comment-page-1/#comment-3211</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Sat, 05 Dec 2009 18:56:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.waded.org/2009/08/working-around-google-voice-number-portability-concerns/#comment-3211</guid>
		<description>*28 on Sprint.</description>
		<content:encoded><![CDATA[<p>*28 on Sprint.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wade Dorrell</title>
		<link>http://www.waded.org/2009/08/working-around-google-voice-number-portability-concerns/comment-page-1/#comment-3206</link>
		<dc:creator>Wade Dorrell</dc:creator>
		<pubDate>Wed, 02 Dec 2009 06:13:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.waded.org/2009/08/working-around-google-voice-number-portability-concerns/#comment-3206</guid>
		<description>Hank, odd. Since I made this post, Google added user interface to explain this process directly within Google Voice, and *71 is what the interface says to use for Verizon Wireless. See 
http://www.waded.org/2009/10/google-voice-with-your-existing-number-the-missing-guide/</description>
		<content:encoded><![CDATA[<p>Hank, odd. Since I made this post, Google added user interface to explain this process directly within Google Voice, and *71 is what the interface says to use for Verizon Wireless. See<br />
<a href="http://www.waded.org/2009/10/google-voice-with-your-existing-number-the-missing-guide/" rel="nofollow">http://www.waded.org/2009/10/google-voice-with-your-existing-number-the-missing-guide/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hank</title>
		<link>http://www.waded.org/2009/08/working-around-google-voice-number-portability-concerns/comment-page-1/#comment-3204</link>
		<dc:creator>Hank</dc:creator>
		<pubDate>Mon, 30 Nov 2009 01:41:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.waded.org/2009/08/working-around-google-voice-number-portability-concerns/#comment-3204</guid>
		<description>*71 does not work with Verizon</description>
		<content:encoded><![CDATA[<p>*71 does not work with Verizon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Youmail Help? - BlackBerry Forums at CrackBerry.com</title>
		<link>http://www.waded.org/2009/08/working-around-google-voice-number-portability-concerns/comment-page-1/#comment-3009</link>
		<dc:creator>Youmail Help? - BlackBerry Forums at CrackBerry.com</dc:creator>
		<pubDate>Mon, 03 Aug 2009 21:14:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.waded.org/2009/08/working-around-google-voice-number-portability-concerns/#comment-3009</guid>
		<description>[...] function on GV, then forward your calls to your GV number just as you did with YouMail.   Replacing YouMail with Google Voice.  GV has a BlackBerry App that is similar to the YM app, but it also shows the transcription. (It&#039;s [...]</description>
		<content:encoded><![CDATA[<p>[...] function on GV, then forward your calls to your GV number just as you did with YouMail.   Replacing YouMail with Google Voice.  GV has a BlackBerry App that is similar to the YM app, but it also shows the transcription. (It&#39;s [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
