Skip to content
Technology November 7, 2026 10 min read

DTMF Not Working on a SIP Trunk? How to Fix Keypresses

IVR menus and opt-out keys ignored? Learn how RFC 4733 events, SIP INFO and in-band DTMF differ, why a mode mismatch drops digits, and how to test each one.

D
November 7, 2026

Quick answer

DTMF fails on a SIP trunk when the two sides do not agree on how digits travel. There are three methods: RTP telephone-events (RFC 4733, which replaced RFC 2833), SIP INFO messages, and in-band audio tones. A mode mismatch drops digits, a payload type mismatch loses RTP events, and a compressed codec can mangle in-band tones. Two active methods at once cause doubled digits. Fix it by agreeing one method per call leg, then testing each route with one call per method and reading the trace.

A caller presses 1 and the menu does not move. An agent dials an extension through an IVR and nothing happens. A contact presses 9 to opt out and the call carries on. Each of these is a DTMF problem, and each is invisible until someone tests it, because the call itself connects and the audio sounds fine.

This guide explains the three ways a keypress crosses a SIP trunk, why digits vanish or double, what transcoding and media bypass do to them, and how to build a short test plan that proves each method before a campaign goes live. It is carrier-neutral: the same logic applies to any PBX, session border controller or dialer.

Three ways DTMF travels

DTMF (dual-tone multi-frequency) is the signal your phone keypad produces. On a SIP call there are three different ways to move that signal from one side to the other, and the two ends must agree on which one is in use.

1. RTP telephone-events (RFC 4733, formerly RFC 2833)

Here the digit is not sent as sound at all. The sender emits small RTP packets, in the same media stream as the audio, that say "digit 5 started" and "digit 5 ended". RFC 4733 obsoletes RFC 2833 (RFC 4733, abstract; its section 1.2 points to the list of changes), which is why you will see both names used for the same mechanism. The event codes are simple: digits 0 to 9 are events 0 to 9, * is event 10, # is event 11, and the letters A to D are events 12 to 15 (RFC 4733, section 3.2).

Each event packet carries the event number, an "end" bit that marks the final packet, a volume field and a duration (RFC 4733, section 2.3). The first packet of an event must have the RTP marker bit set, and the final packet should be sent a total of three times so that a single lost packet does not lose the end of the keypress (RFC 4733, sections 2.5.1.2 and 2.5.1.4).

The payload type for telephone-events is not fixed. It is a dynamic value agreed in the SDP of the call, and the default clock rate is 8000 Hz (RFC 4733, sections 2.1 and 2.4). A typical SDP line pair looks like this:

m=audio 16384 RTP/AVP 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Here payload type 101 is the telephone-event, and "0-15" means the sender supports the sixteen DTMF events. The number 101 is only an example. Another device might use 96, 100 or 127, because RFC 3551 reserves payload types 96 to 127 for dynamic assignment (RFC 3551, section 3). The SDP is the contract: each side must send the number the other side offered.

2. SIP INFO

With SIP INFO, the digit is sent as a signalling message inside the call dialog, not in the media stream. The framework for the INFO method is RFC 6086, but that document does not define a DTMF format. It notes that existing uses of INFO for DTMF are proprietary and have not been standardised (RFC 6086, section 2). In practice, that means the body of a DTMF INFO message differs between vendors, so INFO is the method most likely to fail between unlike systems.

RFC 6086 also warns that DTMF can generate bursts of up to 20 INFO messages per second, and that data which is latency-sensitive is better sent on the media path, because SIP routing can add hundreds of milliseconds (RFC 6086, sections 8.3 and 8.4.2.1). INFO is a valid choice when a platform or carrier requires it, but it is rarely the first choice between two systems that both support RTP events.

3. In-band audio

In-band DTMF is the actual tone, mixed into the voice audio like any other sound. The receiver listens to the audio and detects the tone. It needs no negotiation, which is why it works almost everywhere on a clean G.711 path, and why it fails so often anywhere else: the tone has to survive every encoding step between the two ends.

MethodWhere the digit travelsNeeds SDP agreementTypical weakness
RTP telephone-event (RFC 4733)RTP media stream, as event packetsYes: dynamic payload typePayload type mismatch, a device that strips events
SIP INFO (RFC 6086 framework)SIP signalling, inside the dialogYes: both sides must accept itVendor-specific body, added delay
In-band audioVoice audio itselfNoCodec distortion, short tones missed

Why digits vanish

Mode mismatch

The simplest failure: one side sends RTP events, the other side only listens for SIP INFO. The sender believes it has done its job. The receiver never sees a digit. Both devices are working correctly according to their own settings, so there is no error anywhere, only a menu that does not respond.

Payload type mismatch

Both sides use RTP events, but they disagree on the payload type number. Side A offers telephone-event as 101 and side B sends events as 96. Because the number is negotiated per call and per direction, a device that hard-codes 101 will quietly ignore packets labelled 96. Always read the SDP of both legs in the trace, and compare the payload type in the offer with the payload type of the packets actually arriving.

Compressed codecs and in-band tones

A speech codec is designed to represent the human voice. A pure tone is not a voice, and low-bit-rate codecs can smear, shorten or distort it so the receiver's detector no longer recognises it. RFC 3551 lists G.711 (PCMU, payload type 0, and PCMA, payload type 8) and G.729 (payload type 18), all at an 8000 Hz clock rate (RFC 3551, section 6). If you must rely on in-band tones, G.711 is the safest codec because it is uncompressed in the speech sense; a compressed codec on any hop is a risk. This is the main reason to prefer RTP events: the digit is carried as data, so the codec does not touch it.

Short presses

Some people press a key very briefly, and some IVR detectors expect a minimum tone length. With RTP events the sender reports the duration explicitly, which helps. With in-band audio the detector has to decide from the sound alone. If only fast presses fail, suspect detector timing rather than a mismatch.

Why digits double

A doubled digit, such as 5 arriving as 55, almost always means two methods are active at the same time. A typical case: the far end sends an RTP telephone-event and the in-band tone also stays in the audio. The receiver's detector hears the tone and also receives the event, and counts the keypress twice.

Other causes to check:

  • A device in the middle converts methods. A session border controller or media server might turn INFO into RTP events while still forwarding the original INFO.
  • "Auto-detect" modes that listen for several methods at once, when the other side is sending more than one.
  • Duplicate end packets treated as new events. RFC 4733 expects the final packet to be repeated, and once an event has been played out and ended, further reports for it must be ignored, not counted as new keypresses (RFC 4733, sections 2.5.1.4 and 2.5.2.2).

The cure is the same each time: one method per call leg, and a clear owner for each conversion point.

Transcoding, media bypass and DTMF

Transcoding. When the two sides share no codec, a media server decodes and re-encodes the audio. That is the worst case for in-band tones, because the tone passes through two codecs. It is a smaller problem for RTP events, but only if the transcoding device passes telephone-events through or re-originates them. Some devices do not, and they drop the digit without a log entry.

Media bypass (direct media). When media flows directly between endpoints, the platform in the signalling path never sees the RTP events or the tones. A feature that depends on hearing the keypress, such as an IVR run on the platform, can break if media bypass is on. Where a dialer or contact-centre platform needs to act on keypresses, keep media on the platform for that leg.

Several hops. Each extra device (carrier gateway, border controller, PBX) is a place where a mode can be converted or a payload type renumbered. Test end to end, not just carrier to platform.

Why it matters on outbound calls

Outbound teams depend on keypresses more than they might expect:

  • Opt-out keys. Many campaigns tell the person to press a key to be removed from the list. If the key is not recognised, the person's request is lost and they are called again. Treat it as a quality and customer-trust issue, and check your own legal obligations with qualified counsel; this guide gives technical advice, not legal advice.
  • Press-1 connect. Voice broadcast and callback campaigns use a keypress to transfer to an agent.
  • IVR payments and verification. Digits entered for an account number or a date of birth must arrive intact, with no drops or doubles.
  • Agent navigation. An agent calling into a customer's phone menu must be able to press keys.

Because a failed keypress produces no error, it is a silent failure. See our guide to calling hours, DNC and consent rules for how opt-out handling fits into a wider rules set.

A test plan: one call per method

Do not test "DTMF" in general. Test each method separately and read the trace each time.

  1. Write down the plan. For each carrier route, record which method each leg should use, and the payload type you expect.
  2. Test RTP events. Place a call to a test IVR or echo-style line that reports digits. In the trace, find the SDP of both legs and confirm both list a telephone-event with matching payload type. Press 1, 5, 9, * and #, and confirm each is reported once.
  3. Test SIP INFO. Switch the leg to INFO only, with RTP events off. Confirm INFO messages appear in the trace and the digits arrive once each.
  4. Test in-band. Switch to in-band only, with G.711 forced, and repeat. Then repeat with your compressed codec, to see whether it survives.
  5. Test fast and slow presses. Tap quickly, hold for a second, and enter a long string such as a 10-digit account number.
  6. Test the opt-out flow. Run a real test campaign call to an internal number you control, press the opt-out key and confirm the contact is marked correctly in the system.
  7. Repeat per route. Another carrier, region or codec can behave differently. Repeat after any change to a trunk.

An illustrative reading of a trace: if the call's SDP shows telephone-event on payload 101 from your side and payload 96 from theirs, and digits are lost only in one direction, the payload mismatch is your first suspect.

How DialerBee fits

On DialerBee's bring-your-own-carrier gateway form, the Codecs tab has a DTMF Mode setting that defaults to RFC 2833 (telephone-event), with Inband (audio), SIP INFO and Auto-detect as the other choices. The step-by-step setup is in How to Connect Your SIP Trunk (BYOC Setup), and the architecture is described on the Bring Your Own Carrier page. The setup guide lists a DTMF test against an IVR or test line in its go-live checklist and names an ignored opt-out keypress as a typical sign of a DTMF mode mismatch.

Set the mode to what your carrier supports, then test it as described above. For menus you build yourself, the IVR builder is where callers' menu paths are designed, and a keypress test on each menu belongs in your launch checks. If IVR terminology is new, What Is IVR covers the basics.

Frequently asked questions

Why is DTMF not working on my SIP trunk?

The most common cause is a mode mismatch: one side sends digits as RTP telephone-event packets (RFC 4733, still often called RFC 2833), the other side listens for SIP INFO or for in-band tones. The second most common cause is a payload type mismatch, where the telephone-event payload type in the SDP of one side differs from what the other side sends or expects. Check the SDP of both legs, then run one test call per method.

What is the difference between RFC 2833, RFC 4733, SIP INFO and in-band DTMF?

RFC 4733 replaced RFC 2833 and sends each keypress as a small RTP packet marked as a telephone-event, alongside the audio. SIP INFO sends the digit as a signalling message inside the call dialog instead of in the media stream, and RFC 6086 only defines the INFO framework, not a DTMF format. In-band DTMF is the audible tone itself, carried as ordinary audio, so it depends on the codec preserving the tone.

Why do I get double digits when I press one key?

Usually two methods are active at once, for example the far end sends a telephone-event and also leaves the in-band tone in the audio, and the receiver decodes both. It can also happen when a device in the middle converts one method to another and does not suppress the original. Fix it by agreeing on one method per call leg and checking that nothing in the path adds a second copy.

Does the codec affect DTMF?

For RTP telephone-events, the digit travels as separate packets, so the codec matters much less. For in-band DTMF it matters a lot: tones must survive encoding and decoding, and a low-bit-rate speech codec can distort them. Uncompressed G.711 (PCMU and PCMA) is the safest codec if you must use in-band tones.

Can an opt-out key like press 9 fail silently?

Yes. If the key is not recognised, the call carries on as though nothing was pressed, and nobody sees an error. That is why a keypress test belongs in every go-live checklist, on every carrier route you use, and why you should test again after any change to a trunk, codec or media setting.

Which DTMF mode should I choose?

Choose the mode your carrier has told you it supports, and prefer RTP telephone-events when both sides support them, because they are carried separately from the speech audio. Treat anything else as a deliberate exception that you test end to end. Never assume the default suits every carrier route.

Sources

  1. RFC 4733, RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals. rfc-editor.org/rfc/rfc4733 (checked November 7, 2026)
  2. RFC 6086, Session Initiation Protocol (SIP) INFO Method and Package Framework. rfc-editor.org/rfc/rfc6086 (checked November 7, 2026)
  3. RFC 3551, RTP Profile for Audio and Video Conferences with Minimal Control. rfc-editor.org/rfc/rfc3551 (checked November 7, 2026)

Related reading

Ready to see DialerBee in action?

Request a 15-minute live demo, or start a 14-day free trial — no slides, no commitment. Calling starts once your own SIP trunk or PBX is connected and approved.

14-day free trial · free AI credit · no card · 11 languages · BYOC · compliance-supporting controls