Hi I am ready to start deployment our system, we were ready today for the launch but when I import a number from twilio to have more than 10 outbound calls per day, WE CANNOT MAKE IT WORK.  We dont have NO Logs from twilio, so we cant debug there. Just this error from VAPI: "call.start.error-get-transport" I cannot make a call so no logs on twilio, twilio has fund, is verified, has geo properly set up. So we dont know whats going on

Thanks for sharing the details. The error

"call.start.error-get-transport"

usually points to a configuration issue with the transport (e.g., Twilio) in your Vapi setup. Could you confirm: Have you double-checked that your Vapi call request includes the correct phone number ID and assistant ID, and that your assistant's transport configuration is set to use Twilio? Sometimes missing or incorrect IDs can cause this error. Let me know, and I can guide you on what to check next! Sources: - [Vapi Call Ended Reason Documentation](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi API Reference: Create Call](https://docs.vapi.ai/api-reference/calls/create?explorer=true)

I am trying to call from vapi it self and I get this https://cdn.discordapp.com/attachments/1430707488499568750/1430708271953612923/image.png?ex=68fac269&is=68f970e9&hm=0035ab66228fae6c806271c25a1523fbcf52536bb13aca9866c8413187de5a41&

Where's your twillio account based? I think this is a twillio configuration problem

@EMMANUEL Account is US base, for US numbers, and its working properly in our CRM, so its working.

Try using kixie to call the number.

Hi allanandresch, If you're encountering the error

call.start.error-get-transport

, it indicates an issue retrieving transport information during the call start. Here are some possible steps to resolve it: 1. **Verify Transport Configuration**: Ensure your transport configuration is correctly set in your application. For example:

json
   {
     "transport": {
       "provider": "vapi.websocket",
       "audioFormat": {
         "format": "pcm_s16le",
         "container": "raw",
         "sampleRate": 16000
       }
     }
   }

2. **Check Integration Credentials**: Confirm the validity of any API keys or credentials for your telephony provider (e.g., Twilio or Vonage). 3. **Review Provider Logs**: Check your telephony provider's logs for connectivity issues or errors that might affect the transport setup. You might find additional insights by referring to the [Call Ended Reasons documentation](https://docs.vapi.ai/calls/call-ended-reason).