Title: All outbound PSTN calls fail with Call.start.error get transport — empty logs Body: Every outbound call fails identically. Logs tab empty, $0.00 cost, phone never rings. Web tester works fine. Setup: Org: 6f2c0371-364e-49ec-b7db-b1be4f074fc2 Twilio number: +1 938 356 3672 (US1) Destination: +60 (Malaysia, Twilio geo permissions enabled, caller ID verified) Already ruled out: Voice clone (tested stock Aria — same error) ElevenLabs key backgroundSound URL (disabled) SSML parsing (toggled both ways) Brand new bare-bones assistant from scratch — same error Vapi status page green Account credit fine (PAYG, $3.96) Sample failed call IDs: [019de471-6ef9-7ee6-9daf-7af9f8f3806f] [019de46d-630f-766a-b2de-93e77079a711] [019de46b-b02c-7ff4-8e7d-4334ad144c76] Can someone check server logs?

Hey Thiru, I've dealt with this exact transport error before on Vapi outbound calls. The empty logs + $0.00 cost combo usually points to a SIP trunk or geo-routing issue on Vapi's side not your config. Happy to jump in and help debug. A few quick questions: • Are you using a Vapi-owned number or imported Twilio? • What transport are you setting in the assistant — WebRTC or SIP? Drop me a text and we can get this sorted fast. @THIRU.V