OverviewVideo conferencing is typically not a protocol that is accelerated under the common understanding of acceleration. It is UDP based and as such does not have the same limitations as TCP that would allow acceleration technology to benefit it. Video traffic needs to be provided QoS and bandwidth guarantees as a first step. Then, the customer must evaluate the issue they are trying to solve that makes them think acceleration is needed? If it is ghosting or choppiness, then QoS is the solution.
There are other types of video ÒaccelerationÓ that people might refer to, but these are not accelerated by addressing the performance impact of high latency. One is caching video objects like youtube or vimeo video files, the other is being able to convert a unicast video stream to multicast which, as example would allow one video stream to come in on an internet connection (ie live stream of the President addressing the nation) and then split that out to several viewing stations such that the internet link does not have X number of streams passing for X number of viewing stations. It would then be a one stream to many so the internet link would not be saturated.
Caching of video files, content, and dynamic URL's like YouTube is a huge advantage to reducing WAN traffic and improving user experience. This technology should be employed on almost every WAN link with today's increased usage of video content on the internet and in collaboration solutions. However, without QoS, caching it is only a point solution. By combining QoS, caching, and the proper visibility to understand the behavior and utilization of the network a customer can achieve a complete solution.