Tech

G726: The Best Things in Life Are Free

Published on:

November 21, 2013

Absent for years, the G.726 codec has been reintroduced in version 5.1.3 of our PBX. This codec offers favorable characteristics, including a low data rate of around 56 kbit/s, which is ideal for bandwidth-limited environments. Its lower CPU overhead makes it particularly useful for PBX systems, which handle multiple calls simultaneously. While not ideal for music on hold, due to its simple compression, G.726 performs better than more compressed codecs like G.729. Widely supported by devices like snom, Yealink, Linksys, and Grandstream, the PBX now dynamically handles the codec, improving compatibility and performance.

It has been ages since we have added the G.726 codec. This codec has some features quite favorable for a PBX: it typically runs on 32 kbit/s, which translates into a data rate on the cable of 56 kbit/s (if you include the overhead for the RTP and IP headers). It also has a relatively low CPU overhead, at least compared to heavyweights like OPUS or speex. You have to keep in mind the PBX potentially has to run many calls with that codec, in contrast with endpoints that usually run only one call. Thus the CPU overhead is much more important for a PBX than for the endpoint.

G.726 is not exactly the best codec for music on hold, but at least it performs better than codecs that compress voice a lot more, like G.729 or G.723. This is also no big surprise if you think about it - if you take a lot of bits out of the media stream, it's only the voice that's left over, and other things like drums and trumpets don’t make it. Because the G.726 model is quite simple, it doesn't really differentiate between voice and music.

G.726 is widely deployed in DECT digital cordless telephones, but in the VoIP world it's available in many devices. Quick research shows at least snom, Yealink, Linksys SPA, and also Grandstream support it.

Anyway, it was time to review the support for this codec on the PBX. The IETF originally specified a hardcoded codec type 2 for G.726, probably in anticipation this codec would be very popular. There were problems with the “bit-sex” representation, however; the ITU was using a different representation than the IETF, which lead to quite a lot of chaos getting this codec working between the different devices. We also did take a second look and decided to drop the hardcoded codec number and instead choose a dynamic codec number; this seems to work well with most devices. Version 5.1.3 will re-introduce G.726, and we hope those with limited bandwidth with consider this codec again.

Latest Articles

View All

MEDICA 2026: Why the Future of Healthcare Needs a Voice

What is a telephony vendor doing at the world's largest medical trade fair? After four days at MEDICA 2026 in Düsseldorf, we reflect on a challenge that runs through every hospital, practice and care home: finding time for conversation as administrative demands grow and resources shrink. From AI that supports everyday calls to resilient infrastructure that keeps people connected, we explore how voice communication can help healthcare teams protect that time, improve care and create new opportunities for collaboration.

November 19, 2026

Cloud or on-premises? Rethinking phone system reliability after a Microsoft outage

The latest Microsoft outage raises a familiar question: does every service need to run in the cloud? For business phone systems, reliability depends on the infrastructure, the people managing it and the backup options available. An on-premises PBX can keep local communications running during an internet outage, while distributing systems across locations can help limit the impact of individual failures.

November 17, 2026

A PBX That Lets You Build It Your Way

Every business handles calls differently, and its phone system should support those differences. Vodia PBX gives businesses and service providers the flexibility to shape call flows, configure individual tenants and extensions, and build a branded experience for their customers. Queues, ring groups, schedules, forwarding, and AI agents can work together around each team’s requirements, while the REST API connects the phone system with wider business workflows.

November 11, 2026