My VAPI agent is not working. It is not receiving voice input from my side, but agents for a different organization are working fine. Why is this happening? @Shubham Bajaj @Vapi

Heykishan Thank you for creating the ticket! A member of our team will reach out to you shortly.

kindly check and update me soon

message has been deleted

there is no network issue ,only agents of one organisation is not working .others are working fine.

@kishan Thank you for confirming that there are no network issues and that the problem is isolated to agents from one organization. It sounds like there might be a configuration issue specific to that organization's VAPI setup. Here are a few steps you can take to troubleshoot the problem: 1. Verify that the VAPI agent for the affected organization is correctly configured with the right credentials and settings. 2. Check if there have been any recent updates or changes to the agent that might have affected its functionality. 3. Ensure that the voice input feature is enabled and properly set up for the organization's agent. 4. Look into the organization's VAPI logs for any error messages or warnings that could indicate what the issue might be. If after these steps the issue remains unresolved, it may be best to escalate this to our technical support team for a more detailed analysis. Would you like me to initiate that process for you now?

everthing is configure correctly. i have developed 3 agents still same error

@kishan I understand that this must be frustrating for you. Since you've developed three agents and all are experiencing the same error, it's possible that there's an underlying issue that might not be immediately apparent from the configuration alone. To proceed with resolving this, I would recommend the following steps: 1. Double-check the API keys and access permissions for each agent to ensure they are correct and have not been revoked or expired. 2. Review the code or settings for any recent changes that might have inadvertently affected the agents' ability to receive voice input. 3. Test the agents in a different environment, if possible, to rule out any device-specific or network-related issues. 4. If available, use any debugging tools or logs provided by VAPI to gain insights into the problem. If these steps do not resolve the issue, it would be best to have our support team take a closer look. They can perform a more in-depth analysis and potentially identify the root cause of the problem. Would you like me to escalate this to our support team for further assistance?

Hey @kishan To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!

@Shubham Bajaj @Vapi i have sort out the issue .it was realted to transciber.i changed it from deepgram .

@kishan That's great to hear that you've identified the issue and resolved it by changing the transcriber from Deepgram. It sounds like there might have been a compatibility or configuration issue with the previous setup. I'm glad you were able to troubleshoot and fix the problem effectively. If you have any more questions or need further assistance with your VAPI agents, feel free to reach out. Otherwise, if everything is working smoothly now, would you like me to close this support ticket for you?