<?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: Lessons from a VoIP Entrepreneur</title>
	<atom:link href="http://mrblog.org/2008/04/24/lessons-from-a-voip-entrepreneur/feed/" rel="self" type="application/rss+xml" />
	<link>http://mrblog.org/2008/04/24/lessons-from-a-voip-entrepreneur/</link>
	<description>Mr Blog.  Very technical, or silly, sometimes absurd.</description>
	<lastBuildDate>Wed, 16 May 2012 18:11:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: MrBlog</title>
		<link>http://mrblog.org/2008/04/24/lessons-from-a-voip-entrepreneur/comment-page-1/#comment-1012</link>
		<dc:creator>MrBlog</dc:creator>
		<pubDate>Sun, 27 Apr 2008 00:40:08 +0000</pubDate>
		<guid isPermaLink="false">http://mrblog.org/?p=399#comment-1012</guid>
		<description>Tom, that&#039;s an interesting perspective. Perhaps we in the VoIP industry are missing this &quot;elephant in the room&quot;. I know a lot of people that have fallen in love with a given VoIP product look the other way too frequently in terms of problems; see this post for a few examples: http://mrblog.org/2007/11/12/voip-tail-wags-dog/

On the other hand, I&#039;ve seen people be overly criticl of VoIP, tending to blame any and all problems on VoIP. We did tests that showed that people were overly-sensitive about quality and reliability when they were told they were using VoIP, when they were in fact using POTS. Likewise, when they were using VoIP, but told they were using POTS, they were less likely to be critical of call quality. There was a marked placebo effect.</description>
		<content:encoded><![CDATA[<p>Tom, that&#8217;s an interesting perspective. Perhaps we in the VoIP industry are missing this &#8220;elephant in the room&#8221;. I know a lot of people that have fallen in love with a given VoIP product look the other way too frequently in terms of problems; see this post for a few examples: <a href="http://mrblog.org/2007/11/12/voip-tail-wags-dog/" rel="nofollow">http://mrblog.org/2007/11/12/voip-tail-wags-dog/</a></p>
<p>On the other hand, I&#8217;ve seen people be overly criticl of VoIP, tending to blame any and all problems on VoIP. We did tests that showed that people were overly-sensitive about quality and reliability when they were told they were using VoIP, when they were in fact using POTS. Likewise, when they were using VoIP, but told they were using POTS, they were less likely to be critical of call quality. There was a marked placebo effect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://mrblog.org/2008/04/24/lessons-from-a-voip-entrepreneur/comment-page-1/#comment-1005</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Sat, 26 Apr 2008 00:37:23 +0000</pubDate>
		<guid isPermaLink="false">http://mrblog.org/?p=399#comment-1005</guid>
		<description>my argument that the value(or cheap) model is mandatory for consumer(not neccasarilly bussiness) VOIP products is that i have yet to find a VOIP enabled home phone that begins to approach the call clarity and reliablity of POTS lines. i am not saying that makes it unacceptable; but i do say that becasue of this a very significant discount over POTS is neccassry no matter how many extra features are included.</description>
		<content:encoded><![CDATA[<p>my argument that the value(or cheap) model is mandatory for consumer(not neccasarilly bussiness) VOIP products is that i have yet to find a VOIP enabled home phone that begins to approach the call clarity and reliablity of POTS lines. i am not saying that makes it unacceptable; but i do say that becasue of this a very significant discount over POTS is neccassry no matter how many extra features are included.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

