<?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: What is Holding UC Back?</title>
	<atom:link href="http://lippisreport.com/2010/04/what-is-holding-uc-back/feed/" rel="self" type="application/rss+xml" />
	<link>http://lippisreport.com/2010/04/what-is-holding-uc-back/</link>
	<description>Resources for Network / IT Business Decision Makers</description>
	<lastBuildDate>Tue, 22 May 2012 00:38:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: dubois</title>
		<link>http://lippisreport.com/2010/04/what-is-holding-uc-back/comment-page-1/#comment-197572</link>
		<dc:creator>dubois</dc:creator>
		<pubDate>Tue, 27 Apr 2010 04:55:31 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=2928#comment-197572</guid>
		<description>IM vendors resisted interoperating for long enough to relegate their technology to a small role in history. IM could have replaced SMTP e-mail, enabling rich communications with presence. UC vendors could take heed of that example.

The biggest barrier facing UC vendors, though, isn&#039;t tier interop or video bandwidth. It&#039;s an inability to tell a compelling value story to each market.</description>
		<content:encoded><![CDATA[<p>IM vendors resisted interoperating for long enough to relegate their technology to a small role in history. IM could have replaced SMTP e-mail, enabling rich communications with presence. UC vendors could take heed of that example.</p>
<p>The biggest barrier facing UC vendors, though, isn&#8217;t tier interop or video bandwidth. It&#8217;s an inability to tell a compelling value story to each market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurie Shook</title>
		<link>http://lippisreport.com/2010/04/what-is-holding-uc-back/comment-page-1/#comment-197029</link>
		<dc:creator>Laurie Shook</dc:creator>
		<pubDate>Tue, 20 Apr 2010 14:19:11 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=2928#comment-197029</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;RT @NickLippis: UC &amp; Video conferencing need industry interoperability standards if it&#039;s to enter prime time http://bit.ly/9gizOe&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @NickLippis: UC &amp; Video conferencing need industry interoperability standards if it&#39;s to enter prime time <a href="http://bit.ly/9gizOe" rel="nofollow">http://bit.ly/9gizOe</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Lippis</title>
		<link>http://lippisreport.com/2010/04/what-is-holding-uc-back/comment-page-1/#comment-197023</link>
		<dc:creator>Nick Lippis</dc:creator>
		<pubDate>Tue, 20 Apr 2010 13:59:41 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=2928#comment-197023</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;UC &amp; Video conferencing need industry interoperability standards if it&#039;s to enter prime time http://bit.ly/9gizOe&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">UC &amp; Video conferencing need industry interoperability standards if it&#39;s to enter prime time <a href="http://bit.ly/9gizOe" rel="nofollow">http://bit.ly/9gizOe</a></span></span></span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

