Outbound calls failing immediately in my org. Org ID: 10c4461e-416b-4f25-8ba1-be9bc30414c9 Ended reason: call.start.error-get-transport Symptoms: no ring, $0 cost, no transcript/logs generated. Tried multiple fresh Vapi-provisioned numbers and multiple US destination numbers. Failing call IDs: - 019d5488-4e31-7bbe-9a61-b7688699df56 - 019d5489-73f1-7bbe-9a69-cd957d8d6760 - 019d548d-1a23-7bb9-95b0-0559497990e6 - 019d5493-9141-7aab-9ba0-02946dd3cee4 Need help fixing Vapi telephony transport for outbound PSTN.

The error

call.start.error-get-transport

means Vapi could not retrieve transport information to start your outbound call. To resolve this, please contact Vapi support and provide your call IDs and organization ID for investigation. Example message to support:

Org ID: 10c4461e-416b-4f25-8ba1-be9bc30414c9
Call IDs: [list of failing call IDs]
Error: call.start.error-get-transport

This will help the support team quickly identify and address the issue. Source: - [Call Ended Reason Codes – Vapi Documentation](https://docs.vapi.ai/calls/call-ended-reason)

Hey, I can fix this. That call.start.error-get-transport usually comes from a broken or misconfigured telephony provider setup. I’ll quickly check your Vapi transport, numbers, and routing, and get outbound calls working again. Send me your config. @hyperdrive137

That error usually means your outbound call never successfully connects to a telephony transport, which explains the instant failure, no ringing, and zero logs—it’s not even reaching the carrier layer. I’d focus on verifying your transport configuration (provider selection, credentials, and region routing) and ensuring your Vapi org has an active outbound PSTN path properly linked to the numbers you’re using. Also worth checking if there’s a mismatch between your call settings and the provisioned transport (e.g., SIP vs native carrier). I can help you troubleshoot this directly and pinpoint the root cause quickly. Are you currently routing outbound via a custom SIP trunk or using Vapi’s default carrier setup? @hyperdrive137

Hi, For outbound calling, please import your own phone number from a provider such as Twilio, Telnyx, Vonage, or another SIP provider into Vapi. At the moment, Vapi-provisioned numbers support inbound calling only, so they cannot be used for outbound call flows. Once your provider number is imported, outbound calls should work as expected.

I have imported a phone number from Twilio to my VAPI account. However, when I am trying to make an outbound call, it's giving me an error. Here are the details: 1. Ended: Call.start.error get transport 2. outboundPhoneCall Call ID - 019e2d50-d222-799d-a9c0-6018d344ca3e

Hi, Apologies for the delay in response. We investigated the outbound call issue for call ID

019e2d50-d222-799d-a9c0-6018d344ca3e

. From our side, Vapi queued and dispatched the call correctly, however Twilio rejected the call immediately before it could ring. This is why you are seeing the error:

Call.start.error get transport

. The rejection message indicates:

Account not allowed to call +13155333019

Since this is happening across multiple outbound attempts, it points to a Twilio account-level restriction. The two most common causes are: • Trial Twilio account — Trial accounts can only call verified numbers. Please either upgrade the account or verify the destination number in your Twilio console. • Geo Permissions disabled — Twilio requires outbound calling permissions per region. Please check

Voice → Settings → Geo Permissions

in your Twilio console and ensure the United States is enabled. Kind regards, Support Team