VAPI not sending data to server URL for inbound ca...
# supporth
Himanshu
08/26/2024, 4:51 PMI have set a server url at assistant level. I have also set the same assistant for the twilio inbound phone number. When I call the assistant from the VAPI portal directly things are working fine and webhook is triggered but when call is made to inbound phone number it does not work.
Assistant ID - 3ee7e5fc-65f8-46a9-94d6-b441c917a267
v
Vapi
08/26/2024, 4:52 PMmessage has been deleted
Vapi
08/26/2024, 4:52 PM@Himanshu
It sounds like there might be an issue with the configuration for the inbound calls. Since you've mentioned that the assistant works fine when called directly from the VAPI portal, but not when calling the inbound phone number, we should check a few things:
1. Ensure that the assistant ID
3ee7e5fc-65f8-46a9-94d6-b441c917a267Vapi
08/26/2024, 4:52 PMYou can continue this conversation by mentioning me in the message.
h
Himanshu
08/26/2024, 5:07 PMAssistant ID is associated properly with phone num.
When I call the number, call is been picked.
Server URL is also reachable and configured properly to handle request.
Call log is not there.
Himanshu
08/26/2024, 7:20 PMAssistant ID is associated properly with phone num.
When I call the number, call is been picked.
Server URL is also reachable and configured properly to handle request.
Call log is not there.
v
Vapi
08/26/2024, 7:20 PM@Himanshu
It's good to hear that the assistant ID is correctly associated with the phone number, the call is being picked up, and the server URL is reachable. Since the call log is not available, it's challenging to diagnose the issue without more information.
Here are a few additional steps you can take:
1. Double-check the webhook configuration for the inbound phone number to ensure it's pointing to the correct server URL.
2. Make sure that the server handling the webhook is properly logging incoming requests. This can help identify if the request from the inbound call is reaching the server.
3. If possible, test the server endpoint with a tool like Postman or cURL to simulate an inbound call and see if the server responds as expected.
4. Review any security settings or access control lists (ACLs) that might be preventing the webhook from being triggered.
5. If your server requires authentication, ensure that the necessary credentials are provided and are correct.
If after these checks the issue still persists, it may be necessary to contact VAPI support for a more in-depth investigation. They might be able to provide insights from the backend that are not visible to us here. Please ask support for more info on this.
h
Himanshu
08/27/2024, 8:59 AMHow to contact support team
v
Vapi
08/27/2024, 8:59 AM@Himanshu
To contact the support team, you can typically do so through the following channels:
1. **Support Portal**: Visit the official support portal of the service provider and submit a ticket or request.
2. **Email**: Send an email to the support team's official email address.
3. **Phone**: Call the support hotline if one is available for immediate assistance.
4. **Live Chat**: Use the live chat feature on the service provider's website for real-time help.
5. **Community Forums**: Post your issue in the community forums where other developers or support team members can assist you.
Since I don't have the specific contact details for the VAPI support team, please check the official website or the documentation provided to you for the exact contact methods available. If you have access to a customer dashboard, support contact options might also be listed there.
If you need further assistance finding the contact information, please let me know, and I'll do my best to assist you.
s
Shubham Bajaj
08/27/2024, 1:26 PM@Himanshu your assistantId is binded with phone number so won't send assistant request server event.
Shubham Bajaj
08/27/2024, 1:26 PMif your talking about other server events then share the call id and events not triggered.