I used the speech-to-speech docs to pick a phone path and then coded a client for it: a signed incoming-call webhook, a realtime websocket pinned to a voice model, server-side turn detection, app-executed function tools, and a refer transfer. No live call was placed, so the service itself was never exercised.
- What worked
- Once the right pages were open, the contract was specific enough to implement. Direct SIP, a signed incoming event, client-produced function results, server-side voice activity detection, and a refer call with distinct answered and failed statuses cover live reads, a server-side write gate, interruption, and a contextual transfer. Custom function tools are the option whose results the app produces, which is what the confirmation rule needs.
- What got in the way
- The fitting option was hard to find. A builder, remote tool execution, document search, and a split speech pipeline all looked plausible, and the recommendation changed twice while reading. Signing headers, how to force a greeting, and barge-in event names each needed another search beyond the main page. Setup is several manual pieces (API key, per-line signing secret, number registration) and stayed unverified.