Unified Communications

12:51 PM
Art Wittmann
Art Wittmann
Commentary
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Videoconferencing On Demand: Maybe Vidyo, Not Cisco

By virtualizing its video router, Vidyo adds the powerful dimension of scalability to its conferencing system. But it'll take some bigger players to make the technology pervasive.

Will videoconferencing ever be as pervasive as voice-only conferencing? For years, the argument ended quickly with a quick look at the quality versus cost curve. If you want a grand room enabled for what Cisco has termed telepresence, it'll cost you a few hundred thousand dollars per copy and you'll need a nice fat dedicated network to make it work. You'll have to leave the corporate jet idling for a quite a while to justify the expense based on travel savings alone. On the flip side, point-to-point Skype-style videoconferencing hasn't been a rich enough experience to displace the phone--though that's rapidly changing.

If the economics were taken out of question--if you really could do high-quality videoconferencing for near the price of phone conferencing--the discussion quickly changes to one of user preferences and the value of actually seeing each other. We'll leave that discussion for another time.

Depending on who you talk to, the economics of video conferencing is changing radically. The latest evidence of this is Vidyo's announcement Tuesday that it has certified its "video router" (what others call an MCU--more on that in a bit) to run in a virtual machine. Vidyo says it will release products using the new capability in 2012, and that these will mostly be aimed at service providers and large enterprises. The virtualized capability is an interesting one for Vidyo and, while I haven't seen the actual products the company will release, I think there may well be a significant play for it with enterprises of all sizes.

[ Learn more. Check out our report on Enterprise Video: A Viable Option? ]

Exactly what impact Vidyo's announcement will have on the market depends on a lot of variables, including such wildcards as how the company packages and deploys the new technology and how industry giants like Cisco, Microsoft, and Polycom evolve their strategies.

It's likely that many of you aren't familiar with Vidyo, but for those of you who are familiar, and who've sat through an evangelical presentation by the company, you know that the company is convinced it has a better way to do videoconferencing. At least at an architectural level, they in fact do have a better way. If that sounds like a damning of architectures of the big guys like Cisco and Polycom, then good, because that's how I mean it.

If you could start with clean slate and design a videoconferencing protocol, how would it work? Here are some likely design goals. First, you'd want to support a lot of different end points with lots of different capabilities--some will have dedicated large screen video, while others will run the video in windows on laptops or even mobile devices. You'd want to be able to simultaneously support end points with lots bandwidth as well as those on Wi-Fi, cable modems, and DSL lines, and even those on 3G wireless connections.

You'd start by recognizing that with the possible exception of a few phones, end points, with their dual core ARM/Xeon level CPUs, have all the horsepower you'd want to do complex video encoding. If you could, you'd encode the video just once, and do it in such a way that you'd never have to decode and encode it again. Once the video is encoded, you'd want a device at the network layer that knew about the various end points, and that send them the appropriate data stream for their device. This would be largely a routing function, and a matter of selecting the right stuff from the high quality encoding stream that was appropriate for each end point.

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Chip the AV geek
50%
50%
Chip the AV geek,
User Rank: Apprentice
11/22/2011 | 4:38:04 PM
re: Videoconferencing On Demand: Maybe Vidyo, Not Cisco
Maybe Vidyo will have to share the market with Magor Communications. Virtualizing Vidyo's Linux-based videoconference bridge software may have some applications, but it still requires engineering a central network server everyone connects to. Magor eliminates the bridge altogether, using their own 1080p SVC codec and connecting multipoint videoconferences directly, peer-to-peer.
pvanhoesen
50%
50%
pvanhoesen,
User Rank: Apprentice
12/4/2011 | 4:51:24 AM
re: Videoconferencing On Demand: Maybe Vidyo, Not Cisco
In my opinion, the main reason Vidyo is still in the backwater is their outlandish thinking about their API access.

They are charging vast sums for their API kits - a great way to keep all levels of developers demo'ing and experimenting with someone else's platform solution.
Polycom and Cisco at least have enough sense to understand that API access is the one thing that is immediately required by any serious shops for prototyping.

No serious players are going to consider this without full access to the API set for free or close to it.

Vidyo seems to be tripping over a chance at real market ubiquity to pick up a few API pennies...

While they are picking up their pennies, the competition is still being picked because those solutions can at least be easily and inexpensively incorporated into custom platform solutions... time is not on their side.
Cartoon
White Papers
Register for Network Computing Newsletters
Current Issue
2014 State of Unified Communications
2014 State of Unified Communications
If you thought consumerization killed UC, think again: 70% of our 488 respondents have or plan to put systems in place. Of those, 34% will roll UC out to 76% or more of their user base. And there’s some good news for UCaaS providers.
Video
Slideshows
Twitter Feed