We've established our server settings but the webhook output is being sent to a different server that is not ours. We understand the server priority but show no conflicting server settings, including within our payload. Any suggestions would be great. However, the fundamental issue remains: Vapi is sending events to the ngrok URL for calls associated with this phone number (728a3746-...) and assistant (ba9729f8-...), despite you having configured the correct Azure URL at the Assistant and Function levels. https://cdn.discordapp.com/attachments/1357394711530438716/1357394711869915186/Vapi_Server_Issue_2.png?ex=67f00bd6&is=67eeba56&hm=13763ce41e2f38ad74a032a9a449e37163013f5f59ddf6634fa4944fc8a2d97a& https://cdn.discordapp.com/attachments/1357394711530438716/1357394712192880692/Vapi_Server_Issue_.png?ex=67f00bd6&is=67eeba56&hm=dedb765d197eae87bcf27d4c56cdd8962d61094950743d7f85c84ca22a8e7b1b&

I see the issue - your events are being sent to an ngrok URL instead of your configured Azure URL. This can be frustrating! Have you recently made any changes to your Phone Number settings? Since you mentioned you've configured the Azure URL at both the Assistant and Function levels, the issue might be at the Phone Number level, which would override your Assistant settings according to [Vapi's server priority](https://docs.vapi.ai/server-url/setting-server-urls). Could you check if there's an old ngrok URL configured at the Phone Number level in your Vapi dashboard? Also, when was the last time you used that ngrok URL for development before switching to Azure? Another possibility is caching - sometimes Vapi might be using a cached version of your server URL. Have you tried restarting the assistant or creating a new one with the correct Azure URL to see if that resolves the issue? Source: - [Setting Server URLs](https://docs.vapi.ai/server-url/setting-server-urls)

There's no server settings in the VAPI UI for the VAPI phone numbers

Thank you for reaching out to us. We've received your message and will get back to you as soon as possible.

This appears to be a larger caching issue with Vapi and we had a work around but not sure if the Vapi caching issues have been resolved

Hey, this issue has been fixed by us, so could you please give it a try once more and let me know how it goes for you?