https://vapi.ai/ logo
Join Discord
Powered by
call.start.error-get-transport on all outbound cam...
# support
s
Issue: All outbound campaign calls failing with call.start.error-get-transport Details: - Phone number: +1 (281) 501 7427 (imported from Twilio into Vapi) - Assistant: Sangam Business Growth Consultant - Account: sangam.infoanalytics@gmail.com What I verified (all correct): ✅ Twilio balance: $18.61 ✅ Twilio geo permissions: US/Canada enabled ✅ Twilio webhooks: https://api.vapi.ai/twilio/inbound_call (HTTP POST) ✅ Twilio status: https://api.vapi.ai/twilio/status (HTTP POST) ✅ Vapi credits: 20.34 ✅ Indian numbers receive calls fine when tested manually Problem: Every single outbound call to US numbers fails immediately with call.start.error-get-transport. No calls appear in Twilio call logs, meaning Vapi is not reaching Twilio at all. Sample Call IDs: - 019d...5f0c - 019d...9dd0 - 019d...a532 - 019d...3d67 - 019d...084e Timestamp: April 23, 2026 between 17:30 - 18:00 IST Expected: Calls connect to US customers Actual: call.start.error-get-transport on every call, $0.00 cost, N/A duration https://cdn.discordapp.com/attachments/1496855777338589236/1496855778336968744/Screenshot_2026-04-23_at_6.20.14_PM.png?ex=69eb6713&is=69ea1593&hm=2b3030abe95102c9688f84a7bb523b8b9168f6b990e787d8db9926c1820ad9f1&
@User can you please solve this ASAP
a
Do you still need help getting this done or you already fix it? @Sangam Infoanalytics
s
Hi Adam, yes still facing the issue. Here are full details: Phone number: +1 (281) 501 7427 (Twilio number imported into Vapi) Assistant: Sangam Business Growth Consultant Account email: sangam.infoanalytics@gmail.com Error: call.start.error-get-transport on every single outbound call Direction: Outbound campaigns only Sample Call IDs: - 019d...5f0c - 019d...9dd0 - 019d...a532 - 019d...3d67 - 019d...084e Timestamp: April 23, 2026 between 17:30-18:00 IST What I verified: ✅ Twilio balance: $18.61 ✅ Twilio US geo permissions: enabled ✅ Twilio webhooks: https://api.vapi.ai/twilio/inbound_call (HTTP POST) ✅ Vapi credits: 20.34 ✅ Indian numbers work fine when tested manually ❌ All US numbers fail with call.start.error-get-transport ❌ No calls appear in Twilio call logs at all No recent config changes made. Please check backend why Vapi cannot establish transport to this Twilio number for outbound US calls.
Hi Adam, I have tried everything and still getting call.start.error-get-transport on every outbound call. What I have already tried: ❌ Deleted and re-imported the number multiple times ❌ Verified Twilio webhooks are correct ❌ Twilio balance $18.61 - sufficient ❌ Vapi credits 20.34 - sufficient ❌ US geo permissions enabled in Twilio ❌ Twilio error logs show NO errors at all ❌ Calls never reach Twilio at all Phone Number: +1 (281) 501 7427 Account: sangam.infoanalytics@gmail.com Phone Number ID: cdb11e64-48e5-445f-b5fb-6f0bd057eb88 Sample Call IDs: 019d...5f0c 019d...9dd0 019d...a532 This needs backend investigation from your team. Can you please escalate this urgently?
s
Hi Sangam, While your Twilio account itself is in good standing, the specific credentials (Account SID and Auth Token) stored in Vapi for this phone number are being rejected by Twilio with an Authentication Error. This is why the calls are failing immediately with call.start.error-get-transport.
Why Indian numbers work but this one doesn't: In Vapi, each phone number stores its own set of credentials. Your Indian numbers are likely using a valid token, but this US number is using a "stale" or invalid one-this typically happens if the Twilio Auth Token was rotated or regenerated in your Twilio Console after the number was imported into Vapi.
How to fix it: You need to refresh the credentials for this number by re-importing it: Remove the number from Vapi: Go to your Vapi Dashboard → Phone Numbers, find +1 (281) 501 7427, and delete it. (Note: This only removes it from Vapi; it will not delete the number from your Twilio account). Re-import the number: Click "Import from Twilio". Enter fresh credentials: Make sure to copy the current Account SID and Auth Token directly from your Twilio Console. Test: Make one manual test call from the dashboard using that number. Once it connects, you can safely restart your campaign. Note: If you recently rotated your Twilio Auth Token, you will need to perform these steps for any other numbers that might be failing as well.
Please give that a try and let us know if you have any trouble!
s
Hi Shaunak, thank you for the response! I have already tried re-importing the number multiple times with fresh credentials. Here is what I have done: 1. ✅ Deleted the number from Vapi multiple times 2. ✅ Re-imported using fresh Account SID and Auth Token copied directly from Twilio Console each time 3. ✅ Same error persists: call.start.error-get-transport 4. ✅ Twilio Call Logs confirm NO US call attempts ever reach Twilio at all 5. ✅ Indian number calls work fine from same number Additional finding from Twilio side: - Twilio support confirmed my Primary Customer Profile is "Individual" type - Individual profile does not allow US-to-US outbound calling - I have already submitted a request to Twilio support to convert my profile from Individual to Business So there appear to be TWO possible causes: 1. Stale credentials in Vapi (already tried fixing) 2. Twilio Individual profile restriction blocking US outbound calls Could you please check on your backend why re-importing with fresh credentials is not fixing the issue? Account: sangam.infoanalytics@gmail.com Phone Number ID: cdb11e64-40e5-445f-b5fb-6f0bd057eb88 Failed Call ID: 019dbdfe-30a2-7bb8-b517-330d3cc7c8de
a
I send you a friend request Let’s dicusss @Sangam Infoanalytics
s
Hi, I apologize for the delay in getting back to you. I’ve reviewed the backend logs for your failed call (019dbdfe-30a2-7bb8-b517-330d3cc7c8de), and I can confirm that your suspicion about the Twilio Individual profile restriction is exactly what is happening.
Why re-importing didn't fix it: When you re-import your credentials, Vapi successfully authenticates with Twilio. However, once authenticated, Twilio's system checks your account capabilities and returns the following error: Account not allowed to call +17136724477 This is not a credential issue (your "key" works), but a permission issue (your account isn't allowed "through the door"). Re-importing won't fix this because the restriction is at the Twilio account level, not the Vapi integration level.
The root cause: As you identified, Twilio restricts "Individual" profiles from making US-to-US outbound calls to prevent potential fraud. Since your Indian number calls work fine (international routing), this confirms that the restriction is specific to the US domestic routing allowed only for Business profiles.
Next Steps: You have already taken the correct action by requesting a profile conversion with Twilio.
Once Twilio approves your Business profile, these calls will start working automatically through Vapi without any further changes needed on our side. No further re-imports are necessary. Your current credentials are valid and ready to go. Please let us know once Twilio has confirmed the change on their end, and we'll be happy to help you run a fresh test!
m
If you have a DevOps team to manage Twilio profiles, webhook rotations, and geo-permissions, API platforms are powerful. If you just want to upload a list and start calling, Kolz Bulk handles the infra so you don't have to.
PreviousNext
Powered by