Lessons from real-world VOIP

23.01.2006
Will 2006 be the year that voice and data convergence really takes off? Looking back, VOIP was one of the hottest and most hyped technologies of 2005. Yet despite all the attention, only about a third of IT departments have rolled out full-fledged deployments, according to a recent survey by Forrester Research.

Much of the reluctance can be attributed to the burden that VOIP can place on even the most efficient networks, in addition to concerns about voice quality, scalability, and QoS. Still, many experts say present-day technologies have smoothed over most of the potholes. Nonetheless, there is extensive provisioning involved in implementing and maintaining a VOIP system. Fortunately, the right deployment strategy can dispel any apprehension.

"People were told that VOIP is going to be the greatest thing," says William Stofega, VOIP research director at IDC. "But in some cases, people didn't do the necessary network planning. Ninety-nine percent of all VOIP network implementations that fail do so because IT departments didn't do their homework."

So, what do you need to make it work? How will you manage it? And how much will it cost? The answers vary and depend on numerous factors. Practically no one is ripping and replacing but rather installing hybrids that put VOIP where it yields the greatest benefit while leaving legacy systems in place elsewhere. Regardless of the scenario, early adopters are providing clear answers.

Proceed With Caution

Good planning begins with a comprehensive review of your existing infrastructure. For fees starting around US$5,000, telecom equipment vendors will help you decide which systems can take on voice traffic and perform adequately, and which ones need to be replaced. A rigorous pre-assessment also aids in identifying potential network bottlenecks.