By Greg Paul
I have made the point in my Technology Seminars in USA and Canada that VoIP imposes additional network requirements. This story in IT Business Canada illustrates the point nicely.
“When voice over IP first began appearing on business networks, many people expected to simply fire it up and start talking. But when they tried it, a lot of what they had to say never made it to the other end of the line – which was probably a good thing, because when they discovered how well VoIP worked on their existing networks, some of their language wasn’t very polite.
Because many early VoIP adopters expected it to be plug and play, networks often got no pre-implementation testing to see if they were ready to handle voice, recalls Brad Masterson, product manager at Mississauga, Ont.-based Fluke Electronics Canada LP, a maker of network testing tools. That frequently led to problems when the IP telephony application was turned on.
In 2003 Jeremy Urwin, a technical sales support director at Telus Corp., told the story of LAN administrator who refused to have Telus check his network for VOIP readiness before going live, even when offered a discount on the work. “The first two calls went through flawlessly, “ Urwin reported. “The third call dropped, and guess who that was? That was the CIO.” Telus belatedly did the readiness report, the network was adjusted – and the customer got a new LAN administrator.
Such hubris on the part of network managers not only cost a few unfortunates their jobs, but battered the reputation of voice over IP technology and some of the vendors who sell it. As a result, some major VOIP vendors now insist on testing every network on which they install their wares to make sure beforehand that it’s ready for voice.”
Read the complete story here.