<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Mark Nickerson's Blog</title><subtitle type="html">Real Time Collaboration discussions, web conferencing, audio and video conferencing, futures</subtitle><id>http://blogs.technet.com/unified_communications/atom.xml</id><link rel="alternate" type="text/html" href="http://blogs.technet.com/unified_communications/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.technet.com/unified_communications/atom.xml" /><generator uri="http://communityserver.org" version="2.1.61025.2">Community Server</generator><updated>2005-07-11T09:04:00Z</updated><entry><title>The Evolution of Unified Communications to Software</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/unified_communications/archive/2008/10/06/the-evolution-of-unified-communications-to-software.aspx" /><id>http://blogs.technet.com/unified_communications/archive/2008/10/06/the-evolution-of-unified-communications-to-software.aspx</id><published>2008-10-06T21:57:00Z</published><updated>2008-10-06T21:57:00Z</updated><content type="html">&lt;P&gt;Software is becomming the platform of choice for Unified Communications.&amp;nbsp; PBX's are transforming from proprietary silod platforms to software application running on servers.&amp;nbsp; The big players in this space are Micrososft, IBM and Cisco (in addition the the PBX vendors own offerings).&amp;nbsp; Cisco has taken the "acquire" approach, while Microsoft and IBM are developing mostly internerally.&amp;nbsp; The big challenge today is the convergence to the corporate IP network.&amp;nbsp; Voice and video have unique requirements for bandwidth, and most companies are re-engineering their networks to address these new needs.&amp;nbsp; Microsoft's&amp;nbsp;technology is a bit trickeir since bandwidth consumption is adaptive. &lt;/P&gt;
&lt;P&gt;Most companies are evaluating options or traffic prioritization. QOS is the most common technique.&amp;nbsp; Though QOS does not guarantee a quality experience, it certainly can help network managers prioritize traffic, especially on WAN links that are already saturated.&lt;/P&gt;
&lt;P&gt;Though we're in tough economic times, UC is still popular as businesses are looking to reduce&amp;nbsp;communications costs.&amp;nbsp; Audio conferencing and Web Conferencing are hard cost savings which have sparked interest of late.&amp;nbsp; Businesses will still have to&amp;nbsp;spend money to save money.&lt;/P&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3133012" width="1" height="1"&gt;</content><author><name>marknick</name><uri>http://blogs.technet.com/members/marknick.aspx</uri></author></entry><entry><title>Video Conferencing - The good, the bad, the ugly</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/unified_communications/archive/2005/07/11/407520.aspx" /><id>http://blogs.technet.com/unified_communications/archive/2005/07/11/407520.aspx</id><published>2005-07-11T16:29:00Z</published><updated>2005-07-11T16:29:00Z</updated><content type="html">Working for MSFT in the Live Meeting group (web conferencing) I spend alot of time discussing Video Conferencing with customers.&amp;nbsp; The more I use video conferencing the more I start to question the value of this technology when applying to meetings.&amp;nbsp; I can understand the importance of seeing a presenter of an executive webcasts, but if they are presenting data its distracting and causes the audience to lose focus.&amp;nbsp; The better value I see is for the presenter to see the attendees video.&amp;nbsp; Then they could adapt their presentation based on the audience's expression.&amp;nbsp; As far as desktop video goes, I lose 30 minutes of productivity preparing for a video conference (comb hair, shave, nice shirt, etc.).&amp;nbsp; Still pictures that can be staged and re-used are better.&amp;nbsp; Maybe the better strategy is not to mix video with data conferencing since its too difficult to focus on both.&amp;nbsp; With the bandwidth expense of video I don't see enterprise adoption happeneing anytime soon.&amp;nbsp; What's more important: your CEO getting to Seibel to view the sales reports or Johnny IT having a video conference with Billy Sales?&amp;nbsp; Maybe IP v6 is the answer, until then most should keep the video traffic on dedicated links.&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=407520" width="1" height="1"&gt;</content><author><name>marknick</name><uri>http://blogs.technet.com/members/marknick.aspx</uri></author></entry><entry><title>IP Convergence</title><link rel="alternate" type="text/html" href="http://blogs.technet.com/unified_communications/archive/2005/07/11/407518.aspx" /><id>http://blogs.technet.com/unified_communications/archive/2005/07/11/407518.aspx</id><published>2005-07-11T16:10:00Z</published><updated>2005-07-11T16:10:00Z</updated><content type="html">&lt;P&gt;Seems like everybody is trying to ride on the IP network these days.&amp;nbsp; PBX's, video conferencing providers, VOIP.&amp;nbsp; Problem is, current networks are not designed for audio and video.&amp;nbsp; Real time conferencing components such as voice and video require significant "sustained" bandwidth.&amp;nbsp; Private networks have features such as QOS/bandwidth reservation, but not the public networks.&amp;nbsp; The next generation of IP (IP6) is&amp;nbsp;better suited for rich communications but it may be some time before its widely adopted.&amp;nbsp; In the mean time customer will need to decide if these technologies are worth the bandwidth expense.&amp;nbsp; Microsoft Office Communicator offer audio and video conferencing out of the box, however peer to peer only.&amp;nbsp; Multi-party is supported with a partner such as Radvision or Polycom.&amp;nbsp; You will also&amp;nbsp;need partner solutions to enable A/V over the public internet, since NAT and UDP do not traverse firewalls (research session border contollers/Jasomi).&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=407518" width="1" height="1"&gt;</content><author><name>marknick</name><uri>http://blogs.technet.com/members/marknick.aspx</uri></author></entry><entry><title>Wainhouse Research: Microsoft's Presence-Enabled Real-Time Communications Strategy </title><link rel="alternate" type="text/html" href="http://blogs.technet.com/unified_communications/archive/2005/07/11/407516.aspx" /><id>http://blogs.technet.com/unified_communications/archive/2005/07/11/407516.aspx</id><published>2005-07-11T16:04:00Z</published><updated>2005-07-11T16:04:00Z</updated><content type="html">&lt;P&gt;Wainhouse has just released a report on Microsoft's RTC strategy.&amp;nbsp; &lt;A href="http://www.wainhouse.com/reports/index.html#msft"&gt;http://www.wainhouse.com/reports/index.html#msft&lt;/A&gt;.&amp;nbsp; Great content covering&amp;nbsp;Microsoft's RTC strategy, challenges and partner ecosystem.&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=407516" width="1" height="1"&gt;</content><author><name>marknick</name><uri>http://blogs.technet.com/members/marknick.aspx</uri></author></entry></feed>