VOS3000 codecs and DTMF settings
Make both sides agree on the audio codec and on how keypad tones are sent.
Updated · By the VOS3000 Web team
Quick answer: In a VOS3000 gateway's Additional Settings, the Codec tab chooses Auto negotiation or a Softswitch specified codec list, with optional audio transcoding, and the Protocol tab sets G729 modes and DTMF. For DTMF, RFC2833 is the most common choice; SIP INFO and inband are also available.
- Codecs
- Auto negotiation or Softswitch specified
- Transcoding
- Allows audio transcoding
- DTMF send (SIP)
- Auto, RFC2833, SIP INFO, Off
- No shared codec
- AudioCodecsNotMatch (-45)
Both settings are in a gateway's Additional Settings: codecs on the Codec tab, DTMF on Protocol → DTMF, and G729 options on Protocol → SIP (or H323).
Codecs
- Auto negotiation: the default. VOS3000 lets the two sides agree on a codec.
- Softswitch specified: you choose the codecs. Move codecs from Optional codec to Specify codec and put them in order with Move up and Move down; the first is preferred.
- Allows audio transcoding: lets VOS3000 convert between codecs when the two sides share none.
Available codecs include PCMA, PCMU, G729, G729D, G729E, G723, G722, G726, G728, GSM, GSM-EFR, iLBC, Speex, AMR, SILK and OPUS. Calls where the sides share no codec end with AudioCodecsNotMatch (-45).
G729 options
G729 negotiation mode controls how G729 and G729a are offered:
- Auto: keeps the original G729 codec.
- G729: treats G729a or G729 as G729.
- G729a: treats G729a or G729 as G729a.
- G729&G729a: offers both G729 and G729a.
G729 annexb and G723 annexa (silence suppression) can be Auto, yes, no, None (no annex) or Passthrough.
DTMF
DTMF carries keypad presses, for IVRs and calling-card menus. Both sides must use the same method.
- Dtmf send(sip): Auto, RFC2833, SIP INFO or Off.
- Dtmf send(h323): Auto, RFC2833, H.245 alphanumeric, H.245 signal, Q.931 keypad or Off.
- Dtmf receive: All, RFC2833, Signaling or Off.
- Payload type fields for SIP, H323 and receive, when a carrier uses a non-standard RFC2833 payload type.
- Require inband dtmf and Rtp contain inband dtmf, for tones carried inside the audio.
Common problems
- IVR does not react to key presses: the DTMF methods do not match. Try RFC2833 on both sides, or SIP INFO if the carrier asks for it.
- Keys are pressed twice: DTMF is sent both inband and out of band. Turn one of them off.
- No audio on some calls: check the codecs first, then the audio path; see one-way audio.
Questions about this topic
Which DTMF method should I use in VOS3000?
RFC2833 is the most widely supported. Use SIP INFO only when a carrier or device asks for it.
Should I turn on transcoding?
Only where the two sides share no codec. Transcoding uses server resources, so prefer a shared codec.
What is the difference between G729 and G729a?
They are compatible variants of the same codec. The G729 negotiation mode decides how VOS3000 offers them to each side.
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.
Keep reading
G.729 on VOS3000
G729 negotiation mode, annexb and annexa, why G729 and G729a calls fail, and when G.711 is the better choice.
Fax over VOS3000 (T.38)
Allow T.38 on gateways, or carry fax as G.711, and avoid the settings that break it.
Call transfer and pickup keys
Blind, attended and pickup transfer, hold and call pickup: the keys and the parameters behind them.
Media proxy
What On, Off, Auto and Must on do, how Auto decides, and what it costs in bandwidth.