All Calls failing with call.in-progress.error-prov...
# support
b
Getting these issues for our calls with VAPI numbers and with Twilio numbers. Can someone please help? Here are some call IDs with this issue: 019aa43a-19e4-7009-93f0-de7668813afc 019aa439-4d95-7115-8106-76b86ba91b02 019aa438-95b2-7223-9c69-3c473e8f4c12
v
The error
call.in-progress.error-providerfault-transport-never-connected
means your call provider (like Twilio) failed to establish a connection, often due to provider-side issues.
The best next step is to contact Vapi support with your
call_id
and account email for investigation.
Copy code
text
Please email support@vapi.ai with your call IDs and a description of the issue.
This will help the team review provider logs and assist you directly. Reference: [Vapi call ended reason documentation](https://docs.vapi.ai/calls/call-ended-reason) Source: - [Vapi call ended reason documentation](https://docs.vapi.ai/calls/call-ended-reason)
t
I am having the same error.
j
Same
t
Twilio returns the error of: 31901 - Stream - WebSocket - Connection Timeout
j
Same
t
rip :/
b
Wow, all of you having these issues too.
Unacceptable prod issues
t
💀
h
Same issue…. My clients are NOT happy
j
Seems to be fine now for me
b
Working now too.
Unbelieveable that it happened and no public status/comms for it.
h
Agree…. Has this been a common thing?
Because my clients were not happy and if it is, I’d look at other providers
b
not confident or happy with VAPI. likely will switch for find another solution.
c
Thanks for reporting this issue. Our team noticed some degradation in our SIP server around the time this ticket was submitted, and they resolved the issue immediately. Calls should now be connecting normally. Please let us know if you see this happen again — we’ll be happy to investigate further.
4 Views