call.start.error-get-transport
# support
v
Thank you for sharing the detailed information and error code call.start.error-get-transport. This error means there was a problem retrieving transport information when starting the call (according to the documentation I have found). To help diagnose further: Can you confirm if your Twilio credentials (Account SID and Auth Token) are correctly configured and up to date in your Vapi dashboard? Incorrect or missing credentials can prevent Vapi from establishing the required transport for outbound calls. Let me know, and I can guide you on the next steps! Source: - [Call ended reasons documentation](https://docs.vapi.ai/calls/call-ended-reason)
f
Yes, Twilio credentials are perfectly fine. I deleted/created the phone number many times to make sure the connection was not the problem.
c
Hi francodarget, The error
call.start.error-get-transport
usually indicates an issue with retrieving transport information at the start of a call. Here are a few things to check and try: 1. Twilio Credentials: Double-check your Twilio Account SID and Auth Token in the Vapi dashboard to ensure they are correctly entered and up to date. This is crucial for authentication. 2. Twilio Account Status: Make sure your Twilio account is active with sufficient balance and that outbound calling is permitted for your region and numbers. 3. Phone Number Configuration: Verify that the Twilio number used for outbound calls is active, voice-enabled, and unrestricted. If these configurations are correct and the issue persists, it might be worth reaching out to support with your Call ID for further investigation, as there may be other underlying issues with the configuration or integration. You can also review [this guide on call ended reasons](https://docs.vapi.ai/calls/call-ended-reason) for additional insights.
3 Views