<?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: Interoperability in SIP – state of the Art? - Part I</title>
	<atom:link href="http://blog.radvision.com/voipsurvivor/2008/01/15/is-sip-inteoperability-state-of-art-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.radvision.com/voipsurvivor/2008/01/15/is-sip-inteoperability-state-of-art-part-1/</link>
	<description>IMS &#38; V²oIP industry insights</description>
	<pubDate>Thu, 20 Nov 2008 10:47:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: To Do List 2008, or Crystal Ball 2008 post which never happened &#124; VoIP Survivor</title>
		<link>http://blog.radvision.com/voipsurvivor/2008/01/15/is-sip-inteoperability-state-of-art-part-1/#comment-6</link>
		<dc:creator>To Do List 2008, or Crystal Ball 2008 post which never happened &#124; VoIP Survivor</dc:creator>
		<pubDate>Tue, 29 Jan 2008 15:10:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.radvision.com/voipsurvivor/2008/01/15/is-sip-inteoperability-state-of-art-part-1/#comment-6</guid>
		<description>[...] used in today&#8217;s communications world, SIP stands out as being used the most, and with interoperability not being where it should be, so for the sake of this short post, we are focusing on SIP [...]</description>
		<content:encoded><![CDATA[<p>[...] used in today&#8217;s communications world, SIP stands out as being used the most, and with interoperability not being where it should be, so for the sake of this short post, we are focusing on SIP [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
