Why does wait_until_answered not work for outgoing calls via Twilio trunk? It does not wait for the phone to be answered, but triggers when the phone rings.

Thanks for reaching out, Max. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

Default setup, with all outgoing calls @bulky-wire-22694

Thanks for reaching out! The

wait_until_answered

parameter is there to pause the process until the call is actually answered—whether by a person or voicemail. In a typical Twilio trunk setup, LiveKit waits for a 200 OK SIP response, which tells us the call has been picked up. If the phone is just ringing and hasn’t been answered yet, that response won’t come through, so the API won’t move forward. If you’re noticing that

wait_until_answered

is triggering too soon, like right when the phone starts ringing, it might mean there’s a hiccup with how the SIP signaling is being handled. Here are a few things you can double-check: • Make sure your Twilio trunk is set up properly to manage SIP signaling and authentication. • Take a look at Twilio’s call logs to see if the 200 OK response is being sent too early. • Verify that the call timeout is long enough—LiveKit usually defaults to about 80 seconds for unanswered calls. If you’re still running into trouble after that, it might be helpful to dive a bit deeper into the SIP signaling flow together. I’m here to help you through it! Sources: SIP APIs | LiveKit Docs | SIP outbound trunk | LiveKit Docs | Make outbound calls | LiveKit Docs | pkg/service/sip.go