Source note · DTMF methods and interoperability failures
The final (E-bit) packet for each telephone event and each segment SHOULD be sent a total of three times at the source's update interval.
Checked 2026-09-24
The final packet for each event and for each segment SHOULD be sent a total of three times at the interval used by the source for updates.
- Vendor
- IETF
- Product
- RTP telephone-event payload
- Subsystem
- sender behaviour
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 4733
- Checked
- 2026-09-24
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.4 Retransmission of Final Packet
Cite this note
APA
WarmTransfer. (2026, September 24). DTMF methods and interoperability failures: source note dtmf-interop-end-packet-sent-three-times. WarmTransfer. https://warmtransfer.net/knowledge/claims/dtmf-interop-end-packet-sent-three-times
BibTeX
@misc{warmtransfer-claim-dtmf-interop-end-packet-sent-three-times,
title = {DTMF methods and interoperability failures: source note dtmf-interop-end-packet-sent-three-times},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/dtmf-interop-end-packet-sent-three-times},
note = {Source note dtmf-interop-end-packet-sent-three-times, checked 2026-09-24}
}