Twilio x N8N x VAPI
# support
s
I've got a lot of calls using twilio that are not going through with ended reason "unknown". I'm sending the calls at 1 every 10s. Twilio says they can handle 1 cps. Is this a vapi thing?
v
The "unknown" ended reason typically occurs when Twilio fails to connect with VAPI servers within the required time. According to [VAPI documentation](https://docs.vapi.ai/calls/call-ended-reason), this indicates an unexpected error occurred. The most common fix is to check your webhook configuration in Twilio:
Copy code
xml
<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Redirect method="POST">https://api.vapi.ai/twilio/inbound_call</Redirect>
</Response>
Ensure this is correctly set up in your Twilio configuration. Sources: - [VAPI Call Ended Reason Documentation](https://docs.vapi.ai/calls/call-ended-reason) - [Discord Discussion on Webhook Configuration](https://discord.com/channels/1211482211119796234/1340864767941672960)
The "unknown" ended reason typically occurs when Twilio fails to connect with VAPI servers within the required time. According to [VAPI documentation](https://docs.vapi.ai/calls/call-ended-reason), this indicates an unexpected error occurred. The most common fix is to check your webhook configuration in Twilio:
Copy code
xml
<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Redirect method="POST">https://api.vapi.ai/twilio/inbound_call</Redirect>
</Response>
Ensure this is correctly set up in your Twilio configuration. Sources: - [VAPI Call Ended Reason Documentation](https://docs.vapi.ai/calls/call-ended-reason) - [Discord Discussion on Webhook Configuration](https://discord.com/channels/1211482211119796234/1340864767941672960)
u
Hi @Shaneng
k
To help track down this issue, could you share one or two: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
2 Views