ERROR EXITING MEETING BECAUSE ROOM WAS DELETED
# support
j
I keep getting this error every time I test my AI Assistant. Feedback or help will be really appreciated . We are currently testing to see if Vapi will be a good fit for our company. #1211483291191083018
v
Hi there! I understand you're encountering the "ERROR EXITING MEETING BECAUSE ROOM WAS DELETED" error while testing your AI Assistant with Vapi. This can definitely be frustrating when you're evaluating if Vapi is a good fit for your company. I found several potential causes and troubleshooting steps for this error that might help you resolve the issue: ## Potential Causes According to the information I found, this error can occur due to several reasons: 1. **Assistant End-Call Phrases**: Your assistant might be saying phrases that trigger call termination. According to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337162299621900359), removing these end-call phrases from your assistant can help things work more smoothly. 2. **Microphone Permissions**: If you're using the Web SDK, starting a conversation without microphone permission can cause this error after about 10 seconds, even when messages are being sent from the client using
vapiRef.current.send
as noted in [user reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336782522859913226). 3. **Custom Provider Credentials**: Using your own API keys and endpoint URL under "provider credentials" can trigger this error. [User experiences](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336754090880798765) suggest that removing these provider keys might resolve the issue. 4. **Service Degradation**: There might be a service degradation with Deepgram affecting your voicebot's functionality, as mentioned in [troubleshooting threads](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1296852804631265392).
5. **Misleading Error Message**: Sometimes this error message can be misleading - the actual reason might be different, such as "customer-ended-call" according to [user reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337399575744348180). ## Troubleshooting Steps Here are some steps you can take to troubleshoot this issue: 1. **Check Server and Client Logs**: Look for any error messages or actions that indicate why the room was deleted, as recommended in [troubleshooting guides](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333877747453395014). 2. **Remove End-Call Phrases**: If your assistant is using phrases that might trigger call termination, try removing them from your assistant's responses. 3. **Check Microphone Permissions**: If using the Web SDK, ensure proper microphone permissions are granted. 4. **Verify VAPI Endpoint**: Ensure that the endpoint you're trying to reach is correct and operational as suggested in [support threads](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336456720913797238). 5. **Adjust Endpointing**: Try adjusting the "endpointing value" or disabling it completely as mentioned in [user solutions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333510134617604147). 6. **Share Call ID with Support**: For a more in-depth investigation, you might need to share your call ID with Vapi support. Would you be able to share more details about your implementation or which of these potential causes might apply to your situation? I'd be happy to provide more specific guidance based on your setup. Sources: - [Discord discussion on assistant end-call phrases](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337162299621900359) - [User reports on Web SDK microphone permissions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336782522859913226)
j
Can I have customer support reach out?
p
Hey! To help track down this issue, could you share: - The call ID - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!