Hey, I can help with this. What you're seeing calls stuck at "call.in.progress Twilio completed" typically means Twilio has hung up its leg of the call, but Vapi never received (or didn't process) the final webhook to close the session. This usually points to a webhook delivery failure, a Vapi server-side hang, or a Twilio status callback not reaching Vapi's endpoint. Quick question: did anything change in the last 3–4 hours a Twilio number config update, a webhook URL change, or a new assistant/function deployment?