Dear all, We are Agency customers and are migrating to Enterprise. We are getting errors when making calls. We spoke with the SIP provider and they informed us that the VAPI is not returning a response. The provider sends a 200, but the VAPI does not respond with an ACK. ORG ID: 9cf65ee9-4f57-4f75-b9d3-99966a5dd9ff I have attached the logs for your immediate review. https://cdn.discordapp.com/attachments/1421162479056064582/1421162479484145815/calltrace_551151995600_5521964989962_8f66d7f6-158.txt?ex=68d80833&is=68d6b6b3&hm=ca4a528ffb455a996a749cd7d5064bdae8d5e040e07200a7cdbfb8b751974ed3&

@Marvin I'm not a VAPI employee - but I'll try and provide some context on the above. From the trace you sent, it would appear that the final ACK message is missing from the trace, causing the 200 OK to repeat, but then drop the call after 30 seconds. This can be related to one of the following: 1. Improper NAT configuration of your Jambonz setup - most likely a mis-configuration somewhere 2. A restrictive firewall at your carrier - they way Jambonz/VAPI perform load balancing is by "jumping" calls between application servers. This can cause an issue where the final ACK comes from a totally different server which isn't whitelisted with your carrier - causing the ACK to drop.

Thanks

Hey! 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 us figure out what went wrong!

The information has already been sent in the log. Didn't you check it? Do I need to send the same file again?

Hey Marvin, thanks for sharing your details. Our team will look into it and get back to you soon with an update.