Voice over IP is a (fast) moving target
What a difference a year makes. No matter how you slice and dice the numbers, the popularity of voice over IP grew by leaps and bounds in 2001. The number of installed voice-over-IP networks, the number of players in the voice-over-IP arena, the dollars spent on voice-over-IP products, the number of channels shipped and even the capacity of voice-over-IP products -- all of these elements more than doubled last year.
A few years ago, voice over IP was the domain of just a handful of early pioneers including 3Com, Cisco, Clarent, Nuera Communications and Hypercom. But now this convergence technology is finally being embraced by more traditional networking and telecommunications vendors that previously viewed voice over IP as a serious threat to their installed base.
According to an ongoing survey conducted by Miercom, these early voice-over-IP pioneers have been joined by the classic PBX vendors -- Alcatel, Avaya, Ericsson, Mitel, NEC, Nortel Networks and Siemens. Within the last year, all of the vendors have introduced viable voice-over-IP products, often in the form of add-ons, which "IP-enable" the latest versions of their time-division multiplexer (TDM) and switching matrix-based PBXs. We have seen this technology working -- with good to excellent voice quality and acceptable to very good reliability. In the early days, that wasn't always the case.
Interoperability among voice-over-IP products has been a major stumbling block to widespread acceptance of the technology. The ITU-T's H.323 "umbrella" standard, the first posed for voice-over-IP interoperability, proved complex and difficult to implement. As a result, other less-unwieldy standards were posed in its place, and until recently, we have seen little consensus on which voice-over-IP standards would be most widely implemented.
However, we are now beginning to see some general agreement within the vendor community about where voice-over-IP standards are headed. Based on Miercom's latest survey of voice-over-IP vendors, a number of relative standards -- among them the ITU-T's H.323, the Internet Engineering Task Force (IETF) Session Initiation Protocol (SIP) and Media Gateway Control Protocol (MGCP), and International Softswitch Consortium (ISC) specifications, and the ITU-T's H.248/ Megaco -- will all coexist. So don't expect any single standard to emerge as the basis for interoperability -- at least not anytime soon.
The prevailing opinion among vendor respondents is that H.323 will become the enterprise legacy standard, while MGCP and H.248/ Megaco will be used between carriers' call agents and other media gateways.
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
jfruh
Apple syncing patent can't come soon enough
pasmith
New Twitter features borrow from 3rd party clients
Esther Schindler
Open Source Changes the Software Acquisition Process
mikelgan
How to set up continuous podcast play on the new iTunes
David Strom
Five important Windows 7 mobility features
sjvn
Guard your Wi-Fi for your own sake
Sandra Henry-Stocker
Grepping on Whole Words
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.













