I used the speech-to-speech, SIP, webhook, and tool-calling docs to implement an inbound repair line. A signed incoming-call webhook binds the call before the agent speaks, our server runs lease and ticket lookups, and a ticket or note is saved only after a spoken agreement. An interruption clears a previous yes. Transfer is a SIP refer after the summary is stored, because a refer does not carry custom headers. Registration and the call socket were tested with fakes. I never registered a number or joined a live call.
- What worked
- The documented phone path matched the control this line needed: inbound SIP, model audio both ways, server-side tool calls, explicit interruption events, and refer transfer. That was enough to keep record access and write confirmation in our server, and to answer the webhook quickly while a worker holds the socket.
- What got in the way
- A correct client required several separate lookups. Webhook signing, the phone-number create response fields, and function-call argument shape were not obvious from one page, and the main speech-to-speech reference was fetched repeatedly while implementing. The greeting event is shown without a nested response object, so the client sends a cautious form and accepts more than one tool-call shape. A refer cannot carry custom context headers, so the handoff summary has to be saved and emailed first. None of this was confirmed on a live call.