Voice over Internet protocol (VoIP)

B. Goode

Proceedings of the IEEE · 2002 · 483 citations · 9 references

Concepts

TL;DR

Voice over Internet protocol (VoIP) was once predicted to be just another Internet application, but engineering challenges such as delay–bandwidth tradeoffs and quality‑of‑service requirements complicate its deployment. This paper addresses the technical aspects of implementing VoIP, focusing on practical engineering considerations rather than forecasting convergence timelines. The authors review codec choice, delay budgeting, QoS strategies, call‑signaling protocols (H.323, SIP, MGCP, Megaco/H.248), IP telephony routing, and NAT/firewall challenges to guide VoIP implementation.

Abstract

During the Internet stock bubble, articles in the trade press frequently said that, in the near future, telephone traffic would be just another application running over the Internet. Such statements gloss over many engineering details that preclude voice from being just another Internet application. This paper deals with the technical aspects of implementing voice over Internet protocol (VoIP), without speculating on the timetable for convergence. First, the paper discusses the factors involved in making a high-quality VoIP call and the engineering tradeoffs that must be made between delay and the efficient use of bandwidth. After a discussion of codec selection and the delay budget, there is a discussion of various techniques to achieve network quality of service. Since call setup is very important, the paper next gives an overview of several VoIP call signaling protocols, including H.323, SIP, MGCP, and Megaco/H.248. There is a section on telephony routing over IP (TRIP). Finally, the paper explains some VoIP issues with network address translation and firewalls.

References

9