Zoom Contact Center skill pack for Contact Center apps, web embeds, and native mobile SDK integrations. Use for lifecycle patterns, engagement context/state handling, campaigns, callbacks, and version-drift troubleshooting.
中文简介正在准备中。当前显示原文说明。
Zoom AI Services Voice Agent V2 for real-time microphone conversations over WebSocket, including VAD, PCM audio, speech-to-speech or text responses, interruption handling, and function tools. Use for interactive voice agents; not one-shot media summarization or live meeting transcription.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Use Voice Agent for an interactive microphone conversation where the service transcribes speech, runs an AI turn, and streams spoken or text output in real time.
Current API audit: The V2 route, session shape, event stream, and error recovery below were verified against the official sample and live connections on 2026-10-20. The documented V1 surface was verified on the same /v2/ws/ route with a different subprotocol and body.
Match the session body to the subprotocol: V2 uses listen / think / speak, while the documented V1 surface uses OpenAI-style audio.input / audio.output. A mismatch returns error.code = shape_switch_not_allowed.
wss://api.zoom.us/v2/ws/aiservices/voice-agent/live
Sec-WebSocket-Protocol: voice-agent.zoom.v2
x-api-key: $ZOOM_AI_SERVICES_API_KEY
Required key scope: aiservices:read:voice-agent:admin.
Two subprotocols are live on that route, and they are not interchangeable:
| Surface | Subprotocol | Session body | Server events |
|---|---|---|---|
| V2, official sample | voice-agent.zoom.v2 | listen / think / speak | flat JSON events |
| V1, docs live-mode page | voice-agent.zoom.v1 | OpenAI-style audio.input / audio.output | {type, payload} envelope |
The documented upgrade path wss://api.zoom.us/v2/aiservices/voice-agent/live (without /ws/) returned HTTP 404 on 2026-10-20 for every subprotocol tried, including voice-agent.zoom.v1. The OpenAPI catalog lists GET /aiservices/voice-agent/live, but both working sockets are under /v2/ws/aiservices/....
Both surfaces accept Authorization: Bearer with either an API key or a Zoom AI Services JWT; V2 was also verified with x-api-key. The official sample reads the credential from ZOOM_API_KEY; this skill uses ZOOM_AI_SERVICES_API_KEY to distinguish it from Build-platform JWT pairs. Use one name in your deployment.
Keep the key server-side. A browser WebSocket cannot set x-api-key, so use a server-side relay:
browser microphone WebSocket -> trusted /live relay -> api.zoom.us Voice Agent
The relay must validate Origin and Host, request voice-agent.zoom.v2, inject the key upstream, enforce frame-size and backpressure limits, and never expose the key to the browser.
The first upstream client frame must be session.update:
{
"type": "session.update",
"session": {
"type": "realtime",
"listen": {
"transcription": { "language": "en" },
"format": { "type": "pcm16", "rate": 16000 }
},
"think": {
"provider": { "type": "zoom", "model": "gemma-4" },
"instructions": "You are an AI assistant interacting with a user through spoken conversation."
},
"speak": {
"format": { "type": "pcm16" },
"voice": "ariel"
}
}
}
The official sample uses gemma-4. Treat model availability as deployment-specific and confirm it through session.updated; an unconfigured model returns a non-fatal error event and the socket stays open.
speak is optional; omitting it defaults to voice jenna at 16 kHz. Valid voice IDs are alex, ariel, ava, brooke, hazel, jenna, mark, reid, scott, and tony. Input transcription accepts only en; ja and en-US were both rejected on 2026-10-20.
Function tools are declared under think.tools as OpenAI-compatible function definitions. Tool results are returned with conversation.item.create using item.type = "function_call_output", followed by response.create.
session.created.session.update and wait for session.updated before sending audio.input_audio_buffer.append frames containing base64 PCM16 LE mono audio. The official sample sends 20 ms frames at 16 kHz.input_audio_buffer.speech_started, stop local playback, send response.cancel with the active response.id, then send conversation.item.truncate with item_id and audio_end_ms. Verified: cancel produces response.done with status cancelled.response.done, inspect response.status; cancelled, failed, and incomplete responses must not be treated as successful playback.response.create with no audio produces a spoken turn, which is useful for a connectivity check.Important server events include:
session.created, session.updatedinput_audio_buffer.speech_startedconversation.item.input_audio_transcription.deltaconversation.item.input_audio_transcription.completedresponse.createdresponse.output_item.addedconversation.item.addedresponse.content_part.added / .doneresponse.output_audio_transcript.delta / .doneresponse.output_audio.delta / .doneresponse.output_item.doneconversation.item.doneresponse.function_call_arguments.doneresponse.doneerrorV1 emits the same concepts inside a {type, payload} envelope and adds input_audio_buffer.speech_stopped, input_audio_buffer.timeout_triggered, and response.output_text.delta for text-only sessions.
Audio deltas contain base64 PCM16. Read the output rate from the updated session; the official sample defaults to 16 kHz. Maintain a small playback lead, schedule buffers sequentially, and carry odd bytes across chunk boundaries.
404 on the upgrade: wrong path or missing entitlement. Both surfaces use /v2/ws/aiservices/...; the documented /v2/aiservices/... path returns 404.401 / 403: invalid key, missing aiservices:read:voice-agent:admin, or relay auth failure.426: the client did not request a WebSocket upgrade.429: rate limited; retry with backoff.503: service unavailable.error with invalid_request_error: model, voice, language, format, or first-frame violation. The socket stays open; correct the setting and resend session.update.error.code = shape_switch_not_allowed: the session body does not match the negotiated subprotocol.session.update returns first event must be a session.update carrying a realtime session; the socket stays open.还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Zoom Contact Center skill pack for Contact Center apps, web embeds, and native mobile SDK integrations. Use for lifecycle patterns, engagement context/state handling, campaigns, callbacks, and version-drift troubleshooting.
中文简介正在准备中。当前显示原文说明。
Zoom Contact Center SDK for Android. Use for native Android chat/video/ZVA/scheduled callback integrations, campaign mode, service lifecycle, and rejoin handling.
中文简介正在准备中。当前显示原文说明。
Zoom Contact Center SDK for iOS. Use for native iOS chat/video/ZVA/scheduled callback integrations, app lifecycle bridging, rejoin flow, and callback handling.
中文简介正在准备中。当前显示原文说明。
Zoom Contact Center SDK for Web. Use for web chat/video/campaign embeds, engagement event handling, app-context integrations, and Smart Embed postMessage workflows.
中文简介正在准备中。当前显示原文说明。
Zoom AI Services Decisions for typed predicates, constrained classification, ordered scoring, probability-aware routing, and inline image comparison. Use when building or debugging Decisions requests, production x-api-key authentication, standard/pro model selection, Boolean choices, or score-label normalization.
中文简介正在准备中。当前显示原文说明。
Zoom Meeting SDK for Linux - C++ headless meeting bots with raw audio/video access, transcription, recording, and AI integration for server-side automation
中文简介正在准备中。当前显示原文说明。