VoIP codecs G.723, G.711, and G.729 — How it works

A description of the VOIP codecs G.723, G.711 and G.729, needs initially to provide a description of the use performed by codecs. A standard telephone call that utilizes VoIP architecture needs to pass through two separate environments which are not readily interoperable. The first environment belongs to the standard telephony service which is analog and will need to be converted to digital bitstream in order to progress along the digital environment without disruption to the signal.

When the converted signal reaches the end of the digital highway it will need to be converted back into analog in order that it can be processed at its destination which will be another analog telephone and made intelligible. If the signal does not convert in order to pass through the various stretches of its analog and digital journey the signal that arrives at its destination will not be recognizable.

In order to overcome the problems associated with analog-digital conversion engineers have developed codecs (an algorithm) which are able to translate signals and convert them from one category such as analog to another such as digital, so that they may continue their journey without delay and arrive without disruption. In the VoIP environment codecs are used to encode voice for Internet protocol (IP) transmission. As a general rule codecs compress signals as a way of saving bandwidth, yet at the same time compression does slow the signal down adding an artificial delay to conversations. For that reason the search for the ultimate codec, one that is able to perform all the necessary conversion functions, while interacting with all forms of devices in the minimum amount of time continues.

Currently a lack of standardization is an issue that the Internet needs to resolve. The lack of standardization across the Internet has meant that thousands of bolt-on accessories have been constructed and added in order that the Internet continues to function. Although on the surface this may appear as how things should be, a lack of standardization has in fact played against the Internet improving as rapidly as it might have been able to do had standardization been seriously considered essential at the outset. An example of this is that generally when a VoIP call is established, a codec that both parties and one supported by the provider needs to be present.

Unfortunately non-standardization has meant that this does not always occur, which results in an inconsistent service. The various codecs used to assist in the communications that operate over the VoIP architecture such as G.723, G.711, and G.729 are designed to stabilize the signal and thereby produce a consistently adequate communication. The difficulties produced by non-standardization continue because although the many codecs operating within the internet architecture resolve issues found among the most common devices, there are simply too many variables existing, hence inconsistency in regard to VoIP services will continue until users are provided devices designed to interact more effectively, making redundant the short-term codec solutions that we currently have.