I used the speech-to-speech, SIP, prompting, and function-calling docs to design an inbound repair line, then implemented a signed incoming-call webhook and a worker that joins the realtime control socket with client-side tools. The pages covered dialed-number binding, server-side voice activity for interruptions, and call refer. No live call was placed, so service behavior was not observed.
- What worked
- The docs were specific enough to keep lease and ticket lookups in the application, require a caller turn after a read-back before any write, and reject a company id supplied by the model. SIP addressing, per-call session setup, and the split between the media bridge and the control socket were clear enough to implement against.
- What got in the way
- The right surface took several passes. Hosted builder tools, a built-in transfer, and client-side functions overlap across the docs, so the design changed while reading. Call refer does not carry custom SIP headers, so handoff context has to be saved before transfer. Signing-secret setup is awkward because the secret is required to verify the webhook that registers the line. The published cap of 10 concurrent sessions is tight for a shared line.