2% of our call are never initiated
# support
d
Here are only two example between last 100 calls, but it is an error that happen every several times a day. At Twilio logs we don't see any error, just status call: no-answer At our backend logs we received the assistant-request event and immediately after the hang-up event, after that the status-update event with status ended and endedReason: call.in-progress.error-providerfault-transport-never-connected call id: 743364c0-aadf-4164-996a-406dd6661134, 449c0e4d-2791-4834-a924-c63ca9e1c121 The experience of the client is quite bad because they think that the number of the company is broken or unavailable.
v
Based on your logs, the error indicates a transport connection failure between Twilio and Vapi. This typically happens when Twilio fails to establish a connection with Vapi's servers. The most likely cause is a misconfigured Twilio webhook. Please verify that:
Copy code
1. Your Twilio webhook URL is correctly pointing to Vapi's endpoint
2. Your Twilio account has proper permissions and is in good standing
3. There are no network connectivity issues between Twilio and Vapi
For further investigation, contact support with your call IDs for a more in-depth analysis of the logs. Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1343208312249913397) - [Discord Channel](https://discord.com/channels/1211482211119796234/1334137548162728040) - [Discord Channel](https://discord.com/channels/1211482211119796234/1336995626604564551)
Based on your logs, the error indicates a transport connection failure between Twilio and Vapi. This typically happens when Twilio fails to establish a connection with Vapi's servers. The most likely cause is a misconfigured Twilio webhook. Please verify that:
Copy code
1. Your Twilio webhook URL is correctly pointing to Vapi's endpoint
2. Your Twilio account has proper permissions and is in good standing
3. There are no network connectivity issues between Twilio and Vapi
For further investigation, contact support with your call IDs for a more in-depth analysis of the logs. Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1343208312249913397) - [Discord Channel](https://discord.com/channels/1211482211119796234/1334137548162728040) - [Discord Channel](https://discord.com/channels/1211482211119796234/1336995626604564551)
Based on your logs, the error indicates a transport connection failure between Twilio and Vapi. This typically happens when Twilio fails to establish a connection with Vapi's servers. The most likely cause is a misconfigured Twilio webhook. Please verify that:
Copy code
1. Your Twilio webhook URL is correctly pointing to Vapi's endpoint
2. Your Twilio account has proper permissions and is in good standing
3. There are no network connectivity issues between Twilio and Vapi
For further investigation, contact support with your call IDs for a more in-depth analysis of the logs. Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1343208312249913397) - [Discord Channel](https://discord.com/channels/1211482211119796234/1334137548162728040) - [Discord Channel](https://discord.com/channels/1211482211119796234/1336995626604564551)
s
@David Jurado Twilio isn't connecting with us within the required time, causing your calls to end. The provider fault transport never connected. As you mentioned, no answer indicates the user isn't picking up your call. šŸ”µ 07:20:27:119 CallId
743364c0-aadf-4164-996a-406dd6661134
Worker Ending Call With Reason call.in-progress.error-providerfault-transport-never-connected. Error: { "code": "ETIMEDOUT", "message": "timeout" }
d
How long is the timeout? Do you have any ideas or suggestions for trying to resolve this issue?
k
You have to write an email to the Twilio team. The timeout is usually between 7.5 seconds or 15 seconds. For more details on why they didn't connect in the required time, you have to write them.
Sorry, this is something not in our control, even yours. It's Twilio and then Infra system.