You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/plugins/voice-call.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -211,6 +211,11 @@ each carrier call should start with fresh context, for example reception,
211
211
booking, IVR, or Google Meet bridge flows where the same phone number may
212
212
represent different meetings.
213
213
214
+
Generated session keys are scoped under the configured voice agent, for example
215
+
`agent:main:voice:15550001234` for per-phone sessions or
216
+
`agent:main:voice:call:<call-id>` for per-call sessions. Explicit session keys
217
+
provided by an inbound route or outbound call request are preserved as-is.
218
+
214
219
## Realtime voice conversations
215
220
216
221
`realtime` selects a full-duplex realtime voice provider for live call
@@ -233,7 +238,7 @@ Current runtime behaviour:
233
238
-`realtime.agentContext.enabled` is default-off. When enabled, Voice Call injects a bounded agent identity, system prompt override, and selected workspace-file capsule into the realtime provider instructions at session setup.
234
239
-`realtime.fastContext.enabled` is default-off. When enabled, Voice Call first searches indexed memory/session context for the consult question and returns those snippets to the realtime model within `realtime.fastContext.timeoutMs` before falling back to the full consult agent only if `realtime.fastContext.fallbackToConsult` is true.
235
240
- If `realtime.provider` points at an unregistered provider, or no realtime voice provider is registered at all, Voice Call logs a warning and skips realtime media instead of failing the whole plugin.
236
-
- Consult session keys reuse the stored call session when available, then fall back to the configured `sessionScope` (`per-phone` by default, or `per-call` for isolated calls).
241
+
- Consult session keys reuse the stored call session when available, then fall back to the agent-scoped configured `sessionScope` (`per-phone` by default, or `per-call` for isolated calls).
0 commit comments