Dead-air after caller

open

1 independent reportacross 1 sourceon 1 stacklast reported 2026-07-24

What this is

The caller finishes and the line goes silent for seconds before the agent responds, with no audible acknowledgement in between.

Status open: reported and still open where it was reported.

Evidence

A report2026-07-24GitHub issueshow a report comes down
Withdrawn: collected in error: a pull request is a change somebody wrote, not an independent report of a call that went wrong.

First seen 2026-07-24 · our copy fetched 2026-07-25T06:02:03Z · SHA-256 of that copy begins b31893140631bd06…

timofey-TK2026-07-24pipecatGitHub issuesgithub.com/…/5110
...Nothing reaches the transport — on a phone call this is 20–40 s of dead air until the callee says "Hello?". Observed on pipecat 1.6.0 (telephony, auto_mode=True, default buffer settings...

First seen 2026-07-24 · our copy fetched 2026-07-25T17:50:31Z · SHA-256 of that copy begins 4891230123214ad1… · profile

Quotes run to 30 words around the reported failure and link to the post.Add your call to this entryTake a quote down within 24 hours.

What is measurable

Signalhotato autopsy ./call.wav maps to this mode as detector kind long_response_gap. The silence between the caller finishing and the agent responding. Printed as DEAD AIR at 5 seconds or more, and as LATENCY SPIKE between 2 and 5 seconds.
EstablishesThe seconds of silence between the caller finishing and the agent answering, timestamped in the call.
What else it establishes, and what your own trace settles
  • Dead air is visible in a single mixed channel, so this one is measurable on a mono recording as well as a split one.

What your trace settles

  • Your latency spans for that turn name where the seconds went: transcription, the model, or speech synthesis.
TierTier 3 · single mixed channel: one mixed channel still measures what silence shows, and each finding carries its measured confidence. hotato is MIT and runs locally, getting started.

Status history

The record has carried one status since it opened: open, reported and still open where it was reported. A move lands here with the link, the quote and the date that show it.

Discussion

Reader discussion of this mode: what fixed it and what did not. The reports above are attributed and linked; a comment is a comment.

Open this discussion on GitHub

The record

Ids, digests, every link this entry stands on, and how to take a quote down
Atlas idVFA-2026-0006
Mode idpat_361aece86cc7a9daf0c4ab02
Content digestsha256:361aece86cc7a9daf0c4ab020c6ae08c175afc9761ad16357d5a7260b27e7073
First reported2026-07-24
Last reported2026-07-24
First seen by the atlas2026-07-24T22:10:52Z
Last re-checked2026-07-24T22:10:52Z
Reported onpipecat
SourcesGitHub issues
Scope1 independent public report across 1 source. This entry states where the mode has been reported; where else it can occur is what the next report settles.
References
  1. reporthttps://github.com/pipecat-ai/pipecat/issues/5110 · timofey-TK · GitHub issues · 2026-07-24
Machine surfacesfeed.jsonfeed.atomfeed.schema.jsonatlas.llms.txt
RemovalIf you wrote something quoted on this page and want it gone, one email to [email protected] does it. The removal path takes the quote, the handle and the link off this page, out of the feeds and out of the llms.txt within 24 hours, and tombstones the id so the entry cannot quietly return at a new address.