What is DTMF? Keypad tones, how they travel, and voice AI
DTMF (dual-tone multi-frequency) is the signal a phone sends when you press a key. Here’s how the tones work, how they travel on VoIP calls, why digits go missing, and what changes when an AI agent is on the line.
In this guide
DTMF, short for dual-tone multi-frequency, is what a phone sends when someone presses a key. Each key plays two tones at once, one low and one high, and the system on the other end decodes the pair into a digit. Bell introduced it as Touch-Tone in 1963 to replace rotary pulse dialing, and the frequencies are still defined by ITU-T Recommendation Q.23.
It’s how “press 1 for billing” works, and how callers enter account numbers, PINs and extensions. Voice agents haven’t replaced it: they meet keypads on both sides of a call, and missing keypresses are a common ticket for any phone team.
How DTMF works
The keypad is a grid of four rows and four columns. Every row has a low frequency and every column a high one. Pressing a key plays its row tone and its column tone together.
| 1209 Hz | 1336 Hz | 1477 Hz | 1633 Hz | |
|---|---|---|---|---|
| 697 Hz | 1 | 2 | 3 | A |
| 770 Hz | 4 | 5 | 6 | B |
| 852 Hz | 7 | 8 | 9 | C |
| 941 Hz | * | 0 | # | D |
So the 1 key is 697 Hz plus 1209 Hz, and pound is 941 Hz plus 1477 Hz. The fourth column (A to D) was built for military and network equipment and isn’t on consumer phones, so in practice a phone system handles twelve keys: 0 to 9, star and pound.
The two-tone design keeps DTMF reliable. Voices and background noise rarely put strong energy on exactly one frequency from each group at the same moment, so a decoder can tell a keypress apart from someone talking. Receivers also check how long the pair lasts and how balanced the two tones are before they accept a digit.
How DTMF travels on a VoIP call
On a copper line, DTMF was simply sound on the wire. On a VoIP or SIP trunk call it can travel three ways, and both ends of every leg have to agree on which one.
| Method | How the digit is sent | Where it breaks |
|---|---|---|
| In-band audio | The tones are mixed into the call audio, like any other sound | Compressed codecs and packet loss distort the tones, so digits are missed or repeated |
| RTP events (RFC 4733, formerly RFC 2833) | A separate “telephone-event” packet in the media stream names the digit and how long it was held | One side sends events while the other only listens for tones in the audio |
| SIP INFO | The digit rides in a SIP message on the signaling path, outside the audio | Carriers or proxies that don’t pass INFO messages along, and timing that drifts from the audio |
RFC 4733 replaced RFC 2833 in 2006, but most carrier and PBX settings still say “RFC 2833.” They mean the same thing. Use it unless something forces you not to. The digit arrives as data rather than as a sound to decode, so the codec doesn’t matter, and nearly every carrier, SBC and contact center platform supports it.
Codecs matter for in-band tones. G.711, the uncompressed 8 kHz codec most phone calls use, carries DTMF well. Low-bitrate codecs such as G.729 are tuned for speech and can smear the tones enough that a decoder misses them, which is why RTP events exist in the first place.
Why DTMF digits go missing
When keypresses work on one route and fail on another, check these in order:
- Mismatched methods. One leg sends RTP events and the next only decodes in-band audio, or the other way round. Compare the DTMF settings in the SDP offer and answer on every leg of the call.
- A compressed leg. Somewhere in the path the call is transcoded to a low-bitrate codec, and the in-band tones don’t survive. Move that leg to RTP events or keep it on G.711.
- Doubled digits. A gateway sends each press both as audio and as an event, and the receiver counts both. “1234” arrives as “11223344.” Turn off one of the two.
- Short or clipped tones. Tones that are too short, or that start while audio is being trimmed for silence, fall below what the receiver accepts.
- Timeouts. The caller pauses mid-entry and the system submits a partial number. Ask for a terminator (“then press pound”) and set the expected length when you know it.
Test on the real path. A softphone or SIP test client often negotiates a different DTMF method than a mobile phone on the public network. Call in from an ordinary phone, press every key, and enter a number with repeated digits in it.
DTMF and AI voice agents
A voice agent lets callers say what they want instead of working through a keypad menu, the idea behind a natural language IVR. Keypads still show up in two places.
Callers pressing keys
Callers who have spent years in IVR menus press keys out of habit, and some information is easier to type than to say. If the agent sits behind an existing IVR, or hands calls back to one, every leg needs a DTMF method that works end to end, or a caller’s keypress disappears between systems.
Card numbers and full PINs deserve their own path. Keeping them out of the conversation, the transcript and the model, for example by handing off to a payment flow that stays inside your PCI scope, is simpler than cleaning them out afterwards.
Agents pressing keys
An outbound agent that calls a business, a pharmacy or an insurer usually meets that company’s phone tree first, and an agent transferring a call may need to dial an extension. To get through, the agent has to send tones itself.
Simple’s voice agents can press keys (0 to 9, star and pound) to work through phone menus, turned on only for the steps of a call that need it. Three habits keep menu navigation reliable:
- Listen to the whole prompt. Many menus ignore input until the prompt finishes, and the right option is often the last one read out.
- Give the agent known paths. If you know a supplier’s menu, put the sequence in the agent’s instructions (“press 2, then 4, then enter the account number followed by pound”).
- Plan for a person picking up. When a menu ends with a live representative, the agent should switch straight back to conversation.
Connecting an agent to your phone system
When Simple connects over a SIP trunk, it sends and receives DTMF as RFC 2833 events, alongside G.711 and Opus audio. If your carrier or CCaaS platform defaults to in-band tones or SIP INFO, settle the method during setup, and check keypresses along with caller ID, audio and transfers before moving live traffic.