The good, bad and ugly of a VoIP implementation

Facing frequent outages in the DSL lines serving 50-plus corporate-owned Gold's gyms, Bobby Badugu knew it was time for a significant network upgrade. After conducting due diligence in April into the various options including satellite, frame relay and a different DSL provider, he opted for a carrier-provided voice-over-IP (VoIP) service. That's when the trouble began.

In the months that followed, the vice president of IT for Gold's Gym, based in Dallas, learned some valuable lessons about not only VoIP, but any major network project that involves upgrades to numerous, far-flung sites. Badugu shared his insights in a presentation at the recent Network World IT Roadmap Conference in Dallas. He said the lessons include using a phased implementation process; establishing clear service-level agreements (SLA), including penalties; and conducting a thorough technology assessment to identify potential problems.

When the rollout began in June, it was scheduled to take eight weeks. As of mid-November, the data portion of the rollout is complete, but only about 20% of the voice lines have been ported to the VoIP network. Badugu remains bullish on VoIP, expects benefits including a 35% to 40% savings in voice and data service costs, and already is saving $6,000 to $10,000 on his conference calling. But if he had it to do over, he'd do more than a few things differently.

Click Here to Continue Reading "The good, bad and ugly of a VoIP implementation"

« Avaya buys Traverse Networks | Main | Case study: VoIP implementation - Gold's Gym »