call.in-progress.error-providerfault-transport-nev...
# support
c
Hey I do like ~200 calls per day all inbound. I get this " call.in-progress.error-providerfault-transport-never-connected" error at LEAST 5 times every day. I spoke with twilio and they said it was not their fault lol (can also confirm after working with their tech team it is in fact not their fault). Can someone look into this and resolve it? Or at least tell me why its occuring.
v
The error
call.in-progress.error-providerfault-transport-never-connected
means the call transport connection to the provider was never established, and this is surfaced by Vapi when the provider (like Twilio) reports a connection failure or when there are network issues between Vapi and the provider.
Since Twilio has confirmed it's not on their end, the issue may be related to network connectivity, configuration, or intermittent service issues between Vapi and your telephony provider. Actionable next step: Please contact Vapi support with your
call_id
, account email, and any relevant call logs so they can investigate the root cause and help resolve the issue ([Vapi Support](https://docs.vapi.ai/support)). Source: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason)
The error
call.in-progress.error-providerfault-transport-never-connected
means the call transport connection to the provider was never established, and this is surfaced by Vapi when the provider (like Twilio) reports a connection failure or when there are network issues between Vapi and the provider.
Since Twilio has confirmed it's not on their end, the issue may be related to network connectivity, configuration, or intermittent service issues between Vapi and your telephony provider. Actionable next step: Please contact Vapi support with your
call_id
, account email, and any relevant call logs so they can investigate the root cause and help resolve the issue ([Vapi Support](https://docs.vapi.ai/support)). Source: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason)
c
caleb@thesavants.ai
bea4ea03-0bcf-489d-be93-56fad10ca50d
e3d86b9d-7fb4-43d0-a427-692259b1f568
7f672ff6-f1a0-4b5d-9eb8-dfb59befaf2e
call ids of ones from last few hours
v
The error
call.in-progress.error-providerfault-transport-never-connected
means that the call transport connection to the provider was never established.
This can happen due to network connectivity issues, configuration problems, or intermittent service disruptions between Vapi and your telephony provider. Since Twilio has confirmed the issue is not on their end, it may be related to other factors in the call flow or infrastructure. I understand how frustrating it is to encounter this error multiple times a day, especially with your high call volume. If you have already checked your network and configuration, and the issue persists, it may require a deeper look into the specific call flow or environment to identify the root cause.
The error
call.in-progress.error-providerfault-transport-never-connected
means that the call transport connection to the provider was never established.
This can happen due to network connectivity issues, configuration problems, or intermittent service disruptions between Vapi and your telephony provider. Since Twilio has confirmed the issue is not on their end, it may be related to other factors in the call flow or infrastructure. I understand how frustrating it is to encounter this error multiple times a day, especially with your high call volume. If you have already checked your network and configuration, and the issue persists, it may require a deeper look into the specific call flow or environment to identify the root cause.
Next step: Please email [support@vapi.ai](support@vapi.ai) with your
call_id
(
bea4ea03-0bcf-489d-be93-56fad10ca50d
), your account email (
caleb@thesavants.ai
), and any relevant call logs. This will allow the Vapi team to investigate the root cause of the
call.in-progress.error-providerfault-transport-never-connected
error and help resolve the issue. You can also reference the [Vapi Support page](https://docs.vapi.ai/support) for more contact options. Tip: Including as much detail as possible (timestamps, frequency, network setup) will help support diagnose the problem faster. Sources: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)
Next step: Please email [support@vapi.ai](support@vapi.ai) with your
call_id
(
bea4ea03-0bcf-489d-be93-56fad10ca50d
), your account email (
caleb@thesavants.ai
), and any relevant call logs. This will allow the Vapi team to investigate the root cause of the
call.in-progress.error-providerfault-transport-never-connected
error and help resolve the issue. You can also reference the [Vapi Support page](https://docs.vapi.ai/support) for more contact options. Tip: Including as much detail as possible (timestamps, frequency, network setup) will help support diagnose the problem faster. Sources: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)
Please send your
call_id
(such as
bea4ea03-0bcf-489d-be93-56fad10ca50d
,
e3d86b9d-7fb4-43d0-a427-692259b1f568
,
7f672ff6-f1a0-4b5d-9eb8-dfb59befaf2e
), your account email (
caleb@thesavants.ai
), and any relevant call logs to [Vapi Support](https://docs.vapi.ai/support) for investigation.
This error means the call transport connection to the provider was never established, and Vapi support can help determine the root cause. Providing these details will allow the technical team to review your specific cases and work toward a resolution. Sources: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)
Please send your
call_id
(such as
bea4ea03-0bcf-489d-be93-56fad10ca50d
,
e3d86b9d-7fb4-43d0-a427-692259b1f568
,
7f672ff6-f1a0-4b5d-9eb8-dfb59befaf2e
), your account email (
caleb@thesavants.ai
), and any relevant call logs to [Vapi Support](https://docs.vapi.ai/support) for investigation.
This error means the call transport connection to the provider was never established, and Vapi support can help determine the root cause. Providing these details will allow the technical team to review your specific cases and work toward a resolution. Sources: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)
Thank you for providing your account email and recent call IDs. The next step is to contact Vapi support directly with these details so they can investigate the root cause of the
call.in-progress.error-providerfault-transport-never-connected
errors in your account. You can reach support here: [Vapi Support](https://docs.vapi.ai/support). This will allow the technical team to review your logs and provide a resolution specific to your situation. Sources: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)
Thank you for providing your account email and recent call IDs. The next step is to contact Vapi support directly with these details so they can investigate the root cause of the
call.in-progress.error-providerfault-transport-never-connected
errors in your account. You can reach support here: [Vapi Support](https://docs.vapi.ai/support). This will allow the technical team to review your logs and provide a resolution specific to your situation. Sources: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)
c
I just checked the call_id and it was reported as twilio-reported-customer-misdialed by twilio. So, you are good to ignore it.
c
What does that mean ?
v
"twilio-reported-customer-misdialed" means Twilio detected that the customer dialed an invalid or incomplete number, so the call could not be completed. This is not a system error, but rather an issue with the number dialed by the customer, and can generally be ignored as suggested by support ([Vapi documentation](https://docs.vapi.ai/calls/call-ended-reason)). Quick question: Have you noticed if this misdial error is happening with specific numbers or is it random? Source: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason)
"twilio-reported-customer-misdialed" means Twilio detected that the customer dialed an invalid or incomplete number, so the call could not be completed. This is not a system error, but rather an issue with the number dialed by the customer, and can generally be ignored as suggested by support ([Vapi documentation](https://docs.vapi.ai/calls/call-ended-reason)). Quick question: Have you noticed if this misdial error is happening with specific numbers or is it random? Source: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason)
c
Hey Caleb, checking if this is resolved/solved for you?