Inbound calls to imported Twilio phone number is f...
# support
d
I have a phone number which I purchased from Twilio and have been using it to make outbound calls in the app via TwiML app configuration. Now we're looking into possibilities to make inbound calls answered by AI assistant. Steps I did: 1. I've detached the number from the previous TwiML app configuration and cleared everything under webhooks. 2. Imported phone number via VAPI dashboard (even tried via API). Phone number is successfully imported into VAPI 3. Assigned assistant to the imported phone number 4. Double checked that Twilio phone number has correct webhook https://api.vapi.ai/twilio/inbound_call and https://api.vapi.ai/twilio/status for statuses. When I call to the phone number, it fails with "Your server rejected
assistant-request
webhook. Error: Request failed with status code 404" I don't see any logs in VAPI dashboard too. Any ideas what I'm missing? https://cdn.discordapp.com/attachments/1370265772823416872/1370265773163151400/image.png?ex=681edef2&is=681d8d72&hm=ef60d87d223f6c7a0810d0a56a9b1970f8a28109f23e29b6199c6447d88b5b2b& https://cdn.discordapp.com/attachments/1370265772823416872/1370265773716541460/image.png?ex=681edef2&is=681d8d72&hm=8375bd88f5d169cb7862d850da85ce487f6082bdbb140020a468aaf5f5373ce9&
v
Thanks for sharing the detailed steps you've taken and the error message you're seeing. From what you've described, it looks like you've set up the webhooks correctly and assigned the assistant, but the inbound call to the Vapi webhook is returning a 404 error and there are no logs appearing in the Vapi dashboard. At this time, I don't have access to specific information or documentation that explains why this 404 error is occurring or what additional steps might resolve it. If you have any more details or changes in behavior, feel free to share them.
Thanks for sharing the detailed steps you've taken and the error message you're seeing. From what you've described, it looks like you've set up the webhooks correctly and assigned the assistant, but the inbound call to the Vapi webhook is returning a 404 error and there are no logs appearing in the Vapi dashboard. At this time, I don't have access to specific information or documentation that explains why this 404 error is occurring or what additional steps might resolve it. If you have any more details or changes in behavior, feel free to share them.
Thanks for sharing the detailed steps you've taken and the error message you're seeing. From what you've described, it looks like you've set up the webhooks correctly and assigned the assistant, but the inbound call to the Vapi webhook is returning a 404 error and there are no logs appearing in the Vapi dashboard. At this time, I don't have access to specific information or documentation that explains why this 404 error is occurring or what additional steps might resolve it. If you have any more details or changes in behavior, feel free to share them.
Thanks for sharing the detailed steps and configuration you've set up for your Twilio number and VAPI integration. From what you've described, it looks like you've correctly detached the number from previous configurations, imported it into VAPI, assigned an assistant, and set the webhook URLs as required. The 404 error message on the
https://api.vapi.ai/twilio/inbound_call
webhook and the absence of logs in the VAPI dashboard suggest that something might not be connecting as expected, but without additional documentation or logs, it's difficult to pinpoint the exact cause. Your configuration details and error responses are clear, and it sounds like you've covered the main setup steps.
Thanks for sharing the detailed steps and configuration you've set up for your Twilio number and VAPI integration. From what you've described, it looks like you've correctly detached the number from previous configurations, imported it into VAPI, assigned an assistant, and set the webhook URLs as required. The 404 error message on the
https://api.vapi.ai/twilio/inbound_call
webhook and the absence of logs in the VAPI dashboard suggest that something might not be connecting as expected, but without additional documentation or logs, it's difficult to pinpoint the exact cause. Your configuration details and error responses are clear, and it sounds like you've covered the main setup steps.
Thanks for providing such a detailed description of your setup and the steps you've taken. From what you've shared, it looks like you've correctly configured your Twilio number and set the webhook URLs as required. The 404 error on the
https://api.vapi.ai/twilio/inbound_call
endpoint typically means that the server couldn't find the requested resource, which could point to a misconfiguration or an issue with how the webhook is set up or being called. Since you don't see any logs in the VAPI dashboard, it suggests that the request might not be reaching the expected handler within VAPI, or the endpoint isn't active for some reason. Double-checking the exact webhook URL, ensuring the assistant is properly assigned, and confirming that the phone number import process completed successfully are all good steps. If everything appears correct, it may be helpful to review any recent changes or settings that could affect how inbound calls are routed to your assistant. Let me know if you have any other details or if anything changes after rechecking these areas!
Thanks for sharing the detailed steps and configuration you've set up for your Twilio number and VAPI integration. From what you've described, it looks like you've correctly detached the number from previous configurations, imported it into VAPI, assigned an assistant, and set the webhook URLs as required. The 404 error message on the
https://api.vapi.ai/twilio/inbound_call
webhook and the absence of logs in the VAPI dashboard suggest that something might not be connecting as expected, but without additional documentation or logs, it's difficult to pinpoint the exact cause. Your configuration details and error responses are clear, and it sounds like you've covered the main setup steps.
Thanks for providing such a detailed description of your setup and the steps you've taken. From what you've shared, it looks like you've correctly configured your Twilio number and set the webhook URLs as required. The 404 error on the
https://api.vapi.ai/twilio/inbound_call
endpoint typically means that the server couldn't find the requested resource, which could point to a misconfiguration or an issue with how the webhook is set up or being called. Since you don't see any logs in the VAPI dashboard, it suggests that the request might not be reaching the expected handler within VAPI, or the endpoint isn't active for some reason. Double-checking the exact webhook URL, ensuring the assistant is properly assigned, and confirming that the phone number import process completed successfully are all good steps. If everything appears correct, it may be helpful to review any recent changes or settings that could affect how inbound calls are routed to your assistant. Let me know if you have any other details or if anything changes after rechecking these areas!
Thanks for providing such a detailed description of your setup and the steps you've taken. From what you've shared, it looks like you've correctly configured your Twilio number and set the webhook URLs as required. The 404 error on the
https://api.vapi.ai/twilio/inbound_call
endpoint typically means that the server couldn't find the requested resource, which could point to a misconfiguration or an issue with how the webhook is set up or being called. Since you don't see any logs in the VAPI dashboard, it suggests that the request might not be reaching the expected handler within VAPI, or the endpoint isn't active for some reason. Double-checking the exact webhook URL, ensuring the assistant is properly assigned, and confirming that the phone number import process completed successfully are all good steps. If everything appears correct, it may be helpful to review any recent changes or settings that could affect how inbound calls are routed to your assistant. Let me know if you have any other details or if anything changes after rechecking these areas!
d
Tried setting up via Twilio SIP guide and have same error message
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!
d
@Kings_big💫 - Call ID: there is none, I don't see any requests in VAPI dashboard - Time: 2025-05-09 10:34:47 UTC - Assistant pickup inbound call - An automated reply: "Your server rejected
assistant-request
webhook. Error: Request failed with status code 404"
k
Looking into it
s
I have the same problem and contacted support by email. You can get some information from the report from Twilio. This information may help to narrow down the problem.
d
Do you mean contact Twilio support for more insight? Twilio call itself is marked as completed, but the TwiML response contains error message
Copy code
<Response>
    <Say>Your server rejected `assistant-request` webhook. Error: Request failed with status code 404</Say>
</Response>
I don't know where to look for verbose error report 😦
s
@daniyar.chambylov @Sullidor can you share your phone number ID? You've assigned a server URL to your phone number, and VAPI is rejecting requests for the assistant. I need your phone number ID to confirm this.
s
I have sent the ID by e-mail to support@vapi.ai. But if it helps, here again: The Phone Number ID is a800ea57-f671-4dc1-b9c4-17195607cd01
d
@Shubham Bajaj The Phone Number ID: e9cffb27-73b6-452f-9ccd-1010110479d9 @Sullidor already have emailed VAPI support, no response yet.
c
Hey, can you try again? There is no server URL assigned to your phone number. I guess you have made the update, so it should work by now. For reference, you can check the below screenshot. https://cdn.discordapp.com/attachments/1370265772823416872/1370930504186204220/image.png?ex=68214a06&is=681ff886&hm=f06a2bfa56a41c04209a76d688d1db22f4e9f7c46c756877cbfc3404deb7bf6b&
d
HI, still getting same error message.
s
I am also still getting the same error message. I have compared the number with a working number from a customer account. Via the dashboard and also via the API. Both look identical to me (apart from the different IDs and times). I had already tested the number with another account. I have the same problem there.
I have now bought a new number and released the number in question. The new number has worked as it should so far.
d
Same, new number works, but previously owned numbers do not. @Shubham Bajaj @Kings_big💫
@Shubham Bajaj @Kings_big💫 any updates?
c
We recommend continuing with the new number for now.