VAPI giving Unknow error while making outbound cal...
# support
d
I tried to make outbound calls and VAPI is giving unknown error. Please let me know how to fix it ec1d2409-1b59-47a2-998a-d96422ce7c8e 945f2474-9ce6-416a-bf09-f85e2680785f 54739e47-21fe-477e-ac54-b3ccdf5acc9e d219f71e-61cb-448b-bf12-6e5b47d1b085
v
Hi there! I see you're experiencing an "unknown error" when making outbound calls with VAPI. I don't have access to your specific account details or logs to diagnose the exact cause of the error with your provided call IDs. However, I can definitely help with common causes and troubleshooting steps for this issue! Based on the information I found, there are several potential causes for the "unknown error" during VAPI outbound calls: 1. **Concurrency Limits**: You may have reached the concurrency limit for outbound calls, which can result in "unknown" statuses in call logs. [Increasing your concurrency limit](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336054616206348479) might resolve this. 2. **Twilio Configuration Issues**: The error could occur if Twilio isn't sending the expected websocket message or if there are [permission issues with your Twilio account](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336432457943351358). 3. **SIP Trunk Configuration**: Misconfiguration in SIP trunk settings or network connectivity issues can cause errors like "sip gateway failed to connect" which might appear as an unknown error in some cases. 4. **VAPI Service Issues**: There might be a [service disruption with VAPI's SIP service](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339440148806504458) affecting outbound calls. Here are some troubleshooting steps you can take: 1. **Check Twilio Logs**: Review the Twilio logs for the specific call IDs to understand what went wrong. 2. **Verify VAPI Settings**: Make sure your VAPI settings haven't been altered and are still configured correctly. 3. **Test Network Connectivity**: Ensure there are no network issues causing timeouts. 4. **Check for Stuck Calls**: Look for any stuck or hung calls in your dashboard.
5. **Contact VAPI Support**: If the issue persists, contact VAPI support with your organization ID and the call IDs you've provided. This will help them investigate the specific issue with your calls. Would you like me to provide more details on any of these potential causes or troubleshooting steps? Sources: - [Discord thread about concurrency limits](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336054616206348479) - [Discord thread about Twilio configuration issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336432457943351358) - [Discord thread about VAPI service issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339440148806504458)
a
🔵 16:46:51:124 Call
ec1d2409-1b59-47a2-998a-d96422ce7c8e
Waited 300s But Transport Never Connected.
Twilio failed to connect with us in the required time, resulting in "transport never connected" and eventually none of your calls connected to the customer. You have to check with Twilio support regarding this.
a gentle reminder to continue this thread.