My assistants were working properly as of Friday but now they aren't recognizing any voice input when inbound or outbound calling. Instead the system disconnects from silence even though someone is speaking. I've verified my phone's microphone is working properly. This is happening on both my dynamic and static assistants. Please assist.

@Tim I'm sorry to hear that you're experiencing issues with your assistants not recognizing voice input during calls. Let's try to troubleshoot the problem together. First, could you please confirm if there have been any recent changes to your assistant configurations or the environment where the assistants are deployed? Additionally, please check if there are any updates or error messages in your system logs that could provide more insight into the issue. If everything seems to be in order on your end, there might be an issue with the assistant service itself. In that case, I would recommend checking the status of the VAPI service to ensure there are no ongoing outages or maintenance that could be affecting the functionality. If you've already checked these and the problem persists, we may need to look into the specific details of your assistant configurations. Please provide any relevant IDs or configuration details that could help us identify the issue more accurately. Rest assured, we will do our best to resolve this as quickly as possible.

I'm showing that all the services are online and that there are no updates or error messages in my system logs. Here are some of my call id's to look into: bb465608-df33-4db2-b8cd-340b97cafcc6 07b6b699-791d-495e-8a75-887daf43daaa 0612abd7-0b8d-42a9-9c51-5dfc3e7605c9 Thanks!

@Tim Thank you for providing the call IDs. I will look into the details of these calls to better understand the issue. In the meantime, it would be helpful if you could also check the following: 1. Ensure that the voice input settings for your assistants are correctly configured and haven't been altered. 2. Verify that there are no network issues that could be affecting the voice transmission quality. 3. Confirm that the issue is consistent across different devices and not isolated to a specific hardware setup. Once I have more information from the call IDs you've provided, we can take further steps to diagnose and resolve the issue. Your patience is appreciated as we work through this. If you have any additional information or observations that might help, please feel free to share them.

Tried a web call and recieved this error in the log: [ERROR] Transcriber failed (reason: Received network error or non-101 status code.) Call ID: b387a7c2-11f4-4e61-811a-266531082870

@Tim The error message you received indicates that there was a network error or a non-101 status code, which suggests a problem with the WebSocket connection used by the transcriber. This could be due to various reasons such as network connectivity issues, firewall restrictions, or a problem with the transcriber service itself. Here are a few steps you can take to troubleshoot this issue: 1. Check your network connection to ensure it is stable and reliable. Intermittent connectivity could cause such errors. 2. Review your firewall settings to make sure that WebSocket connections are allowed and not being blocked. 3. If you are using a proxy server, verify that it is configured correctly to handle WebSocket traffic. 4. Ensure that the transcriber service URL is correct and that the service is operational. 5. If possible, try making a web call from a different network environment to rule out any local network issues. If after checking these steps the problem persists, it may be necessary to escalate this issue to the technical support team for further investigation. They will be able to analyze the call ID you provided and give you more detailed guidance on resolving the issue. Please let me know if you would like me to assist you in contacting support or if there's anything else I can do to help.

After I removed my API key from the transcriber it started working. Not sure why that caused the issue but can consider this resolved. Thanks!

@Tim Sweet. Have a great day!