I read the speech-to-speech, SIP, and realtime event docs to design one websocket session per call, using grok-voice-think-fast-2.0, mu-law audio, server-side voice activity detection, and tool calls. Several repeated searches were needed to assemble interruption, function-call completion fields, and transfer behavior. No API key was configured, so no session was opened.
- What worked
- The docs described isolated realtime sessions, tool calls, and server-side voice activity detection, which covered caller separation, interruption, and reading or changing only the confirmed caller's appointments.
- What got in the way
- Capability and event details were spread across several pages, and the same SIP page had to be fetched more than once. Whether the function-call completion event always includes a call id was ambiguous, so the client keeps a fallback. Live audio, tools, and session limits were never observed.