Audio gate cooldown blocks endpoint finalization

acknowledged

2 independent reportsacross 1 sourceon 5 stackslast reported 2026-08-20

What this is

A local audio-level gate stops forwarding the caller's audio to the speech-to-text service after a brief silence cooldown, so the remote signal that would mark the turn finished never arrives and the call stalls.

Status acknowledged: the thread it was reported in was acknowledged upstream.

Evidence

saran-0072026-08-20openai-realtimepipecatGitHub issuesgithub.com/…/5380
...context frame, the service never forwards a single byte of caller audio, and with server-VAD turn detection the session deadlocks: - no audio reaches xAI, so server VAD never emits...

First seen 2026-08-20 · our copy fetched 2026-08-20T01:03:10Z · SHA-256 of that copy begins e6d6fcc3ee4b30dd… · profile

CampbellMBXJ2026-08-07deepgramlivekitsileroGitHub issuesgithub.com/…/2242
...the Deepgram plugin sends to the websocket. Once the 1 second cooldown elapses with no audio above its RMS threshold, the plugin stops sending audio entirely (KeepAlive still goes out,...

First seen 2026-08-07 · our copy fetched 2026-08-07T18:11:29Z · SHA-256 of that copy begins 6aef0a7fdf83dbbd… · 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

SignalThis record stands on its own linked sources. To put a number on your own call, hotato autopsy ./call.wav reads a recording you already have and ranks the timing incidents in it.
EstablishesEvery report below links to the original post and names the handle that wrote it; the quote is at most 30 words around the reported failure.
What else it establishes, and what your own trace settles
  • The status changes only when a re-check stores the evidence link, the quote and the date behind the change.
  • Every timestamp comes from the fetched artifact it describes, recorded with the sha256 of the response body it was read from.

What your trace settles

  • Reproducing the mode on your own stack is the next step: the reports below carry the configuration each reporter was running.
TierAtlas record: every field on this page traces to a fetched public artifact. hotato is MIT and runs locally, getting started.

Status history

DateStateWhat moved it
2026-08-20openacknowledgedissue closed (completed) evidence dated 2026-08-20

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-0028
Mode idpat_bb19437bf013452afc5c56f0
Content digestsha256:bb19437bf013452afc5c56f008b2df328e33b81d8f290352ea1dc23993eb59b8
First reported2026-08-07
Last reported2026-08-20
First seen by the atlas2026-08-07T17:57:59Z
Last re-checked2026-08-20T00:20:18Z
Reported ondeepgramlivekitopenai-realtimepipecatsilero
SourcesGitHub issues
Scope2 independent public reports 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/5380 · saran-007 · GitHub issues · 2026-08-20
  2. reporthttps://github.com/livekit/agents-js/issues/2242 · CampbellMBXJ · GitHub issues · 2026-08-07
Machine surfacesfeed.jsonfeed.atomfeed.schema.jsonatlas.llms.txt
RemovalIf you wrote something quoted on this page and want it gone, one email to atlas-remove@hotato.dev 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.