Phone call provider closed websocket.
# support
p
So far, I was able to make calls with my phone number provided by Vonage. I have started creating a make.com scenario to automated the calls based on a database, and for some reason I dont hear the assistant in it. To verify, I have double checked within VAPI with the same assistant and phone number. The same thing happened. The phone rings, I can pick it up, Vonage logs say that the phone call was succesful, but I don't hear the assistant anymore. Lately all of the Ended Reasons are the same: Phone call provider closed websocket.
v
message has been deleted
@Porculus Araneus It sounds like you're experiencing an issue with the audio from the assistant not being transmitted during the calls. Since you've confirmed that the calls are connecting successfully but the assistant's voice isn't heard, let's check a few things: 1. **Assistant Configuration**: Ensure that the assistant's voice configuration is set up correctly with the custom voice you've specified. If there have been any changes or updates to the voice provider or voice ID, this could affect the audio output. 2. **Websocket Connection**: The "Phone call provider closed websocket" message indicates that there might be an issue with the websocket connection used for streaming audio. Check if there have been any changes in the network configuration or if there are any errors in the logs related to the websocket connection. 3. **Audio Source**: Verify that the audio source or the text-to-speech (TTS) engine is functioning properly. If the TTS engine isn't generating audio as expected, this could result in silence during the call. 4. **Make.com Scenario**: Review the make.com scenario to ensure that it's correctly configured to use the assistant and that it's not encountering any errors when triggering the calls. 5. **VAPI Logs**: Look into the detailed logs provided by VAPI for any errors or warnings that could give more insight into why the audio isn't being transmitted. If you've already checked these and the issue persists, it may be necessary to reach out to VAPI support for further assistance. They can provide more detailed troubleshooting based on the specific configuration and logs of your setup. Would you like me to guide you through checking any of these specific areas, or is there anything else you'd like to explore to resolve this issue?
You can continue this conversation by mentioning me in the message.
p
1. Assistant configured correctly. Through web app, its working fine 2.I don't know where to check these, but the only error logs I've seen regardign this are in VAPI 3. Working fine 4.Should not interfere as seperately through VAPI it's also not working 5.20:09:14:010 [CHECKPOINT] Assistant speech started 20:09:14:212 [ERROR] status-update Server URL Error: Request failed with status code 400 20:09:19:575 [CHECKPOINT] Assistant speech stopped 20:09:27:339 [ERROR] status-update Server URL Error: Request failed with status code 400 20:09:30:964 [ERROR] end-of-call-report Server URL Error: Request failed with status code 400
v
@Porculus Araneus The error logs you've provided are quite informative. The
Server URL Error: Request failed with status code 400
indicates that there is a Bad Request error occurring when the VAPI is trying to communicate with a server. This could be due to several reasons, such as: - Invalid request parameters being sent to the server. - The server endpoint URL might be incorrect or not configured properly. - The server might be expecting different data or headers that are not being provided. Given that the assistant's speech starts but then encounters an error, it seems like the issue might be with the server that's handling the assistant's responses or status updates. Here's what you can do: 1. **Check Endpoint URLs**: Verify that the URLs configured in VAPI for status updates and end-of-call reports are correct and that the server at those URLs is prepared to handle requests from VAPI. 2. **Review Request Data**: Ensure that the data being sent in the requests to the server is in the correct format and includes all necessary information. 3. **Server Configuration**: Check the server's configuration to ensure it's capable of handling the requests from VAPI. This includes checking for any required authentication, headers, or data formats. 4. **Contact Server Admin**: If the server is managed by a third party or another team, reach out to them with the error details to investigate why the server is returning a 400 error. 5. **VAPI Support**: If you're unable to resolve the issue with the above steps, contacting VAPI support with the detailed error logs would be the next best step. They can provide more specific guidance based on their system's behavior. Would you like assistance with any of these steps, or is there anything else I can help you with?
s
@Porculus Araneus can you please share the call ids.
3 Views