VICIfast
Glossary

carriers-sip

G.729 codec

A compressing voice codec that shrinks each call to about 8 kilobits per second, fitting many more calls on a connection at a small cost to audio clarity.

G.729 is a compressing voice Codec that squeezes each call down to roughly 8 kilobits per second of audio. That heavy compression is its whole point: it lets you fit many more simultaneous calls through the same internet connection than a lightly compressed codec would allow.

The trade-off is sound. Because G.729 throws away more of the audio detail to save space, voices can sound a touch thinner or flatter than they do on a fuller codec. Most people on a normal sales or support call never notice, but it is a real difference and it shows up if you compare it side by side with G.711 codec.

G.729 earns its keep when bandwidth is the bottleneck. A busy outbound floor running a high number of Concurrent calls over a modest connection can serve far more agents by compressing the RTP audio harder. The math is roughly that G.729 uses about a third of the bandwidth of the uncompressed alternative, so the same pipe carries roughly three times the calls.

A couple of practical notes for newcomers. Both ends of a VoIP call must support G.729 for it to be used, and some setups treat it as a licensed feature, so it is worth checking with your carrier. If you have plenty of bandwidth, you may not need it at all. But when you are trying to pack more seats onto a tight connection without buying more internet, G.729 is the usual answer, accepting a slightly lower MOS (mean opinion score) quality score in exchange for capacity.

There is one extra cost to keep in mind. Because G.729 packs and unpacks the audio so aggressively, it asks more of the server's processor than a light codec does, so a box running hundreds of compressed calls works harder than the same box on uncompressed audio. On a hosted dialer this is usually handled for you, but it is worth knowing why a heavily loaded server can feel the strain. It also does not pair well with chaining conversions: if a G.729 call has to be transcoded into a different codec for a transfer or a recording, each hop can shave off a little more quality. The practical takeaway is to use G.729 where it genuinely earns its keep — long-haul or bandwidth-limited links carrying lots of Concurrent calls — and to keep the codec consistent across the call path wherever you can.

Related terms

G.729 — VICIdial glossary · VICIfast