Ir para o conteúdo
Glossário November 2026 6 min de leitura

What Is DTMF (Touch-Tone Signalling)?

DTMF is the touch-tone signalling a caller sends by pressing keys. Learn how digits travel over VoIP: RFC 4733 telephone events, in-band tones and SIP INFO.

D
November 2026
Última atualização

Resposta rápida

DTMF (dual-tone multi-frequency) is the signalling used when a caller presses keys on the phone. Over VoIP the digits can be sent as tones inside the audio, as RTP telephone events defined in RFC 4733, or as SIP INFO messages. RFC 4733 defines 16 DTMF events: the digits 0 to 9, star, hash and the letters A to D.

Every time you have been told to press 1 for sales, you have used DTMF. It is a long-established way for a caller to send a choice to a machine, and it is still used for phone menus, PIN entries and confirmations. On VoIP it has a quirk: the digits have to be carried across a network built to move audio and packets, so there is more than one way to do it, and a mismatch between the two ends is a well-known cause of menus that do not respond.

The Definition

RFC 4733 describes how to carry DTMF signalling, other tones and telephony events in RTP packets. It defines 16 DTMF events: the digits 0 to 9, the star key (code 10), the hash key (code 11) and the letters A to D (codes 12 to 15). Each event carries a volume value. The RFC obsoletes RFC 2833, a name that systems still use in their settings; DialerBee's own deployment options list the mode as RFC 2833.

Como funciona

There are three common methods, and a system usually lets you choose one.

  • In-band. The tones are part of the audio stream itself, and the receiving end listens for them.
  • RTP telephone events (RFC 4733, formerly RFC 2833). The digit is sent as data. RFC 4733 carries it in a telephone-event payload with a dynamically assigned payload type and a default clock rate of 8000 Hz. Events travel in the same stream as the audio and share its sequence number and timestamp base. The first packet of an event has the marker bit set, update packets repeat the timestamp with a growing duration, and the final packet, flagged with the end (E) bit, should be sent a total of three times so that the event's duration is still recognized if one copy is lost.
  • SIP INFO. The digit is sent as a SIP message. RFC 6086 defines the INFO method and an Info Package framework but defines no DTMF package. It notes that companies have used INFO to carry DTMF tones, that all of these mechanisms are proprietary and not standardized, and that DTMF can produce bursts of INFO traffic of up to 20 messages per second.

An Example

An inbound caller reaches a menu and presses 2 for billing. With RTP telephone events, the caller's phone or gateway sends an event with code 2 in the media stream, begins it with the marker bit, sends updates as the key is held, and ends it with repeated end packets. The platform receives event 2 and takes the billing branch. If the two ends disagreed about the method, for instance one sending events while the other listens only for in-band tones, the menu would never see the key press, and the caller would hear it ignored.

Why It Matters for Outbound and Inbound Teams

For inbound teams DTMF is the input of an IVR: menus, account numbers and confirmations. The Construtor IVR is where flows like these are designed. For outbound teams it matters when calls hit an automated menu on the far side, or when the dialer must press a digit to confirm a connection.

When connecting a carrier or PBX, the DTMF mode is one of the settings to agree. DialerBee's deployment options let you set it to match what your platform already expects: RFC 2833, in-band or SIP INFO. Because RFC 4733 is the updated version of RFC 2833, that setting is the telephone-event method described above. If key presses are being lost on a live trunk, the DTMF troubleshooting guide walks through the checks. The SIP trunk setup guide lists the other settings to confirm with a trunk SIP provider.

Troubleshooting Checklist

  1. Confirm which method each side expects, and set both the same.
  2. Check that the telephone-event payload is negotiated in the call setup.
  3. Test with a real key press on a test call, not only a configuration review.
  4. If digits are doubled or dropped, look at how the end-of-event packets are being handled.

Perguntas frequentes

What does DTMF stand for?

Dual-tone multi-frequency. It is the signalling used when a caller presses a key on a touch-tone keypad.

Which digits does DTMF support?

RFC 4733 defines 16 DTMF events: 0 to 9, star, hash and A to D. The letters A to D are rarely on consumer keypads.

What is the difference between RFC 2833 and RFC 4733?

RFC 4733 obsoletes RFC 2833. It keeps the same basic approach of carrying DTMF and other events in RTP packets, retains only the most basic event codes and sets up an IANA registry to which other event codes may be added.

Is SIP INFO a standard way to send DTMF?

RFC 6086 defines the INFO method but no DTMF Info Package, and notes that INFO-based DTMF mechanisms are proprietary and not standardized. Where a system offers it as an option, both ends still have to use the same method.

Why are my keypad presses ignored on a VoIP call?

A frequent cause is a mismatch in the DTMF method between the two ends. Check that both sides use the same one and that telephone events are negotiated.

Related terms and guides: IVR, Construtor IVR, Configuração de trunk SIP, trunk SIP.

Fontes

Termos relacionados

Pronto para ver DialerBee em ação?

Solicite uma demo ao vivo de 15 minutos ou comece um teste grátis de 14 dias — sem slides, sem compromisso. As ligações começam assim que o seu próprio SIP trunk ou PBX estiver conectado e aprovado.

Teste grátis de 14 dias · crédito de IA gratuito · sem cartão · 11 idiomas · BYOC · controles de apoio à conformidade

Ver o site completo em inglês →