Cisco's Annual UC Analyst Summit: Save me from Ubiquitous UCCisco's Annual UC Analyst Summit: Save me from Ubiquitous UC

Cisco brought the UC-analyst community together in Toronto this week, live and in person—after all, we don’t all have access to telepresence systems. From the start it was clear that the two groups have very different views on how to define UC. Cisco has effectively branded its entire applications business as “unified communications.” That’s how the company reports its earnings, and it’s how it sells its products (and compensates sales people). But UC isn’t all forms of communications that could conceivably be integrated (i.e., unified) some day.

UC isn’t IP telephony, although IP phones can support UC, and although UC is probably better served by IPT than traditional systems. So including your IPT phone sales in UC revenue numbers is a semantic mistake (I don’t think the SEC cares, but end users and investors should). Likewise, unified messaging isn’t UC—it’s a part of UC. Telepresence certainly isn’t UC—especially Cisco’s, which can’t integrate with other video conferencing systems, never mind a UC desktop or mobile application.

(To be fair, Cisco isn’t the only vendor doing this. Recently, I received a press release announcing an agreement between ShoreTel and AudioCodes, “Joining Forces on UC.” But the release touted the integration of ShoreTel’s IP telephony with Microsoft Exchange Unified Messaging. ShoreTel’s VP of Marketing was quoted as saying, “Combined with AudioCodes’ gateways, our enterprise customers can seamlessly combine collaborative applications like Microsoft Exchange with world-class IP telephony.” But MS Exchange isn’t a collaborative application, and Unified Messaging isn’t UC. What’s interesting is that AudioCodes will support integration with Office Communications Server, but that’s not the relationship ShoreTel is hyping.)

Clearly, vendors are changing the meaning of “unified communications” to suit their particular business needs. And that’s not doing their customers any good—they’re just confused by the disparate definitions in the marketplace. It’s worth noting, for example, that the customer case studies Cisco chose to highlight at the event were focused on their use of IPT (valuable, sure, but not UC) and/or contact center applications (some of which incorporate presence info for agent routing purposes, but that’s still a pretty narrow definition of UC). If those customers think they’ve deployed unified communications, they’re mistaken—and they may be in for a surprise down the road, as their competition gets it right and sees the benefits sooner as a result.

That said, Cisco showed off some cool stuff at the conference. Here’s a look at some of the more intriguing bits:

Cisco was a little schizophrenic when it came to discussing the “co-opetition” that exists between it and its partners, including Microsoft and IBM. Although important integration is either available now or coming in the next few quarters, what we all really want is open, out-of-the-box interoperability. That’s not likely anytime soon, although Cisco would seem to be in a pretty good position to make it happen.

Indeed, Cisco seemed to flip-flop when it came to this issue, with one presenter hammering home Cisco’s network-centric approach and suggesting that customers will be best-served by an end-to-end Cisco implementation, and the next echoing VP of enterprise and mid-market solutions Andy Cohen’s statement, “Collaboration demands openness.” Which is it? Clearly the latter, of course.