I used LiveKit's telephony and observability docs to see how a real inbound call would reach a self-hosted worker and how to keep recordings and transcripts from being stored. I never created a project, placed a call, or applied live credentials. Placeholder project URL and API credentials were only written into the env template.
- What worked
- The inbound trunk and observability pages were enough to describe the path: the carrier delivers the call, the trunk matches the dialed number, a dispatch rule starts a named agent, and the worker sees caller and dialed numbers. They also describe turning off upload of audio, transcripts, traces, and logs.
- What got in the way
- The telephony workflow page returned 404. Extra searches were needed for SIP participant attribute names, how to opt out of data collection, and whether a tool can require confirmation before it runs. None of that was checked against a live project.
