KM
12/03/2025, 11:56 AMVapi Support Bot
12/03/2025, 11:57 AMcall.start.error-get-transport means there was a problem retrieving transport information when starting the call.
Since this is affecting all outbound calls and the call never connects, the recommended next step is to contact Vapi support and provide your Call ID (019ae38f-47d1-7336-867d-e5fb2b1244ef) for investigation.
You can reference the [call ended reason documentation](https://docs.vapi.ai/calls/call-ended-reason) for more details.
Tip: Include your organization ID and a brief description when reaching out to support for faster resolution.
Source:
- [Call Ended Reason Documentation](https://docs.vapi.ai/calls/call-ended-reason)KM
12/04/2025, 7:33 AMuwieuwe4
12/04/2025, 10:59 AMKM
12/05/2025, 10:17 AMChiranjeet Mishra
12/05/2025, 10:20 AM019ae38f-47d1-7336-867d-e5fb2b1244ef, we’re seeing the following internal error on our side:
🔴` 09:33:30:127 Couldn't initiate outbound call transport and queue for call 019ae38f-47d1-7336-867d-e5fb2b1244ef. Error: Couldn't Create Twilio Call. Twilio Error: Authenticate`
This means Vapi wasn’t able to authenticate with Twilio when trying to start the outbound leg. It’s not related to your assistant configuration, but to the telephony transport step.
A few things to check on your side while we continue investigating:
1. Twilio credentials in Vapi
- Re-save your Twilio Account SID and Auth Token in the provider/phone number settings (in case the token was rotated or invalidated).
2. Twilio account status
- Confirm in the Twilio console that the project is active, has sufficient balance/credit, and outbound calling is allowed for your region and numbers.
3. From number configuration
- Make sure the Twilio number you’re using for outbound is still valid, SMS/voice-enabled, and not restricted.