<?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: Unified Communications and Simplicity</title>
	<atom:link href="http://gipscorp.com/blog/2008/12/03/unified-communications-and-simplicity/feed/" rel="self" type="application/rss+xml" />
	<link>http://gipscorp.com/blog/2008/12/03/unified-communications-and-simplicity/</link>
	<description>The GIPS Blog</description>
	<lastBuildDate>Tue, 02 Feb 2010 01:09:43 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Hermansen</title>
		<link>http://gipscorp.com/blog/2008/12/03/unified-communications-and-simplicity/comment-page-1/#comment-27</link>
		<dc:creator>John Hermansen</dc:creator>
		<pubDate>Thu, 04 Dec 2008 01:30:33 +0000</pubDate>
		<guid isPermaLink="false">http://gipscorp.com/blog/?p=58#comment-27</guid>
		<description>Tsahi,

You bring up a very good point about UC not being confined to just IM and VoIP, and the need for a more coherent definition. The way I usually think of it is to use a paradigm that places the PC (and probably eventually a mobile device) as the driving force for functionality that used to reside on separate devices. Furthermore, a single application that enables not only IM and VoIP, but video, email, unified messaging, and intuitive voice and video conferencing seems to be the direction most people are heading. That being said, I think Roar hints at a trend that seems to be the dominant force at the moment, and that is enterprises taking a staged approach to UC. For reasons pertaining to budget, infrastructure, and uncertainty, many companies are choosing to implement many features usually associated with UC one step at a time. So, for instance, a company may choose to utilize a VoIP or IM solution, but may still rely on hosted conferencing services, instead of making a big investment in an on-premise, unified solution. I would imagine that this will continue given the current economic climate.</description>
		<content:encoded><![CDATA[<p>Tsahi,</p>
<p>You bring up a very good point about UC not being confined to just IM and VoIP, and the need for a more coherent definition. The way I usually think of it is to use a paradigm that places the PC (and probably eventually a mobile device) as the driving force for functionality that used to reside on separate devices. Furthermore, a single application that enables not only IM and VoIP, but video, email, unified messaging, and intuitive voice and video conferencing seems to be the direction most people are heading. That being said, I think Roar hints at a trend that seems to be the dominant force at the moment, and that is enterprises taking a staged approach to UC. For reasons pertaining to budget, infrastructure, and uncertainty, many companies are choosing to implement many features usually associated with UC one step at a time. So, for instance, a company may choose to utilize a VoIP or IM solution, but may still rely on hosted conferencing services, instead of making a big investment in an on-premise, unified solution. I would imagine that this will continue given the current economic climate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://gipscorp.com/blog/2008/12/03/unified-communications-and-simplicity/comment-page-1/#comment-26</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Wed, 03 Dec 2008 22:16:20 +0000</pubDate>
		<guid isPermaLink="false">http://gipscorp.com/blog/?p=58#comment-26</guid>
		<description>Unified also means having a single source (client) to emminate all types of communication from.  Currently in my office, I have a ShoreTel deskphone, ShoreTel Call Manager software, MS Outlook for email, and MS Office Communicator for IM.  Hardly unified!</description>
		<content:encoded><![CDATA[<p>Unified also means having a single source (client) to emminate all types of communication from.  Currently in my office, I have a ShoreTel deskphone, ShoreTel Call Manager software, MS Outlook for email, and MS Office Communicator for IM.  Hardly unified!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tsahi Levent-Levi</title>
		<link>http://gipscorp.com/blog/2008/12/03/unified-communications-and-simplicity/comment-page-1/#comment-25</link>
		<dc:creator>Tsahi Levent-Levi</dc:creator>
		<pubDate>Wed, 03 Dec 2008 19:06:46 +0000</pubDate>
		<guid isPermaLink="false">http://gipscorp.com/blog/?p=58#comment-25</guid>
		<description>Roar,
Unified Communications should be MORE than IM/VoIP - we have this for over 3 years now and for consumers not just enterprises.
Please have been using Skype and other IM clients to communicate without their IT departments installing and rolling out a &quot;corporate&quot; service for them.
Someone needs to sit down and define UC in a way that will make sense and remove all of this hype nonsense, otherwise, people will just say that &lt;a href=&quot;http://blog.radvision.com/voipsurvivor/2008/07/31/there-is-no-such-thing-as-uc-social-media-web20-or-phone20/&quot; rel=&quot;nofollow&quot;&gt;there is no such thing as UC&lt;/a&gt;...</description>
		<content:encoded><![CDATA[<p>Roar,<br />
Unified Communications should be MORE than IM/VoIP &#8211; we have this for over 3 years now and for consumers not just enterprises.<br />
Please have been using Skype and other IM clients to communicate without their IT departments installing and rolling out a &#8220;corporate&#8221; service for them.<br />
Someone needs to sit down and define UC in a way that will make sense and remove all of this hype nonsense, otherwise, people will just say that <a href="http://blog.radvision.com/voipsurvivor/2008/07/31/there-is-no-such-thing-as-uc-social-media-web20-or-phone20/" rel="nofollow">there is no such thing as UC</a>&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
