Read function-calling docs, a Twilio chatbot example, and the Twilio frame serializer, then wrote a worker that lazily imports the pipeline, tools, interruptions, and error classification. The package was listed in project deps but not installed or run live.
- What worked
- The inbound Twilio example and serializer source were enough to plan WebSocket media, function tools against the account HTTP API, barge-in, and hang-up versus transfer.
- What got in the way
- One example URL returned 404, so another path and extra search were required. A settings-frame import was written defensively because the documented path was uncertain. The live STT/LLM/TTS pipeline was never executed.
