Voice over IP
Voice over Internet Protocol (VoIP), also called IP telephony, is a method and group of technologies for the delivery of voice communications and multimedia sessions over Internet Protocol (IP) networks, such as the Internet. The terms Internet telephony, broadband telephony, and broadband phone service specifically refer to the provisioning of communications services (voice, fax, SMS, voice-messaging) over the public Internet, rather than via the public switched telephone network (PSTN), also known as plain old telephone service (POTS).
The steps and principles involved in originating VoIP telephone calls are similar to traditional digital telephony and involve signaling, channel setup, digitization of the analog voice signals, and encoding. Instead of being transmitted over a circuit-switched network, the digital information is packetized and transmission occurs as IP packets over a packet-switched network. They transport media streams using special media delivery protocols that encode audio and video with audio codecs and video codecs. Various codecs exist that optimize the media stream based on application requirements and network bandwidth; some implementations rely on narrowband and compressed speech, while others support high-fidelity stereo codecs.
The most widely speech coding standards in VoIP are based on the linear predictive coding (LPC) and modified discrete cosine transform (MDCT) compression methods. Popular codecs include the MDCT-based AAC-LD (used in FaceTime), the LPC/MDCT-based Opus (used in WhatsApp), the LPC-based SILK (used in Skype), μ-law and A-law versions of G.711, G.722, and an open source voice codec known as iLBC, a codec that uses only 8 kbit/s each way called G.729.
Early providers of voice-over-IP services used business models and offered technical solutions that mirrored the architecture of the legacy telephone network. Second-generation providers, such as Skype, built closed networks for private user bases, offering the benefit of free calls and convenience while potentially charging for access to other communication networks, such as the PSTN. This limited the freedom of users to mix-and-match third-party hardware and software. Third-generation providers, such as Google Talk, adopted the concept of federated VoIP. These solutions typically allow dynamic interconnection between users in any two domains of the Internet, when a user wishes to place a call.
In addition to VoIP phones, VoIP is also available on many personal computers and other Internet access devices. Calls and SMS text messages may be sent via Wi-Fi or the carrier's mobile data network. VoIP provides a framework for consolidation of all modern communications technologies using a single unified communications system.
A variety of functions are needed to implement VoIP communication. Some protocols perform multiple functions, while others perform only a few and must be used in concert. These functions include:
- Network and transport – Creating reliable transmission over unreliable protocols, which may involve acknowledging receipt of data and retransmitting data that wasn't received.
- Session management – Creating and managing a session (sometimes glossed as simply a "call"), which is a connection between two or more peers that provides a context for further communication.
- Signaling – Performing registration (advertising one's presence and contact information) and discovery (locating someone and obtaining their contact information), dialing (including reporting call progress), negotiating capabilities, and call control (such as hold, mute, transfer/forwarding, dialing DTMF keys during a call [e.g. to interact with an automated attendant or IVR], etc.).
- Media description – Determining what type of media to send (audio, video, etc.), how to encode/decode it, and how to send/receive it (IP addresses, ports, etc.).
- Media – Transferring the actual media in the call, such as audio, video, text messages, files, etc.
- Quality of service – Providing out-of-band content or feedback about the media such as synchronization, statistics, etc.
- Security – Implementing access control, verifying the identity of other participants (computers or people), and encrypting data to protect the privacy and integrity of the media contents and/or the control messages.
VoIP protocols include:
- Session Initiation Protocol (SIP), connection management protocol developed by the IETF
- H.323, one of the first VoIP call signaling and control protocols that found widespread implementation. Since the development of newer, less complex protocols such as MGCP and SIP, H.323 deployments are increasingly limited to carrying existing long-haul network traffic.
- Media Gateway Control Protocol (MGCP), connection management for media gateways
- H.248, control protocol for media gateways across a converged internetwork consisting of the traditional PSTN and modern packet networks
- Real-time Transport Protocol (RTP), transport protocol for real-time audio and video data
- Real-time Transport Control Protocol (RTCP), sister protocol for RTP providing stream statistics and status information
- Secure Real-time Transport Protocol (SRTP), encrypted version of RTP
- Session Description Protocol (SDP), a syntax for session initiation and announcement for multi-media communications and WebSocket transports.
- Inter-Asterisk eXchange (IAX), protocol used between Asterisk PBX instances
- Extensible Messaging and Presence Protocol (XMPP), instant messaging, presence information, and contact list maintenance
- Jingle, for peer-to-peer session control in XMPP
- Skype protocol, proprietary Internet telephony protocol suite based on peer-to-peer architecture
Mass-market VoIP services use existing broadband Internet access, by which subscribers place and receive telephone calls in much the same manner as they would via the PSTN. Full-service VoIP phone companies provide inbound and outbound service with direct inbound dialing. Many offer unlimited domestic calling and sometimes international calls for a flat monthly subscription fee. Phone calls between subscribers of the same provider are usually free when flat-fee service is not available.
A VoIP phone is necessary to connect to a VoIP service provider. This can be implemented in several ways:
- Dedicated VoIP phones connect directly to the IP network using technologies such as wired Ethernet or Wi-Fi. These are typically designed in the style of traditional digital business telephones.
- An analog telephone adapter connects to the network and implements the electronics and firmware to operate a conventional analog telephone attached through a modular phone jack. Some residential Internet gateways and cablemodems have this function built in.
- Softphone application software installed on a networked computer that is equipped with a microphone and speaker, or headset. The application typically presents a dial pad and display field to the user to operate the application by mouse clicks or keyboard input.
PSTN and mobile network providers
It is increasingly common for telecommunications providers to use VoIP telephony over dedicated and public IP networks as a backhaul to connect switching centers and to interconnect with other telephony network providers; this is often referred to as IP backhaul.
Because of the bandwidth efficiency and low costs that VoIP technology can provide, businesses are migrating from traditional copper-wire telephone systems to VoIP systems to reduce their monthly phone costs. In 2008, 80% of all new Private branch exchange (PBX) lines installed internationally were VoIP. For example, in the United States, the Social Security Administration is converting its field offices of 63,000 workers from traditional phone installations to a VoIP infrastructure carried over its existing data network.
VoIP allows both voice and data communications to be run over a single network, which can significantly reduce infrastructure costs. The prices of extensions on VoIP are lower than for PBX and key systems. VoIP switches may run on commodity hardware, such as personal computers. Rather than closed architectures, these devices rely on standard interfaces. VoIP devices have simple, intuitive user interfaces, so users can often make simple system configuration changes. Dual-mode phones enable users to continue their conversations as they move between an outside cellular service and an internal Wi-Fi network, so that it is no longer necessary to carry both a desktop phone and a cell phone. Maintenance becomes simpler as there are fewer devices to oversee.
VoIP solutions aimed at businesses have evolved into unified communications services that treat all communications—phone calls, faxes, voice mail, e-mail, web conferences, and more—as discrete units that can all be delivered via any means and to any handset, including cellphones. Two kinds of service providers are operating in this space: one set is focused on VoIP for medium to large enterprises, while another is targeting the small-to-medium business (SMB) market.
Skype, which originally marketed itself as a service among friends, has begun to cater to businesses, providing free-of-charge connections between any users on the Skype network and connecting to and from ordinary PSTN telephones for a charge.
In general, the provision of VoIP telephony systems to organisational or individual users can be divided into two primary delivery methods: private or on-premises solutions, or externally hosted solutions delivered by third-party providers. On-premises delivery methods are more akin to the classic PBX deployment model for connecting an office to local PSTN networks.
While many use cases still remain for private or on-premises VoIP systems, the wider market has been gradually shifting toward 'Cloud' or Hosted' VoIP solutions. Hosted systems are also generally better suited to smaller or personal use VoIP deployments, where a private system may not be viable for these scenarios.
Hosted VoIP Systems
As with any other SaaS (Software as a Service) solution, 'Hosted' or 'Cloud' VoIP solutions involve a service provider or telecommunications carrier hosting the prerequisite telephone system as a software solution within their own infrastructure.
Typically this will be one or more datacentres, with geographic relevance to the end user(s) of the system. This infrastructure is external to the user of the system, and is deployed and maintained by the service provider.
Endpoints, such as VoIP telephones or softphone applications (apps running on a computer or mobile device), will therefore connect to the VoIP service remotely. These connections typically take place over public internet links, such as local fixed WAN breakout or mobile carrier service (such as 4G).
Private VoIP Systems
In the case of a private VoIP system, the primary telephony system itself is located within the private infrastructure of the end user organisation. Usually, the system will be deployed on-premises at a site within the direct control of the organisation. This can provide numerous benefits in terms of QoS control (see below), cost scalability, and ensuring privacy and security of communications traffic. However, the responsibility for ensuring that the VoIP system remains performant and resilient is predominantly vested in the end user organisation. This is not the case with a Hosted VoIP solution.
Private VoIP systems can be physical hardware PBX appliances, converged with other infrastructure, or they can be deployed as software applications. Generally the latter two options will be in the form of a separate virtualised appliance. However in some scenarios, these systems are deployed on bare metal infrastructure or IoT devices. With some solutions, such as 3CX, companies can attempt to blend the benefits of hosted and private on-premises systems by implementing their own private solution but within an external environment. Examples can include datacentre collocation services, public cloud, or private cloud locations.
For on-premises systems, local endpoints within the same location typically connect directly over the LAN. For remote and external endpoints, available connectivity options mirror those of Hosted or Cloud VoIP solutions.
However, VoIP traffic to and from the on-premises systems can often also be sent over secure private links. Examples include personal VPN, site-to-site VPN, private networks such as MPLS and SD-WAN, or via private SBCs (Session Border Controllers). While exceptions and private peering options do exist, it is generally uncommon for those private connectivity methods to be provided by Hosted or Cloud VoIP providers.
Quality of service
Communication on the IP network is perceived as less reliable in contrast to the circuit-switched public telephone network because it does not provide a network-based mechanism to ensure that data packets are not lost, and are delivered in sequential order. It is a best-effort network without fundamental Quality of Service (QoS) guarantees. Voice, and all other data, travels in packets over IP networks with fixed maximum capacity. This system may be more prone to data loss in the presence of congestion[a] than traditional circuit switched systems; a circuit switched system of insufficient capacity will refuse new connections while carrying the remainder without impairment, while the quality of real-time data such as telephone conversations on packet-switched networks degrades dramatically. Therefore, VoIP implementations may face problems with latency, packet loss, and jitter.
By default, network routers handle traffic on a first-come, first-served basis. Fixed delays cannot be controlled as they are caused by the physical distance the packets travel. They are especially problematic when satellite circuits are involved because of the long distance to a geostationary satellite and back; delays of 400–600 ms are typical. Latency can be minimized by marking voice packets as being delay-sensitive with QoS methods such as DiffServ.
Network routers on high volume traffic links may introduce latency that exceeds permissible thresholds for VoIP. Excessive load on a link can cause congestion and associated queueing delays and packet loss. This signals a transport protocol like TCP to reduce its transmission rate to alleviate the congestion. But VoIP usually uses UDP not TCP because recovering from congestion through retransmission usually entails too much latency. So QoS mechanisms can avoid the undesirable loss of VoIP packets by immediately transmitting them ahead of any queued bulk traffic on the same link, even when the link is congested by bulk traffic.
VoIP endpoints usually have to wait for completion of transmission of previous packets before new data may be sent. Although it is possible to preempt (abort) a less important packet in mid-transmission, this is not commonly done, especially on high-speed links where transmission times are short even for maximum-sized packets. An alternative to preemption on slower links, such as dialup and digital subscriber line (DSL), is to reduce the maximum transmission time by reducing the maximum transmission unit. But since every packet must contain protocol headers, this increases relative header overhead on every link traversed.
The receiver must resequence IP packets that arrive out of order and recover gracefully when packets arrive too late or not at all. Packet delay variation results from changes in queuing delay along a given network path due to competition from other users for the same transmission links. VoIP receivers accommodate this variation by storing incoming packets briefly in a playout buffer, deliberately increasing latency to improve the chance that each packet will be on hand when it is time for the voice engine to play it. The added delay is thus a compromise between excessive latency and excessive dropout, i.e. momentary audio interruptions.
Although jitter is a random variable, it is the sum of several other random variables which are at least somewhat independent: the individual queuing delays of the routers along the Internet path in question. Motivated by the central limit theorem, jitter can be modeled as a gaussian random variable. This suggests continually estimating the mean delay and its standard deviation and setting the playout delay so that only packets delayed more than several standard deviations above the mean will arrive too late to be useful. In practice, the variance in latency of many Internet paths is dominated by a small number (often one) of relatively slow and congested bottleneck links. Most Internet backbone links are now so fast (e.g. 10 Gbit/s) that their delays are dominated by the transmission medium (e.g. optical fiber) and the routers driving them do not have enough buffering for queuing delays to be significant.
A number of protocols have been defined to support the reporting of quality of service (QoS) and quality of experience (QoE) for VoIP calls. These include RTP Control Protocol (RTCP) extended reports, SIP RTCP summary reports, H.460.9 Annex B (for H.323), H.248.30 and MGCP extensions.
The RTCP extended report VoIP metrics block specified by RFC 3611 is generated by an IP phone or gateway during a live call and contains information on packet loss rate, packet discard rate (because of jitter), packet loss/discard burst metrics (burst length/density, gap length/density), network delay, end system delay, signal/noise/echo level, mean opinion scores (MOS) and R factors and configuration information related to the jitter buffer. VoIP metrics reports are exchanged between IP endpoints on an occasional basis during a call, and an end of call message sent via SIP RTCP summary report or one of the other signaling protocol extensions. VoIP metrics reports are intended to support real-time feedback related to QoS problems, the exchange of information between the endpoints for improved call quality calculation and a variety of other applications.
DSL and ATM
DSL modems typically provide Ethernet connections to local equipment, but inside they may actually be Asynchronous Transfer Mode (ATM) modems.[b] They use ATM Adaptation Layer 5 (AAL5) to segment each Ethernet packet into a series of 53-byte ATM cells for transmission, reassembling them back into Ethernet frames at the receiving end.
Using a separate virtual circuit identifier (VCI) for audio over IP has the potential to reduce latency on shared connections. ATM's potential for latency reduction is greatest on slow links, because worst-case latency decreases with increasing link speed. A full-size (1500 byte) Ethernet frame takes 94 ms to transmit at 128 kbit/s but only 8 ms at 1.5 Mbit/s. If this is the bottleneck link, this latency is probably small enough to ensure good VoIP performance without MTU reductions or multiple ATM VCs. The latest generations of DSL, VDSL and VDSL2, carry Ethernet without intermediate ATM/AAL5 layers, and they generally support IEEE 802.1p priority tagging so that VoIP can be queued ahead of less time-critical traffic.
ATM has substantial header overhead: 5/53 = 9.4%, roughly twice the total header overhead of a 1500 byte Ethernet frame. This "ATM tax" is incurred by every DSL user whether or not they take advantage of multiple virtual circuits – and few can.
Several protocols are used in the data link layer and physical layer for quality-of-service mechanisms that help VoIP applications work well even in the presence of network congestion. Some examples include:
- IEEE 802.11e is an approved amendment to the IEEE 802.11 standard that defines a set of quality-of-service enhancements for wireless LAN applications through modifications to the Media Access Control (MAC) layer. The standard is considered of critical importance for delay-sensitive applications, such as voice over wireless IP.
- IEEE 802.1p defines 8 different classes of service (including one dedicated to voice) for traffic on layer-2 wired Ethernet.
- The ITU-T G.hn standard, which provides a way to create a high-speed (up to 1 gigabit per second) Local area network (LAN) using existing home wiring (power lines, phone lines and coaxial cables). G.hn provides QoS by means of Contention-Free Transmission Opportunities (CFTXOPs) which are allocated to flows (such as a VoIP call) which require QoS and which have negotiated a contract with the network controllers.
The quality of voice transmission is characterized by several metrics that may be monitored by network elements and by the user agent hardware or software. Such metrics include network packet loss, packet jitter, packet latency (delay), post-dial delay, and echo. The metrics are determined by VoIP performance testing and monitoring.
This section needs additional citations for verification. (November 2019) (Learn how and when to remove this template message)
A VoIP media gateway controller (aka Class 5 Softswitch) works in cooperation with a media gateway (aka IP Business Gateway) and connects the digital media stream, so as to complete the path for voice and data. Gateways include interfaces for connecting to standard PSTN networks. Ethernet interfaces are also included in the modern systems which are specially designed to link calls that are passed via VoIP.
E.164 is a global numbering standard for both the PSTN and public land mobile network (PLMN). Most VoIP implementations support E.164 to allow calls to be routed to and from VoIP subscribers and the PSTN/PLMN. VoIP implementations can also allow other identification techniques to be used. For example, Skype allows subscribers to choose Skype names (usernames) whereas SIP implementations can use Uniform Resource Identifier (URIs) similar to email addresses. Often VoIP implementations employ methods of translating non-E.164 identifiers to E.164 numbers and vice versa, such as the Skype-In service provided by Skype and the E.164 number to URI mapping (ENUM) service in IMS and SIP.
Echo can also be an issue for PSTN integration. Common causes of echo include impedance mismatches in analog circuitry and acoustic coupling of the transmit and receive signal at the receiving end.
Local number portability (LNP) and mobile number portability (MNP) also impact VoIP business. In November 2007, the Federal Communications Commission in the United States released an order extending number portability obligations to interconnected VoIP providers and carriers that support VoIP providers. Number portability is a service that allows a subscriber to select a new telephone carrier without requiring a new number to be issued. Typically, it is the responsibility of the former carrier to "map" the old number to the undisclosed number assigned by the new carrier. This is achieved by maintaining a database of numbers. A dialed number is initially received by the original carrier and quickly rerouted to the new carrier. Multiple porting references must be maintained even if the subscriber returns to the original carrier. The FCC mandates carrier compliance with these consumer-protection stipulations.
A voice call originating in the VoIP environment also faces challenges to reach its destination if the number is routed to a mobile phone number on a traditional mobile carrier. VoIP has been identified in the past as a Least Cost Routing (LCR) system, which is based on checking the destination of each telephone call as it is made, and then sending the call via the network that will cost the customer the least. This rating is subject to some debate given the complexity of call routing created by number portability. With GSM number portability now in place, LCR providers can no longer rely on using the network root prefix to determine how to route a call. Instead, they must now determine the actual network of every number before routing the call.
Therefore, VoIP solutions also need to handle MNP when routing a voice call. In countries without a central database, like the UK, it might be necessary to query the GSM network about which home network a mobile phone number belongs to. As the popularity of VoIP increases in the enterprise markets because of least cost routing options, it needs to provide a certain level of reliability when handling calls.
A telephone connected to a land line has a direct relationship between a telephone number and a physical location, which is maintained by the telephone company and available to emergency responders via the national emergency response service centers in form of emergency subscriber lists. When an emergency call is received by a center the location is automatically determined from its databases and displayed on the operator console.
In IP telephony, no such direct link between location and communications end point exists. Even a provider having hardware infrastructure, such as a DSL provider, may know only the approximate location of the device, based on the IP address allocated to the network router and the known service address. Some ISPs do not track the automatic assignment of IP addresses to customer equipment.
IP communication provides for device mobility. For example, a residential broadband connection may be used as a link to a virtual private network of a corporate entity, in which case the IP address being used for customer communications may belong to the enterprise, not being the IP address of the residential ISP. Such off-premises extensions may appear as part of an upstream IP PBX. On mobile devices, e.g., a 3G handset or USB wireless broadband adapter, the IP address has no relationship with any physical location known to the telephony service provider, since a mobile user could be anywhere in a region with network coverage, even roaming via another cellular company.
At the VoIP level, a phone or gateway may identify itself with a Session Initiation Protocol (SIP) registrar by its account credentials. In such cases, the Internet telephony service provider (ITSP) knows only that a particular user's equipment is active. Service providers often provide emergency response services by agreement with the user who registers a physical location and agrees that emergency services are provided to that address only if an emergency number is called from the IP device.
Such emergency services are provided by VoIP vendors in the United States by a system called Enhanced 911 (E911), based on the Wireless Communications and Public Safety Act of 1999. The VoIP E911 emergency-calling system associates a physical address with the calling party's telephone number. All VoIP providers that provide access to the public switched telephone network are required to implement E911, a service for which the subscriber may be charged. "VoIP providers may not allow customers to "opt-out" of 911 service."
The VoIP E911 system is based on a static table lookup. Unlike in cellular phones, where the location of an E911 call can be traced using assisted GPS or other methods, the VoIP E911 information is accurate only if subscribers, who have the legal responsibility, keep their emergency address information current.
Sending faxes over VoIP networks is sometimes referred to as Fax over IP (FoIP). Transmission of fax documents was problematic in early VoIP implementations, as most voice digitization and compression codecs are optimized for the representation of the human voice and the proper timing of the modem signals cannot be guaranteed in a packet-based, connection-less network. A standards-based solution for reliably delivering fax-over-IP is the T.38 protocol.
The T.38 protocol is designed to compensate for the differences between traditional packet-less communications over analog lines and packet-based transmissions which are the basis for IP communications. The fax machine may be a standard device connected to an analog telephone adapter (ATA), or it may be a software application or dedicated network device operating via an Ethernet interface. Originally, T.38 was designed to use UDP or TCP transmission methods across an IP network. UDP provides near real-time characteristics due to the "no recovery rule" when a UDP packet is lost or an error occurs during transmission.
Some newer high end fax machines have built-in T.38 capabilities which are connected directly to a network switch or router. In T.38 each packet contains a portion of the data stream sent in the previous packet. Two successive packets have to be lost to actually lose data integrity.
Telephones for traditional residential analog service are usually connected directly to telephone company phone lines which provide direct current to power most basic analog handsets independently of locally available electrical power.
IP Phones and VoIP telephone adapters connect to routers or cable modems which typically depend on the availability of mains electricity or locally generated power. Some VoIP service providers use customer premises equipment (e.g., cablemodems) with battery-backed power supplies to assure uninterrupted service for up to several hours in case of local power failures. Such battery-backed devices typically are designed for use with analog handsets.
Some VoIP service providers implement services to route calls to other telephone services of the subscriber, such a cellular phone, in the event that the customer's network device is inaccessible to terminate the call.
The susceptibility of phone service to power failures is a common problem even with traditional analog service in areas where many customers purchase modern telephone units that operate with wireless handsets to a base station, or that have other modern phone features, such as built-in voicemail or phone book features.
The security concerns of VoIP telephone systems are similar to those of other Internet-connected devices. This means that hackers with knowledge of VoIP vulnerabilities can perform denial-of-service attacks, harvest customer data, record conversations, and compromise voicemail messages. Compromised VoIP user account or session credentials may enable an attacker to incur substantial charges from third-party services, such as long-distance or international calling.
The technical details of many VoIP protocols create challenges in routing VoIP traffic through firewalls and network address translators, used to interconnect to transit networks or the Internet. Private session border controllers are often employed to enable VoIP calls to and from protected networks. Other methods to traverse NAT devices involve assistive protocols such as STUN and Interactive Connectivity Establishment (ICE).
Though many consumer VoIP solutions do not support encryption of the signaling path or the media, securing a VoIP phone is conceptually easier to implement than on traditional telephone circuits. A result of the lack of encryption is that it is relatively easy to eavesdrop on VoIP calls when access to the data network is possible. Free open-source solutions, such as Wireshark, facilitate capturing VoIP conversations.
Standards for securing VoIP are available in the Secure Real-time Transport Protocol (SRTP) and the ZRTP protocol for analog telephony adapters, as well as for some softphones. IPsec is available to secure point-to-point VoIP at the transport level by using opportunistic encryption.
Government and military organizations use various security measures to protect VoIP traffic, such as voice over secure IP (VoSIP), secure voice over IP (SVoIP), and secure voice over secure IP (SVoSIP). The distinction lies in whether encryption is applied in the telephone endpoint or in the network. Secure voice over secure IP may be implemented by encrypting the media with protocols such as SRTP and ZRTP. Secure voice over IP uses Type 1 encryption on a classified network, such as SIPRNet. Public Secure VoIP is also available with free GNU software and in many popular commercial VoIP programs via libraries, such as ZRTP.
Hearing aid compatibility
Wireline telephones which are manufactured in, imported to, or intended to be used in the US with Voice over IP service, on or after February 28, 2020, are required to meet the hearing aid compatibility requirements set forth by the Federal Communications Commission.
VoIP has drastically reduced the cost of communication by sharing network infrastructure between data and voice. A single broad-band connection has the ability to transmit more than one telephone call. Secure calls using standardized protocols, such as Secure Real-time Transport Protocol, as most of the facilities of creating a secure telephone connection over traditional phone lines, such as digitizing and digital transmission, are already in place with VoIP. It is necessary only to encrypt and authenticate the existing data stream. Automated software, such as a virtual PBX, may eliminate the need of personnel to greet and switch incoming calls.
Regulatory and legal issues
As the popularity of VoIP grows, governments are becoming more interested in regulating VoIP in a manner similar to PSTN services.
Throughout the developing world, particularly in countries where regulation is weak or captured by the dominant operator, restrictions on the use of VoIP are often imposed, including in Panama where VoIP is taxed, Guyana where VoIP is prohibited. In Ethiopia, where the government is nationalising telecommunication service, it is a criminal offence to offer services using VoIP. The country has installed firewalls to prevent international calls being made using VoIP. These measures were taken after the popularity of VoIP reduced the income generated by the state owned telecommunication company.
In Canada, the Canadian Radio-television and Telecommunications Commission regulates telephone service, including VoIP telephony service. VoIP services operating in Canada are required to provide 9-1-1 emergency service.
This section needs to be updated.September 2013)(
In the European Union, the treatment of VoIP service providers is a decision for each national telecommunications regulator, which must use competition law to define relevant national markets and then determine whether any service provider on those national markets has "significant market power" (and so should be subject to certain obligations). A general distinction is usually made between VoIP services that function over managed networks (via broadband connections) and VoIP services that function over unmanaged networks (essentially, the Internet).
The relevant EU Directive is not clearly drafted concerning obligations which can exist independently of market power (e.g., the obligation to offer access to emergency calls), and it is impossible to say definitively whether VoIP service providers of either type are bound by them. A review of the EU Directive is under way and should be complete by 2007.
In Oman, it is illegal to provide or use unauthorized VoIP services, to the extent that web sites of unlicensed VoIP providers have been blocked. Violations may be punished with fines of 50,000 Omani Rial (about 130,317 US dollars), a two year prison sentence or both. In 2009, police raided 121 Internet cafes throughout the country and arrested 212 people for using or providing VoIP services.
United Arab Emirates
In the United Arab Emirates (UAE), it is illegal to provide or use unauthorized VoIP services, to the extent that web sites of unlicensed VoIP providers have been blocked. However, some VoIPs such as Skype were allowed. In January 2018, internet service providers in UAE blocked all VoIP apps, including Skype, but permitting only 2 "government-approved" VoIP apps (C’ME and BOTIM) for a fixed rate of Dh52.50 a month for use on mobile devices, and Dh105 a month to use over a computer connected." In opposition, a petition on Change.org garnered over 5000 signatures, in response to which the website was blocked in UAE.
On 24 March 2020, the United Arab Emirates loosened restriction on VoIP services earlier prohibited in the country, to ease communication during the COVID-19 pandemic. However, popular instant messaging applications like WhatsApp, Skype, and FaceTime remained blocked from being used for voice and video calls, constricting residents to use paid services from the country’s state-owned telecom providers.
In India, it is legal to use VoIP, but it is illegal to have VoIP gateways inside India. This effectively means that people who have PCs can use them to make a VoIP call to any number, but if the remote side is a normal phone, the gateway that converts the VoIP call to a POTS call is not permitted by law to be inside India. Foreign based VoIP server services are illegal to use in India.
In the interest of the Access Service Providers and International Long Distance Operators the Internet telephony was permitted to the ISP with restrictions. Internet Telephony is considered to be different service in its scope, nature and kind from real time voice as offered by other Access Service Providers and Long Distance Carriers. Hence the following type of Internet Telephony are permitted in India:
- (a) PC to PC; within or outside India
(b) PC / a device / Adapter conforming to standard of any international agencies like- ITU or IETF etc. in India to PSTN/PLMN abroad.
(c) Any device / Adapter conforming to standards of International agencies like ITU, IETF etc. connected to ISP node with static IP address to similar device / Adapter; within or outside India.
(d) Except whatever is described in [clarification needed], no other form of Internet Telephony is permitted.
(e) In India no Separate Numbering Scheme is provided to the Internet Telephony. Presently the 10 digit Numbering allocation based on E.164 is permitted to the Fixed Telephony, GSM, CDMA wireless service. For Internet Telephony the numbering scheme shall only conform to IP addressing Scheme of Internet Assigned Numbers Authority (IANA). Translation of E.164 number / private number to IP address allotted to any device and vice versa, by ISP to show compliance with IANA numbering scheme is not permitted.
(f) The Internet Service Licensee is not permitted to have PSTN/PLMN connectivity. Voice communication to and from a telephone connected to PSTN/PLMN and following E.164 numbering is prohibited in India.
In South Korea, only providers registered with the government are authorized to offer VoIP services. Unlike many VoIP providers, most of whom offer flat rates, Korean VoIP services are generally metered and charged at rates similar to terrestrial calling. Foreign VoIP providers encounter high barriers to government registration. This issue came to a head in 2006 when Internet service providers providing personal Internet services by contract to United States Forces Korea members residing on USFK bases threatened to block off access to VoIP services used by USFK members as an economical way to keep in contact with their families in the United States, on the grounds that the service members' VoIP providers were not registered. A compromise was reached between USFK and Korean telecommunications officials in January 2007, wherein USFK service members arriving in Korea before June 1, 2007, and subscribing to the ISP services provided on base may continue to use their US-based VoIP subscription, but later arrivals must use a Korean-based VoIP provider, which by contract will offer pricing similar to the flat rates offered by US VoIP providers.
In the United States, the Federal Communications Commission requires all interconnected VoIP service providers to comply with requirements comparable to those for traditional telecommunications service providers. VoIP operators in the US are required to support local number portability; make service accessible to people with disabilities; pay regulatory fees, universal service contributions, and other mandated payments; and enable law enforcement authorities to conduct surveillance pursuant to the Communications Assistance for Law Enforcement Act (CALEA).
Operators of "Interconnected" VoIP (fully connected to the PSTN) are mandated to provide Enhanced 911 service without special request, provide for customer location updates, clearly disclose any limitations on their E-911 functionality to their consumers, obtain affirmative acknowledgements of these disclosures from all consumers, and 'may not allow their customers to “opt-out” of 911 service.' VoIP operators also receive the benefit of certain US telecommunications regulations, including an entitlement to interconnection and exchange of traffic with incumbent local exchange carriers via wholesale carriers. Providers of "nomadic" VoIP service—those who are unable to determine the location of their users—are exempt from state telecommunications regulation.
Another legal issue that the US Congress is debating concerns changes to the Foreign Intelligence Surveillance Act. The issue in question is calls between Americans and foreigners. The National Security Agency (NSA) is not authorized to tap Americans' conversations without a warrant—but the Internet, and specifically VoIP does not draw as clear a line to the location of a caller or a call's recipient as the traditional phone system does. As VoIP's low cost and flexibility convinces more and more organizations to adopt the technology, the surveillance for law enforcement agencies becomes more difficult. VoIP technology has also increased Federal security concerns because VoIP and similar technologies have made it more difficult for the government to determine where a target is physically located when communications are being intercepted, and that creates a whole set of new legal challenges.
The early developments of packet network designs by Paul Baran and other researchers were motivated by a desire for a higher degree of circuit redundancy and network availability in the face of infrastructure failures than was possible in the circuit-switched networks in telecommunications of the mid-twentieth century. Danny Cohen first demonstrated a form of packet voice in 1973 as part of a flight simulator application, which operated across the early ARPANET.
On the early ARPANET, real-time voice communication was not possible with uncompressed pulse-code modulation (PCM) digital speech packets, which had a bit rate of 64 kbps, much greater than the 2.4 kbps bandwidth of early modems. The solution to this problem was linear predictive coding (LPC), a speech coding data compression algorithm that was first proposed by Fumitada Itakura of Nagoya University and Shuzo Saito of Nippon Telegraph and Telephone (NTT) in 1966. LPC was capable of speech compression down to 2.4 kbps, leading to the first successful real-time conversation over ARPANET in 1974, between Culler-Harrison Incorporated in Goleta, California, and MIT Lincoln Laboratory in Lexington, Massachusetts. LPC has since been the most widely used speech coding method. Code-excited linear prediction (CELP), a type of LPC algorithm, was developed by Manfred R. Schroeder and Bishnu S. Atal in 1985. LPC algorithms remain an audio coding standard in modern VoIP technology.
In the following time span of about two decades, various forms of packet telephony were developed and industry interest groups formed to support the new technologies. Following the termination of the ARPANET project, and expansion of the Internet for commercial traffic, IP telephony was tested and deemed infeasible for commercial use until the introduction of VocalChat in the early 1990s and then in Feb 1995 the official release of Internet Phone (or iPhone for short) commercial software by VocalTec , based on the Audio Transceiver patent by Lior Haramaty and Alon Cohen, and followed by other VoIP infrastructure components such as telephony gateways and switching servers. Soon after it became an established area of interest in commercial labs of the major IT concerns. By the late 1990s, the first softswitches became available, and new protocols, such as H.323, MGCP and the Session Initiation Protocol (SIP) gained widespread attention. In the early 2000s, the proliferation of high-bandwidth always-on Internet connections to residential dwellings and businesses, spawned an industry of Internet telephony service providers (ITSPs). The development of open-source telephony software, such as Asterisk PBX, fueled widespread interest and entrepreneurship in voice-over-IP services, applying new Internet technology paradigms, such as cloud services to telephony.
In 1999, a discrete cosine transform (DCT) audio data compression algorithm called the modified discrete cosine transform (MDCT) was adopted for the Siren codec, used in the G.722.1 wideband audio coding standard. The same year, the MDCT was adapted into the LD-MDCT speech coding algorithm, used for the AAC-LD format and intended for significantly improved audio quality in VoIP applications. MDCT has since been widely used in VoIP applications, such as the G.729.1 wideband codec introduced in 2006, Apple's Facetime (using AAC-LD) introduced in 2010, the CELT codec introduced in 2011, the Opus codec introduced in 2012, and WhatsApp's voice calling feature introduced in 2015.
- 1966: Linear predictive coding (LPC) proposed by Fumitada Itakura of Nagoya University and Shuzo Saito of Nippon Telegraph and Telephone (NTT).
- 1973: Packet voice application by Danny Cohen.
- 1974: The Institute of Electrical and Electronics Engineers (IEEE) publishes a paper entitled "A Protocol for Packet Network Interconnection".
- 1974: Network Voice Protocol (NVP) tested over ARPANET in August 1974, carrying barely audible 16 kpbs CVSD encoded voice.
- 1974: The first successful real-time conversation over ARPANET achieved using 2.4 kpbs LPC, between Culler-Harrison Incorporated in Goleta, California, and MIT Lincoln Laboratory in Lexington, Massachusetts.
- 1977: Danny Cohen and Jon Postel of the USC Information Sciences Institute, and Vint Cerf of the Defense Advanced Research Projects Agency (DARPA), agree to separate IP from TCP, and create UDP for carrying real-time traffic.
- 1981: IPv4 is described in RFC 791.
- 1985: The National Science Foundation commissions the creation of NSFNET.
- 1985: Code-excited linear prediction (CELP), a type of LPC algorithm, developed by Manfred R. Schroeder and Bishnu S. Atal.
- 1986: Proposals from various standards organizations[specify] for Voice over ATM, in addition to commercial packet voice products from companies such as StrataCom
- 1991: First Voice-over-IP application, Speak Freely, is released into the public domain. It was originally written by John Walker and further developed by Brian C. Wiles.
- 1992: The Frame Relay Forum conducts development of standards for Voice over Frame Relay.
- 1992: InSoft Inc. announces and launches its desktop conferencing product Communique, which included VoIP and video. The company is credited with developing the first generation of commercial, US-based VoIP, Internet media streaming and real-time Internet telephony/collaborative software and standards that would provide the basis for the Real Time Streaming Protocol (RTSP) standard.
- 1993 Release of VocalChat, a commercial packet network PC voice communication software from VocalTec.
- 1994: MTALK, a freeware LAN VoIP application for Linux
- 1995: VocalTec releases Internet Phone commercial Internet phone software.
- ITU-T begins development of standards for the transmission and signaling of voice communications over Internet Protocol networks with the H.323 standard.
- US telecommunication companies petition the US Congress to ban Internet phone technology.
- G.729 speech codec introduced, using CELP (LPC) algorithm.
- 1997: Level 3 began development of its first softswitch, a term they coined in 1998.
- The Session Initiation Protocol (SIP) specification RFC 2543 is released.
- Mark Spencer of Digium develops the first open source private branch exchange (PBX) software (Asterisk).
- A discrete cosine transform (DCT) variant called the modified discrete cosine transform (MDCT) is adopted for the Siren codec, used in the G.722.1 wideband audio coding standard.
- The MDCT is adapted into the LD-MDCT algorithm, used in the AAC-LD standard.
- 2004: Commercial VoIP service providers proliferate.
- 2006: G.729.1 wideband codec introduced, using MDCT and CELP (LPC) algorithms.
- 2007: VoIP device manufacturers and sellers boom in Asia, specifically in the Philippines where many families of overseas workers reside.
- 2009: SILK codec introduced, using LPC algorithm, and used for voice calling in Skype.
- 2010: Apple introduces FaceTime, which uses the LD-MDCT-based AAC-LD codec.
- 2012: Opus codec introduced, using MDCT and LPC algorithms.
- Audio over IP
- Communications Assistance For Law Enforcement Act
- Comparison of audio network protocols
- Comparison of VoIP software
- Differentiated services
- High bit rate audio video over Internet Protocol
- Integrated services
- Internet fax
- IP Multimedia Subsystem
- List of VoIP companies
- Mobile VoIP
- Network Voice Protocol
- RTP audio video profile
- SIP Trunking
- Voice VPN
- VoIP recording
- "XMPP Federation". Google Talkabout. 2006. Retrieved May 11, 2012.
- Booth, C (2010). "Chapter 2: IP Phones, Software VoIP, and Integrated and Mobile VoIP". Library Technology Reports. 46 (5): 11–19.
- "VoIP". Cambridge Dictionaries Online.
- "H.323 and SIP Integration". Retrieved January 24, 2020.
- "WIRELESS: Carriers look to IP for backhaul". www.eetimes.com. EE Times. Archived from the original on August 9, 2011. Retrieved April 8, 2015.CS1 maint: unfit url (link)
- "Mobile's IP challenge". www.totaltele.com. Total Telecom Online. Archived from the original on February 17, 2006. Retrieved April 8, 2015.CS1 maint: unfit url (link)
- "Android SIP Client". Retrieved January 30, 2018.
- "Learn to Make Free or Inexpensive Calls Using SIP on Android". Retrieved January 30, 2018.
- Michael Dosch and Steve Church. "VoIP in the Broadcast Studio". Axia Audio. Archived from the original on October 7, 2011. Retrieved June 21, 2011.
- Jackson, William (May 27, 2009). "SSA goes big on VOIP". Government Computer News. Retrieved May 28, 2009.
- "Social Security to Build "World's Largest VOIP"". Government Technology. Archived from the original on June 2, 2009. Retrieved May 29, 2009.
- Korzeniowski, Peter (January 8, 2009). "Three Technologies You Need In 2009". Forbes. Retrieved March 2, 2009.
- Callahan, Renee (December 9, 2008). "Businesses Move To Voice-Over-IP". Forbes. Retrieved March 3, 2009.
- "Skype For Business". skype.com. Retrieved March 16, 2009.
- "VoIP– Vulnerability over Internet Protocol?".
- "Quality of Service for Voice over IP". Retrieved May 3, 2011.
- Prabhakar, G.; Rastogi, R.; Thotton, M (2005). "OSS Architecture & Requirements for VoIP Networks". Bell Labs Technical Journal. 10 (1): 31–45. doi:10.1002/bltj.20077. S2CID 12336090.
- "Quality of Service for Voice over IP". Retrieved May 3, 2011.
- Caceres, Ramon. RTP Control Protocol Extended Reports (RTCP XR). doi:10.17487/RFC3611. RFC 3611.
- CableLabs, PacketCable Residential SIP Telephony Feature Definition, Technical Report, PKT-TR-RST-V03-071106 (2007)
- "VoIP performance measurement using QoS parameters" (PDF). A.H.Muhamad Amin. August 14, 2016.
- "Methodology for SIP Infrastructure Performance Testing" (PDF). Miroslav Voznak, Jan Rozhon. August 14, 2016.
- "Voice over IP (VoIP) Performance Evaluation on VMware vSphere® 5" (PDF). VMware. August 14, 2016.
- "Performance and Stress Testing of SIP Servers, Clients and IP Networks". StarTrinity. August 13, 2016.
- "Testing Voice over IP (VolP) Networks" (PDF). IXIA. August 14, 2016.
- "Importance of Softswitch VoIP Technology". ixc.ua. May 20, 2011. Archived from the original on November 26, 2012.
- "RFC 3824– Using E.164 numbers with the Session Initiation Protocol (SIP)". The Internet Society. June 1, 2004. Retrieved January 21, 2009.
- "Create a Skype Name". Skype. Retrieved January 21, 2009.
- "RFC 3969– The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)". The Internet Society. December 1, 2004. Retrieved January 21, 2009.
- "Your personal online number". Skype. Retrieved January 21, 2009.
- "Application-level Network Interoperability and the Evolution of IMS". TMCnet.com. May 24, 2006. Retrieved January 21, 2009.
- Jeff Riddel (2007). Packetcable Implementation. Cisco Press. p. 557. ISBN 978-1-58705-181-4.
- "Keeping your telephone number when you change your service provider". FCC.
- "FCC Consumer Advisory VoIP and 911 Service" (PDF). Retrieved May 2, 2011.
- Soft-Switch.org, Faxing over IP networks
- "UMass Discussion on UDP transmission Characteristics".
- "ICT Regulation Tool Kit – 4.4 VOIP – Regulatory Issues – Universal Service". Retrieved September 21, 2017.
- "Examining Two Well-Known Attacks on VoIP". CircleID. Retrieved April 5, 2006.
- Disa.mil, Internet Protocol Telephony & Voice over Internet Protocol Security Technical Implementation Guide
- Secure Voice over IP (SVoIP) vs. Voice over Secure IP (VoSIP) Installations General Dynamics C4 Systems
- Dunte, Markus; Ruland, Christoph (June 2007). "Secure Voice-over-IP" (PDF). International Journal of Computer Science and Network Security. 7 (6): 63–68.
- Sans.org, SANS Institute InfoSec Reading Room
- White, C.M.; Teague, K.A.; Daniel, E.J. (November 7–10, 2004). Browse Conference Publications > Signals, Systems and Computer ... Help Working with Abstracts Packet loss concealment in a secure voice over IP environment (PDF). Signals, Systems and Computers, 2004. Conference Record of the Thirty-Eighth Asilomar Conference on. 1. pp. 415–419. CiteSeerX 10.1.1.219.633. doi:10.1109/ACSSC.2004.1399165. ISBN 978-0-7803-8622-8. S2CID 402760.
- "Cellcrypt secure VOIP heading to BlackBerry". Networkworld.com.
- "Secure VOIP calling, free software, and the right to privacy". Free Software Magazine.
- VOIPSA.org, Blog: "Hello Mom, I'm a Fake!" (Telespoof and Fakecaller).
- "Hearing Aid Compatibility for Wireline and Wireless Telephones". Federal Communications Commission. October 30, 2014. Retrieved July 9, 2019.
- FCC.gov, What are some advantages of VoIP?
- "Voip Infrastructure" (PDF).
- "Global VOIP Policy Status Matrix". Global IP Alliance. Retrieved November 23, 2006.
- Proenza, Francisco J. "The Road to Broadband Development in Developing Countries is through Competition Driven by Wireless and VOIP" (PDF). Archived from the original (PDF) on June 2, 2012. Retrieved April 7, 2008.
- "Telecom Decision CRTC 2005-21". Canadian Radio-television and Telecommunications Commission. Government of Canada. April 4, 2005. Retrieved April 29, 2017.
- Metz, Cade. "Oman cuffs 212 for selling VoIP calls". The Register. Retrieved September 20, 2016.
- "Saudi Arabia to lift ban on internet calls". BBC News. September 20, 2017. Retrieved January 10, 2018.
- "Saudi Arabia to lift ban on internet calls". Reuters. September 20, 2017. Retrieved January 10, 2018.
- "Don't worry, Skype is working in UAE". Khaleejtimes. June 26, 2017. Retrieved January 11, 2018.
- Debusmann Jr, Bernd (January 9, 2018). "Etisalat launches new unlimited calling plan with VoIP apps". Arabian Business. Retrieved January 9, 2018.
- Maceda, Cleofe (January 8, 2018). "No Skype? Pay Dh50 monthly for video calls". Gulf News. Retrieved January 9, 2018.
- Zacharias, Anna \ (January 8, 2018). "Etisalat launches new calling app plan days after Skype disruptions". The National. Retrieved January 9, 2018.
- "UAE loosens some VoIP restrictions as residents in lockdown call for end to WhatsApp and Skype ban". CNBC. Retrieved March 26, 2020.
- Mahanagar Doorsanchar Bhawan and Jawahar Lal Nehru Marg (May 2008). "Telecom Regulatory Authority of India (TRAI) Consultation paper on Issues related to Internet Telephony. Consultation Paper No. 11/2008" (PDF). New Delhi India: Telecom Regulatory Authority of India (TRAI). p. 16 (Section 22.214.171.124 PC–to–Phone Internet telephony). Archived from the original (PDF) on October 6, 2014. Retrieved September 19, 2012.
An end user is allowed to make PC–to-Phone Internet Telephony calls only on PSTN/PLMN abroad.
- Harish Kumar Gangwar Technical Note on Illegal International Long Distance telephone Exchange in India
- Stripes.com, Stars and Stripes: USFK deal keeps VoIP access for troops
- Pershing, Genny. "Cybertelecom :: VoIP :: FCC". www.cybertelecom.org. Retrieved September 21, 2017.
- GPO.gov, 47 C.F.R. pt. 9 (2007)
- "VoIP and 911 Service". FCC. Retrieved August 16, 2014.
- "Voice Over Internet Protocol (VoIP)". November 18, 2010. Retrieved September 21, 2017.
- Greenberg, Andy (May 15, 2008). "The State Of Cybersecurity Wiretapping's Fuzzy Future". Forbes. Retrieved March 2, 2009.
- "Danny Cohen". INTERNET HALL of FAME. Retrieved December 6, 2014.
- Advanced Content Delivery, Streaming, and Cloud Services (Pg 34). Willey. September 19, 2014. ISBN 9781118909706. Retrieved December 6, 2014.
- Gray, Robert M. (2010). "A History of Realtime Digital Speech on Packet Networks: Part II of Linear Predictive Coding and the Internet Protocol" (PDF). Found. Trends Signal Process. 3 (4): 203–303. doi:10.1561/2000000036. ISSN 1932-8346.
- Gupta, Shipra (May 2016). "Application of MFCC in Text Independent Speaker Recognition" (PDF). International Journal of Advanced Research in Computer Science and Software Engineering. 6 (5): 805–810 (806). ISSN 2277-128X. S2CID 212485331. Retrieved October 18, 2019.
- M. R. Schroeder and B. S. Atal, "Code-excited linear prediction (CELP): high-quality speech at very low bit rates," in Proceedings of the IEEE International Conference on Acoustics, Speech, and Signal Processing (ICASSP), vol. 10, pp. 937–940, 1985.
- Hersent, Olivier; Petit, Jean-Pierre; Gurle, David (2005). Beyond VoIP Protocols: Understanding Voice Technology and Networking Techniques for IP Telephony. John Wiley & Sons. p. 55. ISBN 9780470023631.
- Lutzky, Manfred; Schuller, Gerald; Gayer, Marc; Krämer, Ulrich; Wabnik, Stefan (May 2004). A guideline to audio codec delay (PDF). 116th AES Convention. Fraunhofer IIS. Audio Engineering Society. Retrieved October 24, 2019.
- Schnell, Markus; Schmidt, Markus; Jander, Manuel; Albert, Tobias; Geiger, Ralf; Ruoppila, Vesa; Ekstrand, Per; Bernhard, Grill (October 2008). MPEG-4 Enhanced Low Delay AAC - A New Standard for High Quality Communication (PDF). 125th AES Convention. Fraunhofer IIS. Audio Engineering Society. Retrieved October 20, 2019.
- Nagireddi, Sivannarayana (2008). VoIP Voice and Fax Signal Processing. John Wiley & Sons. p. 69. ISBN 9780470377864.
- Daniel Eran Dilger (June 8, 2010). "Inside iPhone 4: FaceTime video calling". AppleInsider. Retrieved June 9, 2010.
- Presentation of the CELT codec by Timothy B. Terriberry (65 minutes of video, see also presentation slides in PDF)
- Valin, Jean-Marc; Maxwell, Gregory; Terriberry, Timothy B.; Vos, Koen (October 2013). High-Quality, Low-Delay Music Coding in the Opus Codec. 135th AES Convention. Audio Engineering Society. arXiv:1602.04845.
- Leyden, John (October 27, 2015). "WhatsApp laid bare: Info-sucking app's innards probed". The Register. Retrieved October 19, 2019.
- Cerf, V.; Kahn, R. (May 1974). "A Protocol for Packet Network Intercommunication" (PDF). IEEE Transactions on Communications. 22 (5): 637–648. doi:10.1109/TCOM.1974.1092259.
- "The Launch of NSFNET". The National Science Foundation. Retrieved January 21, 2009.
- "Speak Freely History". Brian C. Wiles. April 18, 1999. Retrieved March 19, 2013.
- IDG Network World Inc; Eckerson, Wayne (September 21, 1992). "Network World - Startup targets desktop Videoconferencing arena". Network World. IDG Network World Inc: 39–. ISSN 0887-7661. Retrieved February 10, 2012.
- "Executive Profile, Dan Harple". Bloomberg Businessweek. Bloomberg.com. Retrieved December 20, 2018.
- "Company Overview". Software: InSoft, Inc. February 10, 2012. Bloomberg Businessweek. Retrieved December 20, 2018.
- "MTALK-Readme" (TXT). Sunsite.edu. Retrieved April 29, 2012.
- Keating, Tom. "Internet Phone Release 4" (PDF). Computer Telephony Interaction Magazine. Retrieved November 7, 2007.
- "The 10 that Established VOIP (Part 1: VocalTec)". iLocus. Retrieved January 21, 2009.
- The free Library RADVision and Intel Target Compatibility Between RADVision's H.323/320 Videoconferencing Gateway And Intel's Business Video Conferencing And TeamStation Products. June 2, 1997 VoiP Developer Solutions
- "H.323 Visual telephone systems and equipment for local area networks which provide a non-guaranteed quality of service". ITU-T. Retrieved January 21, 2009.
- "RFC 2235". R. Zakon. Retrieved January 21, 2009.
- International Telecommunications Union, Standardization Sector (ITU-T), Study Group 15 (1993-1996), Recommendation G.729, March 1996.
- "The 10 that Established VOIP (Part 2: Level 3)". iLocus. July 13, 2007. Retrieved November 7, 2007.
- "RFC 2543, SIP: Session Initiation Protocol". Handley, Schulzrinne, Schooler, Rosenberg. Retrieved January 21, 2009.
- "What is Asterisk". Asterisk.org. Retrieved January 21, 2009.
- Remo, Michelle V. (August 27, 2007). "Prospects bright for voice calls over internet". Philippine Daily Inquirer. Retrieved January 1, 2015.
- Audio-Mitschnitt Archived 2013-02-10 at the Wayback Machine vom Treffen der IETF-Codec-Arbeitsgruppe auf der Konferenz IETF79 in Peking, China mit einer Darstellung der grundlegenden Funktionsprinzipien durch Koen Vos (MP3, ~70 MiB)
- "Skype's new super wideband codec". Wirevolution.com. January 13, 2009. Retrieved March 31, 2009.