Agent dispatch latency before connect

open

1 independent reportacross 1 sourceon 2 stackslast reported 2026-06-09

What this is

The agent process is dispatched to an inbound call so many seconds after it arrives that the caller has already hung up before the agent joins.

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

Evidence

Zaheer_Abbas2026-06-09livekittwiliocommunity.livekit.iocommunity.…ung-up/1393

...was dispatched ~8s after the INVITE — and ~2.5s after the caller had already hung up. Why we think the delay is dispatch-side: this was 1 of 208 inbound calls...

First seen 2026-06-09 · our copy fetched 2026-07-25T18:25:17Z · SHA-256 of that copy begins 65d16ea3044802b0… · profile

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

What is measurable

Signal	This 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.
Establishes	Every 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.
Tier	Atlas record: every field on this page traces to a fetched public artifact. 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.

Mode	Status	Shares
Endpoint misdetection	acknowledged	reported on livekit; reported on twilio; reported on livekit_forum
Silence timeout teardown during processing gap	open	reported on livekit; reported on twilio; reported on livekit_forum
Barge-in teardown race	acknowledged	reported on livekit; reported on twilio; reported on livekit_forum

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 id	`VFA-2026-0012`
Mode id	`pat_975de5c29c2b6c63233c33e9`
Content digest	`sha256:975de5c29c2b6c63233c33e9ecd6e68d69f631fa7dd68f38ed5ce4c6efeb0643`
First reported	`2026-06-09`
Last reported	`2026-06-09`
First seen by the atlas	`2026-06-09T20:00:13.948Z`
Last re-checked	`2026-06-09T20:00:13.948Z`
Reported on	livekittwilio
Sources	community.livekit.io
Scope	1 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	reporthttps://community.livekit.io/t/inbound-sip-call-agent-job-dispatched-8s-after-the-invite-reached-livekit-cloud-caller-had-already-hung-up/1393 · Zaheer_Abbas · community.livekit.io · 2026-06-09
Machine surfaces	feed.json feed.atom feed.schema.json atlas.llms.txt
Removal	If 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.