<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>VoIP as you are!</title><link>http://blogs.technet.com/markdea/archive/2007/06/05/voip-as-you-are.aspx</link><description>One of the questions I get asked at events, almost without fail, is 'Are Microsoft creating a PBX replacement?', hopefully this post and the relating web site should give you the answer if you have not already heard it from me directly. If your PBX could</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: VoIP as you are!</title><link>http://blogs.technet.com/markdea/archive/2007/06/05/voip-as-you-are.aspx#1166253</link><pubDate>Thu, 07 Jun 2007 01:23:13 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1166253</guid><dc:creator>Ewan</dc:creator><description>&lt;p&gt;It's like, &amp;quot;VoIP is all about software, stupid!&amp;quot;&lt;/p&gt;
&lt;p&gt;I think we're getting better at making this clear: at the end of the day, Microsoft is a software company and by getting into VoIP territory, we're making it a software business rather than a proprietary, &amp;quot;hardware&amp;quot; thing. I say &amp;quot;hardware&amp;quot; though in recent years, a lot of telecoms kit has largely been commodity-like hardware in a grey box but with proprietary software. What the industry seems to be doing now (and MS is active in that movement) is in making the software bit more standardised and helping make the hardware less grey box and more standard x86 server vendor kit.&lt;/p&gt;
&lt;p&gt;$0.02 :)&lt;/p&gt;
&lt;p&gt;Ewan&lt;/p&gt;</description></item></channel></rss>