We did a call to about 20 calls and 99% are getting unknown error. Call ID: 242ee19e-4466-44c0-9e8a-45307a5948dc
v
Vapi Support Bot
04/01/2025, 3:23 AM
Hi there! I see you're experiencing an "unknown-error" in 99% of your calls. That's definitely frustrating! 👀
I'm unable to determine the exact cause for your specific Call ID without access to the actual logs. However, I can help explain what this error means and provide troubleshooting steps.
Based on the information I found, "unknown-error" in Vapi can occur for several reasons:
1. **Concurrency Limits**: You might be hitting your concurrency limit for outbound calls. According to [information I found](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336054616206348479), reaching this limit can cause calls to have an 'unknown' status in call logs.
2. **Twilio and Websocket Issues**: The error can occur when "Twilio isn't sending the websocket" especially for unanswered or hung-up calls, as noted in [this source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336407849806462976).
3. **System Outages**: According to [this information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334279837581443215), system outages can result in calls ending without the reason being updated correctly.
4. **11labs Model Issues**: If you're using 11labs, the "flash_model" might be causing the error. [This source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335277468805758986) suggests changing the model to "turbo" might help.
Here are some troubleshooting steps:
1. **Check Concurrency Limits**: Review your application to ensure it's not making more simultaneous calls than your plan permits.
2. **Verify SIP Configuration**: If applicable, ensure your SIP URI is correctly formatted and your network allows SIP protocol traffic.
3. **Investigate External Service Integration**: If you're using Twilio or 11Labs, check their configuration.