Asterisk DTMF: keypad signalling and diagnosis
Keypad input can fail even when both parties hear speech. Identify the method used on each call leg and whether the application is listening for digits at the time they arrive.
Source-reviewed, 18 October 2026. Prepared from the cited documentation. No keypad path has been independently tested by Phone Guides. Scope: Asterisk 22/PJSIP; endpoint and provider support must be established for their exact versions and service.
Distinguish the methods
| Method | Where the digit is represented | What to inspect |
|---|---|---|
| RTP telephone events | Event payload in RTP, separate from encoded speech | SDP telephone-event negotiation and the actual events |
| Inband | Audible tones in the audio stream | Codec/media path and tone handling |
| SIP INFO | SIP request content under the peer's supported convention | Signalling exchange and documented peer requirements |
RFC 4733 defines RTP telephony-event payloads. Many product settings still use an older RFC 2833 label. Do not infer complete agreement from a label alone; compare what the product documents and what the call negotiates.
Select the endpoint policy deliberately
PJSIP's dtmf_mode is an endpoint option. The Asterisk 22 option reference describes rfc4733, inband, info, none and automatic alternatives. An automatic mode has a defined fallback; it does not mean Asterisk can repair every unsupported peer combination.
For a peer whose documentation establishes RTP telephone events, this is the relevant option within that existing endpoint:
dtmf_mode=rfc4733
It is not a complete endpoint definition and should not be added to an unrelated object type. If a provider requires another method, record that requirement and its service scope instead of changing every phone account globally.
Follow the digit through the application
Check the originating phone setting, the negotiated method towards Asterisk, the menu or other dialplan application, and any onward provider leg. A digit detected by a local menu is evidence for that local path, not proof that an external service receives it correctly.
In an auto attendant, verify whether input is expected during playback, after playback or both. BackGround() and a later input-wait application have different roles from simply playing a sound. A missing destination, an invalid-input extension or a timeout can look like a keypad fault to the caller.
Collect targeted evidence
Record one failing digit sequence, the exact destination, time and call stage. Confirm the application was ready to accept input. Inspect the SDP and relevant signalling/media evidence privately. A SIP-only trace can show INFO but does not establish the presence or absence of RTP telephone events.
Use first troubleshooting checks for a bounded reproduction. Avoid logging PINs, account numbers or sensitive IVR input in ordinary tickets. Test with non-sensitive digits on a destination you are authorised to use.
Check changes one path at a time
After a justified setting change, confirm loaded endpoint state and repeat the same digit sequence. Also check a different key and the intended timing window. If you hear doubled digits or a service receives repeated input, investigate duplicate handling or multiple signalling paths rather than simply increasing the wait.
Keep the previous configuration for reversal. Do not disable media protection or broadly change codecs solely because someone else's old configuration used inband tones. Establish the peer's required method and the actual failure first.
Related: NAT and RTP and call setup. Return to Asterisk documentation.