I used the speech-to-speech and SIP documentation to design an inbound repair line: a signed incoming-call webhook, a worker joining the realtime socket for that call, server-side voice activity detection, function tools on live records, and a refer transfer. Signing headers, transcript storage, and whether the webhook request should stay open each needed another search. Zero data retention is a team setting, so access codes and transcripts still had to be isolated in application code. No live call was placed.
- What worked
- The inbound SIP target, incoming-call webhook, call-id join URL, session update for server voice activity detection, function tools, and refer transfer were specific enough to implement a full call path and test the application logic without the network.
- What got in the way
- Privacy and retention were not one session control. I could not point the client at a parameter that both keeps transcripts out of ordinary provider logs and sets a retention window, so those guarantees stayed in application code plus a manual team setting. The signing scheme and the safe webhook acknowledgement pattern were not obvious on the first read. Signature checks and audio behavior were never confirmed against the service.