<?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: The Cord Continues to Fray</title>
	<atom:link href="http://mobhappy.com/blog1/2007/07/31/the-cord-continues-to-fray/feed/" rel="self" type="application/rss+xml" />
	<link>http://mobhappy.com/blog1/2007/07/31/the-cord-continues-to-fray/</link>
	<description>Russell Buckley and Carlo Longino on mobile technology.</description>
	<lastBuildDate>Tue, 31 Jan 2012 19:56:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Dean Bubley</title>
		<link>http://mobhappy.com/blog1/2007/07/31/the-cord-continues-to-fray/comment-page-1/#comment-112953</link>
		<dc:creator>Dean Bubley</dc:creator>
		<pubDate>Mon, 06 Aug 2007 18:04:59 +0000</pubDate>
		<guid isPermaLink="false">http://mobhappy.com/blog1/2007/07/31/the-cord-continues-to-fray/#comment-112953</guid>
		<description>Hi Russell

I think there&#039;s a common misperception that fixed=PSTN. There&#039;s a huge blurring going on because of VoIP, with a fair amount of traffic flipping from circuit-based PSTN to fixed/Internet/WiFi VoIP, especially lucrative traffic like international calls. I&#039;m thinking about the growth of SkypeOut, or PSTN-replacement VoIP services here.

There&#039;s also a hard core of calls which will never go mobile - especially in the enterprise. I&#039;ve continually challenged mobile operators to show me a customer-service call centre where all the agents use cellphones, for example. Similarly, plenty of calls are to places, not people, for which a shared fixed phone is optimal. Unless you know the name of the guy that cooks the pizza, or the woman who does reservations at the hotel, that is....

I totally disagree with the &quot;one number for life&quot; notion. Already something like 20-30% of people in Europe have 2+ mobile numbers, plus probably a fixed-line number and 3-5 email addresses &amp; Internet IDs. 

The whole ridiculous &quot;one number, one device, one service provider, one voicemail, one identity&quot;  concept is fading away as it becomes painfully obvious that exactly the opposite thing will occur. Individuals will have an expanding multiplicity of numbers &amp; contact mechanisms. Some will be linked, others kept safely separate.

Dean</description>
		<content:encoded><![CDATA[<p>Hi Russell</p>
<p>I think there&#8217;s a common misperception that fixed=PSTN. There&#8217;s a huge blurring going on because of VoIP, with a fair amount of traffic flipping from circuit-based PSTN to fixed/Internet/WiFi VoIP, especially lucrative traffic like international calls. I&#8217;m thinking about the growth of SkypeOut, or PSTN-replacement VoIP services here.</p>
<p>There&#8217;s also a hard core of calls which will never go mobile &#8211; especially in the enterprise. I&#8217;ve continually challenged mobile operators to show me a customer-service call centre where all the agents use cellphones, for example. Similarly, plenty of calls are to places, not people, for which a shared fixed phone is optimal. Unless you know the name of the guy that cooks the pizza, or the woman who does reservations at the hotel, that is&#8230;.</p>
<p>I totally disagree with the &#8220;one number for life&#8221; notion. Already something like 20-30% of people in Europe have 2+ mobile numbers, plus probably a fixed-line number and 3-5 email addresses &amp; Internet IDs. </p>
<p>The whole ridiculous &#8220;one number, one device, one service provider, one voicemail, one identity&#8221;  concept is fading away as it becomes painfully obvious that exactly the opposite thing will occur. Individuals will have an expanding multiplicity of numbers &amp; contact mechanisms. Some will be linked, others kept safely separate.</p>
<p>Dean</p>
]]></content:encoded>
	</item>
</channel>
</rss>

