This announcement from AudioCodes is interesting on a few levels. For one thing, it shows the continuing move to an emphasis on software within the enterprise communications industry; I had a chance to talk with Alan Percy of AudioCodes about the new release, and he called it a "major change" for AudioCodes to be coming out with a pure software product. Up to now, we've all known AudioCodes for their hardware focus--gateways and phones.Another thing this product points up is the need for integration and interoperability in Unified Communications/VOIP--and what it says about the industry that there is such a need. I mean, let's face it: The headline of this press release is, "AudioCodes Facilitates Use of Standard SIP Phones with Microsoft Office Communications Server."
That headline tells you everything that's wrong, or at least lacking, when it comes to interoperability: The phrase "standard SIP," which we've all seen before, implies (accurately) that there's non-standard SIP. And the fact that you need an additional piece of software to connect a SIP server (OCS) with a SIP phone if that SIP phone isn't made by the same manufacturer, tells you a lot.
I mean, honestly, I thought the whole thing with SIP phones was, when we finally got them, we wouldn't have to worry about proprietary protocols.
Mind you, I'm not criticizing AudioCodes in the least--they're filling a need in the market. As Alan pointed out to me, a lot of companies are interested in migrating toward OCS, but they want to support IP telephony gear that's already in place. But the fact that such a product is needed tells you a lot about the interoperability challenges that lie ahead.
