openclaw - 💡(How to fix) Fix [voice-call] Reduce opening turn gap variability on outbound calls [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#56181Fetched 2026-04-08 01:43:59
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
closed ×1commented ×1locked ×1
RAW_BUFFERClick to expand / collapse

The opening turn gap (time between recipient greeting ending and Imogen's first word) measured 1.8–4.4s in testing. Target is ~1.5s consistent. A first-turn state machine and VAD fallback gate were implemented but not fully tuned before this work was paused.

Current state:

  • Range: 1.8–4.4s (4.4s is an outlier)
  • Opening talk-over: none (protected)
  • Implemented: idle → wait_remote_speech → wait_remote_stop → fired → normal state machine
  • Fallback gate: 1400ms elapsed + 650ms quiet

Next steps:

  • Lower VAD threshold from 0.45 toward 0.35–0.40
  • Tune fallback timing gate
  • Test against real IVR systems (not just synthetic agents) to validate timing doesn't cause DTMF-before-prompt issues

extent analysis

Fix Plan

To reduce the opening turn gap, we will implement the following steps:

  • Lower the VAD threshold
  • Tune the fallback timing gate

Code Changes

# Before
VAD_THRESHOLD = 0.45
FALLBACK_GATE_ELAPSED = 1400  # ms
FALLBACK_GATE_QUIET = 650  # ms

# After
VAD_THRESHOLD = 0.375  # adjusted threshold
FALLBACK_GATE_ELAPSED = 1200  # ms
FALLBACK_GATE_QUIET = 550  # ms

Configuration Changes

  • Update the state machine to use the new VAD threshold and fallback gate timings
  • Test the updated state machine against real IVR systems to validate the timing

Verification

  • Measure the opening turn gap after implementing the changes
  • Verify that the gap is consistently around 1.5s
  • Test for DTMF-before-prompt issues with real IVR systems

Extra Tips

  • Monitor the system's performance and adjust the VAD threshold and fallback gate timings as needed
  • Consider implementing additional logging to track the state machine's transitions and timing metrics.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING