openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@a1b49c4b20

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-05-06 08:21:55 +00:00
parent a36bc765db
commit 987dbfc9f4
3 changed files with 14 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "2eaf8ad7126b373a57ec10b169b49cd63780096e",
"syncedAt": "2026-05-06T08:18:25.843Z"
"sha": "a1b49c4b20027c42abbfeeeafbc34fa4379d3ef0",
"syncedAt": "2026-05-06T08:19:54.997Z"
}

12
docs/plugins/google-meet.md
View File

@ -1668,16 +1668,16 @@ participant:
- Run `openclaw voicecall tail` and check that Twilio webhooks are arriving at
the Gateway.
- Run `openclaw logs --follow` and look for the Twilio Meet sequence: Google
Meet delegates the join, Voice Call starts the phone leg, Google Meet waits
`voiceCall.dtmfDelayMs`, sends DTMF with `voicecall.dtmf`, waits
`voiceCall.postDtmfSpeechDelayMs`, then requests intro speech with
`voicecall.speak`.
Meet delegates the join, Voice Call stores and serves pre-connect DTMF TwiML,
Voice Call serves realtime TwiML for the Twilio call, then Google Meet requests
intro speech with `voicecall.speak`.
- Re-run `openclaw googlemeet setup --transport twilio`; a green setup check is
required but does not prove the meeting PIN sequence is correct.
- Confirm the dial-in number belongs to the same Meet invitation and region as
the PIN.
- Increase `voiceCall.dtmfDelayMs` if Meet answers slowly or the call transcript
still shows the prompt asking for a PIN after DTMF was sent.
- Increase `voiceCall.dtmfDelayMs` from the 12-second default if Meet answers
slowly or the call transcript still shows the prompt asking for a PIN after
pre-connect DTMF was sent.
- If the participant joins but you do not hear the greeting, check
`openclaw logs --follow` for the post-DTMF `voicecall.speak` request and
either media-stream TTS playback or the Twilio `<Say>` fallback. If the call

11
docs/plugins/voice-call.md
View File

@ -902,10 +902,11 @@ If Voice Call is green but the Meet participant never joins, check the Meet
dial-in number, PIN, and `--dtmf-sequence`. The phone call can be healthy while
the meeting rejects or ignores an incorrect DTMF sequence.
Google Meet passes the Meet DTMF sequence and intro text to `voicecall.start`.
For Twilio calls, Voice Call serves the DTMF TwiML first, redirects back to the
webhook, then opens the realtime media stream so the saved intro is generated
after the phone participant has joined the meeting.
Google Meet starts the Twilio phone leg through `voicecall.start` with a
pre-connect DTMF sequence. PIN-derived sequences include the Google Meet plugin's
`voiceCall.dtmfDelayMs` as leading Twilio wait digits. The default is 12 seconds
because Meet dial-in prompts can arrive late. Voice Call then redirects back to
realtime handling before the intro greeting is requested.
Use `openclaw logs --follow` for the live phase trace. A healthy Twilio Meet
join logs this order:
@ -914,7 +915,7 @@ join logs this order:
- Voice Call stores pre-connect DTMF TwiML.
- Twilio initial TwiML is consumed and served before realtime handling.
- Voice Call serves realtime TwiML for the Twilio call.
- The realtime bridge starts with the initial greeting queued.
- Google Meet requests intro speech with `voicecall.speak` after the post-DTMF delay.
`openclaw voicecall tail` still shows persisted call records; it is useful for
call state and transcripts, but not every webhook/realtime transition appears