<?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"
	>
<channel>
	<title>Comments on: Waiting for Voice 2.0</title>
	<atom:link href="http://saunderslog.com/2006/11/06/waiting-for-voice-20/feed/" rel="self" type="application/rss+xml" />
	<link>http://saunderslog.com/2006/11/06/waiting-for-voice-20/</link>
	<description>A daily round table on the tech industry with experts and callers from all over the globe. Join us as we pick apart the news and get to the meat of what\'s happening out there.</description>
	<pubDate>Sat, 10 Jan 2009 00:29:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Mr Blog &#187; Blog Archive &#187; Open Telephony, beyond the abstract</title>
		<link>http://saunderslog.com/2006/11/06/waiting-for-voice-20/#comment-729195</link>
		<dc:creator>Mr Blog &#187; Blog Archive &#187; Open Telephony, beyond the abstract</dc:creator>
		<pubDate>Fri, 25 Apr 2008 03:07:54 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/11/06/waiting-for-voice-20/#comment-729195</guid>
		<description>[...] Saunders revisits the state of Voice 2.0 in a response to a post by Jim Van Meggelen regarding the lack of integration between PBX?s and [...]</description>
		<content:encoded><![CDATA[<p>[...] Saunders revisits the state of Voice 2.0 in a response to a post by Jim Van Meggelen regarding the lack of integration between PBX?s and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exploration Nonetheless &#187; Blog Archive &#187; Open Telephony, beyond the abstract</title>
		<link>http://saunderslog.com/2006/11/06/waiting-for-voice-20/#comment-78846</link>
		<dc:creator>Exploration Nonetheless &#187; Blog Archive &#187; Open Telephony, beyond the abstract</dc:creator>
		<pubDate>Fri, 15 Dec 2006 15:22:16 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/11/06/waiting-for-voice-20/#comment-78846</guid>
		<description>[...] Alec Saunders revisits the state of Voice 2.0 in a response to a post by Jim Van Meggelen regarding the lack of integration between PBXÃ¯Â¿Â½s and carriers.At a recent telephony conference, we saw many telcos reporting about the progress on their open platform initiatives and how there was this glorious future for us all to look forward to. They showed slides and used all the right language about it. That&#8217;s all well and good, when it is nothing more than slides, with no definitive dates and nothing concrete about it all really. I&#8217;m sure the carrier is quite comfortable talking about open-platforms, as long as it&#8217;s slideware discussing some some ill-defined &#8220;out there&#8221; future.But how comfortable are they when the idea of an open platform, that really lets third-parties offer tightly-coupled services to their customers, stops being just an &#8220;idea&#8221; and becomes a reality, here and now?The picture below shows what the PhoneGnome technology, as a platform, does to the value chain (or application stack) when an end user plugs in that little CPE device:On the left, we have the closed vertical platform provided by carriers today. The same applies whether we&#8217;re talking about a traditional 130 year-old carrier, or an upstart 3-year old VoIP player. The supposedly revolutionary 3 year-olds simply copied their grandparents when it comes to opening their platform to third-party innovation.On the right, we have the result after a customer connects the PhoneGnome device. With PhoneGnome installed, the services stack above &#8220;access&#8221; (the local number and local services) is open to any third party provider, without the support or cooperation of the underlying telco access provider required. It is &#8220;unbundling&#8221; at the customer premise (or &#8220;unbundling at the edge&#8221;) without the nightmare that is traditional telco-based &#8220;unbundling&#8221;.&#8220;Open&#8221; is beyond the abstract and slideware now. With the installation of a simple enabling CPE device, anyone&#8217;s service (and brand) can now be seamlessly inserted into the experience for any existing fixed line user, any telephone number anywhere, without the requirement to partner with the underlying telco. It is a &#8220;pay as you grow&#8221; model with no requirement for a large initial cap-ex outlay. The footprint is immediately the entire world, anywhere there is broadband internet and POTS service. And it is here now, in use by real customers, and empowering real non-telco third-party services, provided directly to existing telco customers. [...]</description>
		<content:encoded><![CDATA[<p>[...] Alec Saunders revisits the state of Voice 2.0 in a response to a post by Jim Van Meggelen regarding the lack of integration between PBXÃ¯Â¿Â½s and carriers.At a recent telephony conference, we saw many telcos reporting about the progress on their open platform initiatives and how there was this glorious future for us all to look forward to. They showed slides and used all the right language about it. That&#8217;s all well and good, when it is nothing more than slides, with no definitive dates and nothing concrete about it all really. I&#8217;m sure the carrier is quite comfortable talking about open-platforms, as long as it&#8217;s slideware discussing some some ill-defined &#8220;out there&#8221; future.But how comfortable are they when the idea of an open platform, that really lets third-parties offer tightly-coupled services to their customers, stops being just an &#8220;idea&#8221; and becomes a reality, here and now?The picture below shows what the PhoneGnome technology, as a platform, does to the value chain (or application stack) when an end user plugs in that little CPE device:On the left, we have the closed vertical platform provided by carriers today. The same applies whether we&#8217;re talking about a traditional 130 year-old carrier, or an upstart 3-year old VoIP player. The supposedly revolutionary 3 year-olds simply copied their grandparents when it comes to opening their platform to third-party innovation.On the right, we have the result after a customer connects the PhoneGnome device. With PhoneGnome installed, the services stack above &#8220;access&#8221; (the local number and local services) is open to any third party provider, without the support or cooperation of the underlying telco access provider required. It is &#8220;unbundling&#8221; at the customer premise (or &#8220;unbundling at the edge&#8221;) without the nightmare that is traditional telco-based &#8220;unbundling&#8221;.&#8220;Open&#8221; is beyond the abstract and slideware now. With the installation of a simple enabling CPE device, anyone&#8217;s service (and brand) can now be seamlessly inserted into the experience for any existing fixed line user, any telephone number anywhere, without the requirement to partner with the underlying telco. It is a &#8220;pay as you grow&#8221; model with no requirement for a large initial cap-ex outlay. The footprint is immediately the entire world, anywhere there is broadband internet and POTS service. And it is here now, in use by real customers, and empowering real non-telco third-party services, provided directly to existing telco customers. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
