AMD premature timeout before answer

fixed

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

What this is

On outbound calls, the answering-machine-detection timer starts before the callee has actually answered, so ring or early media triggers a false timeout that the system wrongly treats as a voicemail greeting.

Status fixed: an upstream thread for this mode has been closed as completed.

Evidence

mirandamon2026-06-22livekittwilioGitHub issuesgithub.com/…/6187

Summary On outbound SIP calls with carrier early media, AMD emits uncertain / detection_timeout with speech_duration=0 before the callee answers, so the agent falls through and treats a voicemail...

First seen 2026-06-22 · our copy fetched 2026-07-28T13:08:10Z · SHA-256 of that copy begins e404d12836c0a7df… · 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

Date	State	What moved it
2026-08-08	openfixed	issue closed (completed) evidence dated 2026-08-05

Mode	Status	Shares
Tool call mid-utterance audio truncation	open	reported on livekit; reported on twilio; reported on github
Endpoint misdetection	acknowledged	reported on livekit; reported on twilio; reported on github
Barge-in teardown race	acknowledged	reported on livekit; reported on twilio; reported on github

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-0019`
Mode id	`pat_6e3cef201759ffed346906ea`
Content digest	`sha256:6e3cef201759ffed346906ea6e1fb875ba1fb819be358f8612ba2ec379eeed56`
First reported	`2026-06-22`
Last reported	`2026-06-22`
First seen by the atlas	`2026-06-22T19:34:32Z`
Last re-checked	`2026-06-22T19:34:32Z`
Reported on	livekittwilio
Sources	GitHub issues
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.
Resolved	A stored artifact shows this mode closed upstream: 2026-08-05. The quote and the date behind each move are in the status history above.
References	reporthttps://github.com/livekit/agents/issues/6187 · mirandamon · GitHub issues · 2026-06-22
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 [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.