<?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: Potatoes and Tomatoes: The Varieties of Mobile VoIP</title>
	<atom:link href="http://blog.voipsupply.com/potatoes-and-tomatoes-the-varieties-of-mobile-voip/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.voipsupply.com/potatoes-and-tomatoes-the-varieties-of-mobile-voip</link>
	<description>Everything you need to know about VoIP</description>
	<lastBuildDate>Sun, 14 Mar 2010 15:54:39 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tsahi Levent-Levi</title>
		<link>http://blog.voipsupply.com/potatoes-and-tomatoes-the-varieties-of-mobile-voip/comment-page-1#comment-16562</link>
		<dc:creator>Tsahi Levent-Levi</dc:creator>
		<pubDate>Sun, 14 Sep 2008 06:31:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.voipsupply.com/?p=2502#comment-16562</guid>
		<description>Though I totally agree that these examples are not mobile VoIP, I don&#039;t think that WiFi only solutions are mobile VoIP either.
As more phones have UMTS/EVDO data connection than WiFi, and there&#039;s more coverage for the cellular data networks (at least in Europe), then using the cellular data network for mobile VoIP seems more appropriate for this terminology.</description>
		<content:encoded><![CDATA[<p>Though I totally agree that these examples are not mobile VoIP, I don&#8217;t think that WiFi only solutions are mobile VoIP either.<br />
As more phones have UMTS/EVDO data connection than WiFi, and there&#8217;s more coverage for the cellular data networks (at least in Europe), then using the cellular data network for mobile VoIP seems more appropriate for this terminology.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
