Half-duplex barge-in ignored

open

1 independent reportacross 1 sourceon 1 stacklast reported 2026-05-18

What this is

While the agent is speaking, the system never listens for the caller's speech, so any attempt to interrupt or clarify goes completely unheard until the agent finishes.

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

Evidence

shaan7542026-05-18asteriskcommunity.asterisk.orgcommunity.…rver/112943

...is speaking. If a user interrupts mid-response — for example to clarify something or barge in — their speech is ignored completely. Attempted Solution To support full-duplex conversations and barge-in,...

First seen 2026-05-18 · our copy fetched 2026-07-25T18:22:26Z · SHA-256 of that copy begins f12647c28351e516… · 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	`hotato autopsy ./call.wav` maps to this mode as detector kind `overlap_while_agent_talking`. Printed as BARGE-IN: the caller took the floor and the agent kept speaking, reported with the overlap in seconds. Needs the caller and agent on separate channels.
Establishes	The seconds of overlap where the caller had taken the floor and the agent kept speaking, with the timestamp in the call where it started. What else it establishes, and what your own trace settles The same recording produces the same overlap on every run, so the number is comparable across builds. What your trace settles Your pipeline trace at that timestamp names what held the floor: the interrupt handler, the VAD threshold, or the realtime API's own turn logic. Whether the caller meant to interrupt is a judgement about the conversation; the measurement covers who held the floor and for how long.
Tier	Tier 1 · dual-channel audio: caller and agent separated at capture, so overlap and timing are facts of the recording, exact to the sample. 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
Post hangup pipeline wedge blocks future calls	open	reported on asterisk
Barge-in teardown race	acknowledged	measured by the same detector (overlap_while_agent_talking)
Async interruption response misattribution	open	measured by the same detector (overlap_while_agent_talking)

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-0037`
Mode id	`pat_9ab7abaf398d1913ec649d1d`
Content digest	`sha256:9ab7abaf398d1913ec649d1dd754b0014cda6a80497f5f7d0e1240aa6d98d8db`
First reported	`2026-05-18`
Last reported	`2026-05-18`
First seen by the atlas	`2026-05-18T09:40:39.757Z`
Last re-checked	`2026-05-18T09:40:39.757Z`
Reported on	asterisk
Sources	community.asterisk.org
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.asterisk.org/t/enabling-barge-in-with-audiosocket-connection-between-asterisk-and-python-server/112943 · shaan754 · community.asterisk.org · 2026-05-18
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.