pipecat/changelog/4313.deprecated.md at 675b7df4083d60a96fc35c72c929fc64c752417c

Files

Aleix Conchillo Flaqué 675b7df408 Add tones to OutputDTMFFrame and simplify DTMF frame hierarchy

Introduces a new `tones` field on `OutputDTMFFrame` and
`OutputDTMFUrgentFrame` for sending multi-digit DTMF sequences and
deprecates the existing single-key `button` field. When only `button`
is set, it is used as a single-character `tones` string for backward
compatibility.

`DTMFFrame` is kept as an empty marker class so both input and output
DTMF frames can still be identified via isinstance. `InputDTMFFrame`
keeps its required `button` field (single keypress semantics).

The Daily-specific `DailyOutputDTMFFrame` and
`DailyOutputDTMFUrgentFrame` frames no longer need to override
`button` and simply add `session_id` and `digit_duration_ms`, which
are forwarded to Daily's `send_dtmf` as `sessionId` and
`digitDurationMs`.

The base output audio fallback now iterates `tones` and generates a
tone per character; LiveKit's native DTMF path sends `tones[0]` since
its API is single-tone.

2026-04-15 14:48:02 -07:00

227 B

Raw Blame History

Deprecated the button field on OutputDTMFFrame and OutputDTMFUrgentFrame. Use the new tones field instead. When only button is set, button.value is used as a single-tone tones string for backward compatibility.

227 B Raw Blame History

227 B

Raw Blame History