openclaw - 💡(How to fix) Fix Realtime voice calls remain active after caller hangup [1 participants]

Bundled realtime voice-call sessions can remain active after the caller hangs up. In the realtime handler, Twilio stop and WebSocket close currently close the realtime bridge, but the call is only finalized when the bridge closes with reason error. A normal hangup therefore does not emit call.ended and the call can remain in activeCalls until maxDurationSeconds fires.

• onClose(reason): only emits terminal call event for reason === "error"

TL;DR

Emit call.ended with reason completed when Twilio sends realtime stream stop or on normal realtime WebSocket close to finalize the call.

Guidance

• Review the proposed fix branch (fix/realtime-voice-hangup-finalize) and verify that it addresses the issue by checking the updated realtime-handler.ts file.
• Test the fix using the provided command: docker run --rm -v /home/zss/openclaw:/src -w /src openclaw:local ./node_modules/.bin/vitest run extensions/voice-call/src/webhook/realtime-handler.test.ts.
• Ensure the existing once-only guard is maintained to prevent double finalization.
• Consider retrying the PR from siegelz:fix/realtime-voice-hangup-finalize to openclaw:main to integrate the fix.

Example

No code snippet is provided as the issue already includes a proposed fix branch with the necessary changes.

Notes

The fix relies on the realtime-handler.ts file and the Twilio stop and WebSocket close events. The provided test command can be used to verify the fix.

Recommendation

Apply the workaround by emitting call.ended with reason completed when Twilio sends realtime stream stop or on normal realtime WebSocket close, as proposed in the fix branch. This should resolve the issue of bundled realtime voice-call sessions remaining active after the caller hangs up.