Commentary

Eric Krapf
Editor  

Avaya Plus Tandberg?

In what is probably the first really interesting consolidation rumor I've heard in a long time, there are reports that Silver Lake, the private equity firm that owns Avaya, has approached Tandberg about acquiring that video-focused vendor.

In what is probably the first really interesting consolidation rumor I've heard in a long time, there are reports that Silver Lake, the private equity firm that owns Avaya, has approached Tandberg about acquiring that video-focused vendor.This would be a complementary acquisition rather than a duplicative one; it'd be a vendor (or its owner) buying technology, rather than buying market share. In other words, it'd be the kind of acquisition Cisco does. Which happens to be a pretty successful model.

Indeed, a Silver Lake-Tandberg deal -- assuming Avaya played into the scenario -- would really set Avaya apart and would arguably make Avaya the most credible alternative to Cisco for enterprise communications. It's getting harder and harder to escape the conclusion that video is moving from nice-to-have/status symbol, to critical element of a communications solution going forward (Irwin Lazar thinks so). Of course, video means lots of different things: Desktop, room, telepresence. All but desktop seem like a pretty good bet to take off for business purposes (also see this Wainhouse Research feature article.


More Telecom Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

But if there's another big winner in this scenario besides Avaya, I'd have to say that, in fact, it's Cisco, on both the perception and the reality. In terms of perception, an Avaya-Tandberg mashup essentially validates Cisco's big push into telepresence. I was among those who were very skeptical about telepresence; it just seemed too expensive and, frankly, over the top -- with the lighting and the color design and the C-shaped table and all. But what the ensuing two years have taught us is that the telepresence room may well be the Apple interface writ large: It's just cool, and it makes people go, "Ooooh" and "Aaaah." Technologists discount this factor at their peril.

And, of course, Cisco wins big on the substance if video/telepresence rooms become a standard feature of corporate offices, because that's gonna take a *lot* of bandwidth. In fact, that was one of the reasons I was skeptical of telepresence when Cisco first came out with it: It seemed like just too naked a ploy, too obvious an attempt to get people to upgrade their routers yet again. But damned if it didn't work. Cisco just keeps figuring out ways for its competitors to sell more bandwidth and QOS for Cisco to provision.

A final aspect to watch is the competition/cooperation/partnership view of things. Cisco looms as the only real end-to-end choice, the one-stop shop. Microsoft could be this at the application layer, but you'll always have Cisco in the network, where Microsoft is absent. The contrasting vision is, if not best-of-breed, at least multivendor. With the Siemens-Enterasys JV, there's clearly an attempt to leverage new accounts for both vendors, at the same time that there's a realization that Enterasys still needs customers beyond Siemens users, and Siemens users will have vendors besides Enterasys in their IP infrastructures.

Some enterprises may be truly all-Cisco shops, but going forward it's likely that many will remain multivendor, whether intentionally or by circumstance (M&As, installed base not going away, etc.). Which raises a point about telepresence: If it does become business-critical, or at least something that every business has, there will be intense pressure on the vendors to make their systems interoperate, which they don't today. Cisco may not be thrilled by that, but it will be driven by its own success.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links