VOS3000 how-to

G.729 on VOS3000

Most G.729 problems are not about sound. They are about how each side names the codec and Annex B in the SDP.

Updated · By the VOS3000 Web team

Quick answer: VOS3000 sets G.729 per gateway under Additional settings, Protocol, SIP: G729 negotiation mode decides whether G729 and G729a are treated as one codec, and G729 annexb decides what annexb value goes to the carrier. Most G729 versus G729a failures are a naming mismatch, fixed with negotiation mode G729 or G729&G729a.

Bitrate
8 kbit/s (G.711: 64 kbit/s)
Negotiation mode
Auto, G729, G729a, G729&G729a
G729 annexb
Auto, yes, no, None, Passthrough
Not for
Fax and modem calls

G.729 in short

G.729 compresses voice to 8 kbit/s, against 64 kbit/s for G.711, which is why many carriers prefer it. G.729A (G729a in VOS3000) is a lower-complexity version with a compatible bitstream: a G.729 decoder plays G.729A audio and the other way round. Annex B adds voice activity detection (VAD) and comfort noise (CNG), so less is sent during silence. Because the voice frames are compatible, most G.729 failures come from the SDP offer, not from the audio.

Where the settings are

On a routing gateway, open Additional settings → Protocol → SIP for G729 negotiation mode, G729 annexb and G723 annexa. H.323 gateways have G729 negotiation mode under Protocol → H323. The mapping gateway's SIP page uses the same descriptions as the routing gateway. Which codecs are offered at all is set in Additional settings → Codec → H323/SIP: Auto negotiation lets caller and callee decide, and Softswitch specified sends only the codecs you add. See codecs and DTMF.

G729 negotiation modeWhat VOS3000 does
AutoKeeps the original G729 codec name.
G729Treats G729a or G729 as G729.
G729aTreats G729 or G729a as G729a.
G729&G729aTreats G729 or G729a as both G729 and G729a.

Why G729 against G729a fails

Some equipment offers the codec as G729, some as G729a, and some accepts only the name it knows. If a customer offers only G729a and the carrier accepts only G729, the offers have nothing in common and the call fails before it rings, often with 488 Not Acceptable Here. Since the audio is compatible, change the name rather than the codec: set the routing gateway to G729 (or G729a) to match the carrier, or to G729&G729a to offer both names.

G729 annexb and G723 annexa

G729 annexbWhat is sent to the routing side
AutoThe routing gateway's own G729 annexb setting.
yesannexb=yes
noannexb=no
NoneNo annexb parameter.
PassthroughThe caller's own G729 annexb setting.

G723 annexa has the same choices for G.723.1 and its Annex A silence suppression. Pitfalls:

  • None is not the same as no. For G.729 in SDP, a missing annexb parameter means annexb=yes (RFC 3555). If a carrier cannot handle Annex B, send no.
  • Passthrough is fine while customer and carrier agree, but it passes a bad value straight on.
  • Comfort noise that sounds like a dropped line is a reason to try no.

When to use G.711 instead

  • Fax and modems: use T.38 or G.711 from end to end; see fax over VOS3000.
  • In-band DTMF: G.729 distorts tones, so use RFC2833 or G.711.
  • One side has no G.729, or bandwidth is not a concern.

Worked example: with 20 ms packets and IP, UDP and RTP headers, a G.729 call needs about 24 kbit/s in each direction and a G.711 call about 80 kbit/s. For 100 calls through media proxy, that is roughly 2.4 Mbit/s against 8 Mbit/s each way, for each call leg.

Check what was used

In Current call, Calling code shows the codec in use, and Caller coding and Callee coding show what each side offered.

Questions about this topic

Are G729 and G729a the same codec?

Not quite. G.729A is a lower-complexity version of G.729, but the two are compatible, so either side can decode the other. The trouble is that devices name them differently in SDP, which can stop negotiation.

Which G729 negotiation mode should I use?

Leave Auto while calls work. If a carrier accepts only one name, choose G729 or G729a to match it, or G729 and G729a together (G729&G729a) to offer both names.

What does annexb=no mean?

It tells the other side not to use G.729 Annex B, so no voice activity detection or comfort noise: voice packets are sent all the time, even in silence.

Can I send fax over G.729?

No. G.729 is built for speech and breaks fax and modem tones. Use T.38, or G.711 from end to end.

Try every step in the live demo

Each screen in this guide is in the VOS3000 Web demo, with made-up data. Sign in with demo / demo.