fix(voice-call): delegate cli calls to gateway

docs/cli/voicecall.md

@@ -10,6 +10,11 @@ title: "Voicecall"
 
 `voicecall` is a plugin-provided command. It only appears if the voice-call plugin is installed and enabled.
 
+When the Gateway is running, operational commands (`call`, `start`,
+`continue`, `speak`, `dtmf`, `end`, and `status`) are sent to that Gateway's
+voice-call runtime. If no Gateway is reachable, they fall back to a standalone
+CLI runtime.
+
 Primary doc:
 
 - Voice-call plugin: [Voice Call](/plugins/voice-call)

docs/plugins/voice-call.md

@@ -610,6 +610,11 @@ openclaw voicecall latency                      # summarize turn latency from lo
 openclaw voicecall expose --mode funnel
 ```
 
+When the Gateway is already running, operational `voicecall` commands delegate
+to the Gateway-owned voice-call runtime so the CLI does not bind a second
+webhook server. If no Gateway is reachable, the commands fall back to a
+standalone CLI runtime.
+
 `latency` reads `calls.jsonl` from the default voice-call storage path.
 Use `--file <path>` to point at a different log and `--last <n>` to limit
 analysis to the last N records (default 200). Output includes p50/p90/p99