----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Introduction]() * [Outbound Calling]() * [Web Calling]() * [Glossary]() -----------------------------

### Answer I understand how frustrating technical issues like these can be, especially when it affects your development process. The documents provided don't detail specific troubleshooting steps for issues with voice providers like Deepgram or scenarios involving static and cracking voices during calls. However, Vapi's architecture allows for swapping out different components, such as the voice provider, to tailor the system to your needs. This flexibility can be critical when encountering issues with specific providers [(1)]() . For the problem you described, it seems you've already taken a practical step by switching to a different voice provider, which resolved the issue. This suggests that the problem might have been specific to the interaction between Vapi and the Deepgram voice services at that time. If issues like this persist or you encounter other anomalies, considering the architecture of Vapi could offer some insight into potential areas to investigate, such as configuration settings for the voice provider or the interaction between different components of the pipeline. It's also worth noting that Vapi is designed to handle a wide array of speech-to-text, large language model, and text-to-speech providers, giving developers the flexibility to choose the best tools for their specific use case. While I cannot provide a direct solution to the malfunctioning you experienced, exploring alternative configurations or voice providers, as you have done, is a recommended approach when facing such challenges.