Since mondey i have been getting this error it used to work fine i have tried checking twilio and everything seems good on their side also i have tried with different assistant and phone number but it still shows it The Call Id: 019ae3c9-e778-7aa9-8d1b-e38eb15e436b

Thank you for sharing the details and confirming you've checked Twilio and tried different assistants and phone numbers. The error

call.start.error.get-transport

means there was a problem retrieving transport information during call start, which can sometimes be related to Vapi configuration or service status rather than Twilio itself. Could you please check your Vapi dashboard's Call Logs for this Call ID (

019ae3c9-e778-7aa9-8d1b-e38eb15e436b

) and let me know if there are any additional error messages or details shown there? This will help narrow down the root cause and guide the next troubleshooting steps. For reference, you can find more on this error in the [Vapi documentation](https://docs.vapi.ai/calls/call-ended-reason). Source: - [Call ended reason documentation](https://docs.vapi.ai/calls/call-ended-reason)

There is not other detail or message except call.start.error.get-transport

I had the same issue but just with one number I tried to call but worked for the others.

Hey! To help track down this issue, could you share: \- When exactly this happened (the timestamp) \- What response you expected to get \- What response you actually got instead This would really help us figure out what went wrong!