<?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: H.325 &#8211; Is a rehash necessary ?</title>
	<atom:link href="http://blog.roychowdhury.org/2006/06/21/h325-is-a-rehash-necessary/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.roychowdhury.org/2006/06/21/h325-is-a-rehash-necessary/</link>
	<description></description>
	<lastBuildDate>Tue, 20 Dec 2011 10:18:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: ferdinand</title>
		<link>http://blog.roychowdhury.org/2006/06/21/h325-is-a-rehash-necessary/comment-page-1/#comment-36</link>
		<dc:creator>ferdinand</dc:creator>
		<pubDate>Thu, 19 Apr 2007 12:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/06/21/h325-is-a-rehash-necessary/#comment-36</guid>
		<description>H.323 and SIP are &quot;over IP&quot; protocols designed as were designed other &quot;over IP&quot; protocols use for DATA over Data Networks, more or less seamless protocols. Trouble is that the aim of VoIP is one day or another to replace  the good old PSTN voice Network. Operators will then offers full VoIP service with some portability of public phone numbers and the same level of service that PSTN was achieving. But to be able to do that, they will need another notseamless architecture and protocols as there were organized on the PSTN. H.323 and SIP are all the way through. There are both public and private at the sametime, they won&#039;t match.</description>
		<content:encoded><![CDATA[<p>H.323 and SIP are &#8220;over IP&#8221; protocols designed as were designed other &#8220;over IP&#8221; protocols use for DATA over Data Networks, more or less seamless protocols. Trouble is that the aim of VoIP is one day or another to replace  the good old PSTN voice Network. Operators will then offers full VoIP service with some portability of public phone numbers and the same level of service that PSTN was achieving. But to be able to do that, they will need another notseamless architecture and protocols as there were organized on the PSTN. H.323 and SIP are all the way through. There are both public and private at the sametime, they won&#8217;t match.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul E. Jones</title>
		<link>http://blog.roychowdhury.org/2006/06/21/h325-is-a-rehash-necessary/comment-page-1/#comment-35</link>
		<dc:creator>Paul E. Jones</dc:creator>
		<pubDate>Thu, 15 Mar 2007 08:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/06/21/h325-is-a-rehash-necessary/#comment-35</guid>
		<description>The definition of H.325 is still in progress, so it is neither centralized or decentralized.&lt;br/&gt;&lt;br/&gt;However, there are a lot of problems with SIP and H.323.  They are 11 year old protocols that do not deliver more than just voice and video.  It is virtually impossible to add any new functionaity to a SIP phone, for example.  Where is app sharing?  Whiteboarding?  The concepts behind H.325 enable multiple application providers to provide applications that connect to H.325 and become a part of user&#039;s capabilities.  Just as one example, you can use your mobile phone to view an HDTV transmission, with the video delivered directly to the TV, not to the mobile device.&lt;br/&gt;&lt;br/&gt;Paul</description>
		<content:encoded><![CDATA[<p>The definition of H.325 is still in progress, so it is neither centralized or decentralized.</p>
<p>However, there are a lot of problems with SIP and H.323.  They are 11 year old protocols that do not deliver more than just voice and video.  It is virtually impossible to add any new functionaity to a SIP phone, for example.  Where is app sharing?  Whiteboarding?  The concepts behind H.325 enable multiple application providers to provide applications that connect to H.325 and become a part of user&#8217;s capabilities.  Just as one example, you can use your mobile phone to view an HDTV transmission, with the video delivered directly to the TV, not to the mobile device.</p>
<p>Paul</p>
]]></content:encoded>
	</item>
</channel>
</rss>

