🚨 OUTBOUND CALLS HARD-FAILING (NO RING) — call.start.error-get-transport We cannot place ANY outbound calls in this org — fails instantly before ringing. - Happens across: Vapi numbers + Twilio + Telnyx - EndedReason: call.start.error-get-transport - Cost: $0 - Even a blank assistant test fails - Re-added credit card; still failing orgId: 286c856b-ee2a-4940-a99c-5125c5555370 Recent failing call IDs: - 019eaa13-db3a-7441-994c-256f42861611 (blank assistant test, Vapi number -> +17473898407) - 019ea817-2441-7002-96bd-b9a16a4a217a (Vapi number retry) - 019ea805-427d-7ddd-b8ab-fdd8350e3ec4 (Telnyx) - 019ea7eb-cb0c-7002-84d1-098f959adc1d (Twilio) Request: Can an engineer please check/reset outbound transport provisioning / telephony entitlement for this org? It looks like transport acquisition is failing globally.

Hi Sid, Thank you for the detailed report — this is really helpful. I've reviewed the failing call IDs and can confirm that the error is occurring at the transport layer, before any telephony provider is even reached. Since this is happening across Vapi numbers, Twilio, and Telnyx (including a blank assistant test), this points to an org-level provisioning issue on our side rather than anything in your configuration. I've escalated this directly to our engineering team with your orgId and call IDs, with a request to check and reset outbound transport provisioning for your account. You don't need to make any changes on your end. I'll follow up as soon as I have an update from the team — we're treating this as high priority. Apologies for the disruption and thanks for your patience!

Thanks Praveen. I apreaciate it. Yes this is high priority and we are losing money by the second! Thanks for you're response.

can you share one more call_id sid?