Jabber Acquisition Highlights Cisco Shortfalls in UC

UC without effective presence and IM is like telephony without dial-tone.

So here we have Cisco spending your contributions (remember the Cisco Energy Tax) to acquire Jabber to give them IM for their un-unified UC story. Does this result in a 41st server to deliver UC?

UC has to unify both the end user experience AND the underlying infrastructure, and I don't see Jabber moving Cisco towards the latter objective.

The opinions and views expressed in comments, blogs, etc. are those of the authors alone and not necessarily those of TMC, TMCnet, or its editors. TMCnet reserves the right to edit, delete, or otherwise make changes to the content that appears on these pages at its own discretion and as it deems necessary.
| 2 Comments | 0 TrackBacks

Listed below are links to sites that reference Jabber Acquisition Highlights Cisco Shortfalls in UC:

Jabber Acquisition Highlights Cisco Shortfalls in UC TrackBack URL : http://blog.tmcnet.com/mt/mt-tb.cgi/37542

2 Comments

Like Microsoft doesn't use alot of servers for their "UC" solution? Cisco is a cakewalk compared to other products.

TonyRyb responds: Server count is one dimension. Managing multiple systems is another. Both contribute to TCO.

You think a Jabber acquisition is a bad move? Interesting.

Explain to me Nortel's alternative for what Jabber delivers.

Leave comment to Jabber Acquisition Highlights Cisco Shortfalls in UC article

Recent Comments

  • Another Nortel Watcher: You think a Jabber acquisition is a bad move? Interesting. read more
  • Dan: Like Microsoft doesn't use alot of servers for their "UC" read more

Around TMCnet Blogs

Latest Whitepapers

TMCnet Videos