Under RFC 4733, if no events parameter is received, the sender should assume the receiver supports DTMF events 0-15 and no others.
Checked 2026-10-02
For backward compatibility, if no 'events' parameter is received, the sender SHOULD assume support for the DTMF events 0-15 but for no other events.
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- RTP telephone-event
- Deployment
- standard
- Region
- not restricted
- Release range
- RFC 4733
- Checked
- 2026-10-02
Sources
- RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals — IETF / RFC Editor · tier 1 standards and regulators · Section 2.5.1.1
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting DTMF digits not detected in Webex Contact Center flows: source note wxcc-dtmf-troubleshooting-rfc4733-default-0-15. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxcc-dtmf-troubleshooting-rfc4733-default-0-15
BibTeX
@misc{warmtransfer-claim-wxcc-dtmf-troubleshooting-rfc4733-default-0-15,
title = {Troubleshooting DTMF digits not detected in Webex Contact Center flows: source note wxcc-dtmf-troubleshooting-rfc4733-default-0-15},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxcc-dtmf-troubleshooting-rfc4733-default-0-15},
note = {Source note wxcc-dtmf-troubleshooting-rfc4733-default-0-15, checked 2026-10-02}
}