Houston Finance

Jul 31 2017

Understanding Codecs: Complexity, Hardware Support, MOS, and Negotiation #voip #codec #comparison


Understanding Codecs: Complexity, Hardware Support, MOS, and Negotiation

This document provides an overview of the different coder-decoders (codecs) used with Cisco IOS Voice over IP (VoIP) gateways. In Cisco IOS Software Releases earlier than 12.0(5)T, VoIP gateways supports only the G.729 and G.711 codecs and only one voice/fax-relay call per digital signal processor (DSP). With the introduction of Cisco IOS Software Release 12.0(5)T, Cisco VoIP gateways support a larger number of codecs and DSP modules. They can also support up to four voice/fax-relay calls per DSP.

The DSP Calculator tool (registered customers only) determines the DSP requirements for the Cisco 1751, 1760, 2600XM, 2691, 2800, 3700, and 3800 series router platforms and provides PVDM provisioning suggestions as output. The tool calculates the DSP requirements based on the interface modules, codec configurations, transcoding channels, and conference sessions provided as input. This tool supports different Cisco IOS Software releases valid for the Cisco 1751, 1760, 2600XM, 2691, 2800, 3700, and 3800 platforms.

There are no specific requirements for this document.

This document is not restricted to specific software and hardware versions.

For more information on document conventions, refer to the Cisco Technical Tips Conventions .

Some codec compression techniques require more processing power than others. Codec complexity is broken into two categories named medium and high complexity.

Medium complexity allows the C549 DSPs to process up to four voice/fax-relay calls per DSP and the C5510 DSPs to process up to eight voice/fax-relay calls per DSP.

High complexity allows the C549 DSPs to process up to two voice/fax-relay calls per DSP and the C5510 DSPs to process up to six voice/fax-relay calls per DSP.

Medium Complexity (4 calls / dsp)

High Complexity ( 2 calls / dsp)

Note: The difference between medium and high complexity codecs is the amount of CPU utilization necessary to process the codec algorithm, and therefore, the number of voice channels that can be supported by a single DSP. For this reason, all the medium complexity codecs can also be run in high complexity mode, but fewer (usually half) of the channels are available per DSP.

Note: Fax-relay (2400 bps, 4800 bps, 7200 bps, 9600 bps, 12 kbps, and 14.4 kbps) can use medium or high complexity codecs.

On platforms that support the C549 DSP technology, the codec complexity is configured under the voice-card (for example, the 2600/3600/VG-200 High Density Voice Network Module). Some platforms support only high complexity because they have enough DSPs onboard to support all T1/E1 channels that use the high complexity mode. In order to specify call density and codec complexity according to the codec standard that is used, use the codec complexity command in voice-card configuration mode.

An example of the complexity configuration is shown here:

On platforms that support C5510 DSP technology, an additional option of flex complexity is available. When you use flex complexity, up to sixteen calls can be completed per DSP. The number of supported calls varies from six to sixteen and is based on the codec used for a call.

An example of the configuration is shown here:

This is an excerpt from the show running-config output to determine which complexity is configured:

This table lists the codec support for various Cisco router platforms.

Although it can seem logical from a financial standpoint to convert all calls to low-bit rate codecs to save on infrastructure costs, exercise additional care when you design voice networks with low-bit rate compression. There are drawbacks to compressing voice. One of the main drawbacks is signal distortion due to multiple encodings (called tandem encodings). For example, when a G.729 voice signal is tandem encoded three times, the MOS score drops from 3.92 (very good) to 2.68 (unacceptable). Another drawback is codec-induced delay with low bit-rate codecs.

These two sections clarify many of the common compatibility issues related to the G.729 (8 kbps) codec implementation.

Cisco released a G.729 pre-Internet Engineering Task Force (IETF) codec implementation before the G.729 codec was standardized. In Cisco IOS 12.0(5)T and later, the default bit-ordering of the G.729 codec is changed from the pre-IETF standard to the IETF standardized format. The two formats do not interoperate and result in an unintelligible gulping sound to the end-users.

For compatibility with other vendor’s G.729 implementations, Cisco IOS Software Release 12.0.5T and later default to the standardized implementation of G.729. For backwards compatibility with Cisco IOS software releases earlier than Cisco IOS Software Release 12.0.5T, enable the pre-IETF G.729 implementation with this command:

The pre-ietf option in this command is not supported in Cisco IOS Release 12.2 and later.

G.729 is a high complexity algorithm, and G.729A (also known as G.729 Annex-A) is a medium complexity variant of G.729 with slightly lower voice quality. All platforms that support G.729 also support G.729A.

On Cisco IOS gateways, the variant to use (G.729 or G.729A) is related to the codec complexity configuration on the voice card. It does not show up explicitly in the Cisco IOS command line interface (CLI) codec choice. For example, the CLI does not show g729ar8 ( a code) as a codec option. However, if the voice-card is defined as medium-complexity, then the g729r8 option is the G.729A codec.

Note: For the MC3810, in Cisco IOS Software releases earlier than 12.0.7XK, there is an explicit CLI choice between twenty-four channels of G.729A or twelve channels of G.729.

G.729 Annex-B is a high complexity algorithm, and G.729A Annex-B is a medium complexity variant of G.729 Annex-B with slightly lower voice quality. The difference between the G.729 and G.729 Annex-B codec is that the G.729 Annex-B codec provides built-in IETF voice activity detection (VAD) and Comfort Noise Generation (CNG).

These G.729 codec combinations interoperate:

G.729A and G.729A

G.729 Annex-B and G.729A Annex-B

G.729 Annex-B and G.729 Annex-B

G.729A Annex-B and G.729A Annex-B

Note: There is no explicit way to configure G.729A on the Cisco 2600/3600/VG-200 NM-1V and NM-2V (voice network module) since these voice modules do not support the codec complexity configuration supported on the NM-HDV (High Density Voice Network Module). However, if a G.729A call is set up by another endpoint that terminates on the NM-1V/2V, the call is successfully connected.

There are two versions of G.723.1 called Annex-A and non Annex-A. These versions do not interoperate. G.723.1 Annex-A includes a built-in IETF VAD algorithm and CNG.

Also, in Cisco IOS Software Release 12.0(5)T and later, the G.723.1 codec is supported with a 5.3 kbps and 6.3 kbps rate. When a Cisco VoIP gateway sets up a call between devices that use G723.1, it is concerned only that the far-end uses G.723.1. Neither side is concerned with the 5.3 kbps or 6.3 kbps rate that is supported by the other side. This means that, while it is beneficial to have both sides support the same rate, it is possible that one side transmits at 5.3 kbps and the reverse direction transmits at 6.3 kbps. The speed that is used is viewed with the show call active voice brief command as shown here:

The G.723.1 standard allow stations to change rates between 6.3 kbps and 5.3 kbps during a call to adjust to network traffic loads. The Cisco VoIP gateways do not support this functionality. But they do understand if the remote device (such as a Cisco IP Phone) transmits at a different rate than was originally negotiated.

These G.723.1 codec combinations interoperate:

G.723.1 (5.3 kbps) and G.723.1 (6.3 kbps)

G.723.1 (5.3 kbps) and G.723.1 (5.3 kbps)

G.723.1 (6.3 kbps) and G.723.1 (6.3 kbps)

G.723.1 Annex-A (5.3 kbps) and G.723.1 Annex-A (6.3 kbps)

G.723.1 Annex-A (5.3 kbps) and G.723.1 Annex-A (5.3 kbps)

G.723.1 Annex-A (6.3 kbps) and G.723.1 Annex-A (6.3 kbps)

With the introduction of Cisco IOS Software Release 12.0(5)T, Cisco VoIP gateways support the codec negotiation feature. This feature provides the ability for a Cisco VoIP gateway to connect to other VoIP devices without necessarily knowing which codec is used for a call-setup. Also, this feature allows Cisco VoIP gateways to dynamically adjust to changes on remote devices. As long as the codec used by the remote VoIP device matches the capabilities-list of the Cisco VoIP gateway, the VoIP call is completed. Codec negotiation is supported on both the C542 and C549 DSPs. To specify a list of preferred codecs to use on a dial peer, use the codec preference command in voice-class configuration mode.

This example shows how to configure codec negotiation:

The %DSPRM-5-SETCODEC error is due to a high complexity codec configured on a VoIP dial-peer while it still has the voice card set for the default of medium complexity. To fix this problem, you must remove the ds0-group configuration from the controller which causes the voice-port to be removed. After you remove the ds0-group, follow the procedures earlier in this document to change the complexity.

Written by admin

Leave a Reply

Your email address will not be published. Required fields are marked *