Hi Vapi Support Team, I'm currently implementing a custom LLM integration with Vapi and need to configure IP whitelisting on my server for security purposes. Could you please provide me with the following information: Egress IP addresses or IP ranges that Vapi uses when making requests to custom LLM endpoints Whether these IP addresses are static or subject to change If they do change, what is your notification process for IP updates Any recommended security best practices for custom LLM endpoint configuration My Use Case: I'm setting up a custom LLM endpoint that will receive requests from Vapi during voice conversations, and my infrastructure security policy requires IP whitelisting for incoming API requests. Thank you for your assistance. I look forward to your response.

Hi pankaj, Vapi does not have a fixed set of static egress IP addresses for outbound requests such as those to custom LLM endpoints. Instead, Vapi uses a public proxy pool, meaning the IPs can change, and there isn't a specific range you can whitelist. For security, you might consider: - Whitelisting domains/sub-domains rather than IPs. - Implementing token-based authentication for API requests. - Regularly monitoring your server logs for unexpected IP addresses and updating security configurations as necessary. If you have further questions or need more detailed guidance, feel free to ask.

what is the domains/sub-domains ?

Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team

Team, Do you have any set of ip address that it is using right now ?

Hi pankaj, For Vapi's egress IP ranges when making requests to custom LLM endpoints, we unfortunately do not have a fixed set of IP addresses to provide for whitelisting purposes. Our infrastructure uses a public proxy pool with dynamic IPs, which can change and are not static. As a security best practice, instead of whitelisting IPs, you can consider implementing domain-based whitelisting for enhanced security. This allows you to configure your server to accept requests based on recognized domain names. Additionally, using OAuth2 for authentication can add an extra layer of security for your custom LLM integration. You can set this up as described in this [document](https://docs.vapi.ai/changelog/2024/12/6). Please let me know if you need further assistance or clarity.