I keep getting Error 400 when I try to test my ass...
# support
d
My assistant can't hear me, and it just won't work from Vapi's end. I've tried making new assistants completely fresh from scratch, but nothing helps. It demands a server URL but I don't have one to give!
v
message has been deleted
@Daniel M I'm sorry to hear that you're experiencing issues with your assistant not being able to hear you. Let's try to troubleshoot this together. Firstly, the server URL is typically required for the assistant to know where to send and receive data. If you don't have a server URL, you might need to set up a server where your assistant can process the voice data. This could be a local server on your network or a cloud-based server. If setting up a server is not feasible for you, we can explore other options or configurations that might be causing the issue. Could you please provide more details about the steps you've taken so far and any specific error messages you're receiving? This will help me assist you better.
You can continue this conversation by mentioning me in the message.
d
Can we set up a free server URL that will actually work? I've already got a make.com process for the Vapi AI, but it's still shitting the bed.
@Vapi
v
@Daniel M I understand that you're looking for a solution to set up a server URL for your VAPI assistant and that you've been experiencing issues despite having a process in place with make.com. While VAPI itself does not provide server hosting services, there are several free options you can consider for setting up a server URL: 1. **Heroku**: Offers a free tier for small applications, which can be suitable for development and testing purposes. 2. **Glitch**: Allows you to write, share, and remix code for apps, which can be used to host server-side code for your assistant. 3. Vercel or **Netlify**: These platforms are more geared towards static sites but can also handle serverless functions, which might be useful depending on your assistant's architecture. Once you have your server set up on one of these platforms, you will receive a server URL that you can use with your VAPI assistant. If you're still having trouble after setting up your server, please provide more specific details about the errors or issues you're encountering, and I'll do my best to assist you further. If you need detailed guidance on setting up a server on any of these platforms, please let me know, and I can provide step-by-step instructions.
d
Is this absolutely mandatory? I used to use Vapi a few months ago and I never had this issue at all with server URLs. Is this a new thing? @Vapi
v
@Daniel M I apologize for any confusion. If you were able to use VAPI previously without providing a server URL, it's possible that there have been changes to the system or that your previous setup was using a default or pre-configured server URL. To clarify, the server URL is typically used for VAPI to communicate with your backend services. It's where VAPI sends HTTP GET and POST requests to process the voice data and execute functions based on your assistant's logic. If this requirement seems new to you, it could be due to an update in VAPI's configuration or a change in how your assistant is set up. It's important to check the current documentation or release notes for any updates that might have occurred since you last used the service. If you believe that your setup should work without a server URL or if you're unsure about the changes, I recommend reaching out to VAPI's support team for more specific guidance on your situation. They would be able to provide the most accurate information regarding any recent changes or requirements. Would you like me to assist you with anything else at this moment?
s
@Daniel M can you share call id and along with it explain what you have been doing now steps followed to make the call?
2 Views