https://vapi.ai/ logo
Join Discord
Powered by
Twilio Error on Vapi callback
# support
m
I've imported a phone number from twilio but when I call it I've a 404 error response from vapi: Got HTTP 404 response to https://api.vapi.ai/twilio/inbound_call phone_id is 
600d4a9c-496b-4678-8536-49982c4d6fb8
Response body:
Copy code
{
  "message": "Cannot GET /twilio/inbound_call?AccountSid=...&ApiVersion=2010-04-01&CallSid=CA6b25622035ecde8b4e1f674b6c06a058&CallStatus=ringing&Called=%2B33644607776&CalledCity=&CalledCountry=FR&CalledState=&CalledZip=&Caller=%2B33645862300&CallerCity=&CallerCountry=FR&CallerState=&CallerZip=&Direction=inbound&From=%2B33645862300&FromCity=&FromCountry=FR&FromState=&FromZip=&StirVerstat=TN-Validation-Passed-A&To=%2B33644607776&ToCity=&ToCountry=FR&ToState=&ToZip=",
  "error": "Not Found",
  "statusCode": 404
}
v
message has been deleted
@marem It seems like there might be an issue with the webhook URL configured in Twilio for the inbound call handling. The error indicates that the VAPI server is not able to find the correct endpoint to process the inbound call. To resolve this, please ensure that the webhook URL set in Twilio for incoming calls is correct and points to a valid VAPI endpoint that can handle the request. You should verify the URL in your Twilio console and make sure it matches the expected endpoint provided by VAPI for handling incoming calls. If you need assistance with finding the correct endpoint or configuring your Twilio number with VAPI, please provide me with the necessary context or ask support for more info on this.
You can continue this conversation by mentioning me in the message.
m
Issue is because the webhook callback https://api.vapi.ai/twilio/inbound_call has been created with 
GET
instead of 
POST
@Vapi sorry I see this issue is tagged as solved but it's not.
v
@marem I apologize for the confusion. Let's address the issue with the webhook callback method. The Twilio webhook for inbound calls should indeed be set to use the 
POST
method, as Twilio typically sends data via 
POST
requests to ensure that all the necessary information is securely transmitted. Please check your Twilio configuration for the phone number 
+33644607776
and update the webhook for incoming calls to use the 
POST
method instead of 
GET
. You can do this in your Twilio dashboard under the phone number settings. Once you have updated the configuration to use 
POST
, try calling the number again to see if the issue is resolved. If you continue to experience problems or need further assistance, please let me know, and I'll be happy to help.
m
Yes, that's what I did to fix the issue. But this might happen again when I import a phone with vapi. Vapi should set the correct HTTP method when importing the phone
s
m
Now it's ok because I updated it by myself. (HTTP webhook method was GET instead of POST). But given that vapi configures the wehbook, it should also change the HTTP method if not correct, no?
s
it might have not happened by mistake, will check fpr others.
m
@Shubham Bajaj I retagged it as unsolved. I think you have cases where the callback is not setup correctly if it was already existing. If callback already exists with GET, it's not updated to POST. You should open an issue on product side. I fear we might have the issue with new customers on our side, as our product is self service
d
I have the same error
It's giving me a error 404
and it's saying that the connection wasn't able to be done
I made it like this but the error stay
@Sahil do you know about this?
Please keep me updated on the fix for this problem
s
please create a new ticket for this.
no we onboarded new users it didn't happened but as reported by Digi i will check. Because your issue is resolve i am closing this ticket.
d
Nvm I got it solved
2 Views
PreviousNext
Powered by