After the recent update—where integrations were moved into the Settings section—none of my telephony services are functioning properly. I have a dedicated SIP Trunk configured specifically for VAPI, and I'm currently unable to place any calls. I've noticed a recurring pattern: every time the system is updated, I have to reconfigure my SIP settings on the platform. Normally, this workaround restores functionality, but today, despite trying multiple reconfiguration methods and formats, I am still unable to receive calls. This directly impacts my assistant’s ability to operate, which in turn affects a major part of my operation that relies heavily on this integration. I want to highlight that everything was working perfectly yesterday (June 13th), but after today's update, it stopped functioning altogether. For context, I connect my trunks through: Integrations > SIP Trunk Credentials. Additionally, I’ve identified a potential bug: When I have multiple SIP trunks connected and try to delete one, the system ends up deleting another one instead. Example: I have two connected trunks, one named SIP TRUNK #1 and another named SIP TRUNK #2. When I attempt to delete SIP TRUNK #1, the system deletes SIP TRUNK #2 instead. I’m unsure why this is happening. I kindly request your support in resolving these issues as soon as possible, given the critical impact on my operations. https://cdn.discordapp.com/attachments/1383469421732958208/1383469422190264453/image.png?ex=684ee7cd&is=684d964d&hm=d73dd42b61af43f9a92be288986e7529b1a848bdb998d79a08a2e8646b46021e& https://cdn.discordapp.com/attachments/1383469421732958208/1383469422525677588/image.png?ex=684ee7cd&is=684d964d&hm=78679ef3419dd0051880d04de896aadcd0bc8858972c94e311c29f7086e6d8bd&

Please try re-adding your SIP trunk credentials in the Integrations > SIP Trunk Credentials section, ensuring all required signaling IPs are allowlisted and your gateway settings match your provider's requirements. If the issue persists, document the steps you've taken and contact Vapi support directly, as this may be a platform-side issue following the recent update. For the deletion bug, report the exact steps and trunk names to support so they can investigate and resolve the misbehavior. [See SIP trunk setup and troubleshooting documentation](https://docs.vapi.ai/advanced/sip/sip-trunk) Sources: - [Vapi SIP Trunking Documentation](https://docs.vapi.ai/advanced/sip/sip-trunk) - [Vapi Discord Support Thread](https://discord.com/channels/1211482211119796234/1372358449761091584)

Thanks for the suggestion, but I’ve already reconfigured all SIP trunk settings multiple times: I’ve re-added the credentials in Integrations > SIP Trunk Credentials. All signaling IPs are allowlisted. The gateway settings match exactly what my provider requires. Despite that, calls are still not going through, and the integration remains non-functional. This issue clearly started after the recent platform update, and everything was working perfectly before (June 13th). At this point, it seems to be a platform-side issue, not a misconfiguration. @Vapi Support Bot

Hey, sorry to hear about the issue with your account. Could you please record a loom video showing the error or behavior you're experiencing? It would really help us understand the problem better. Also, please share your account email address so we can assist you further.

Look, unfortunately I can’t record a video because I don’t have direct access to the platform—only the connection credentials. Since this is a third-party service, they’re unable to send a video due to the sensitive nature of the data. However, they did send me this screenshot and mentioned that they are receiving two distinct records from the VAPI platform. The correct one is the first, which contains the word "SIP." https://cdn.discordapp.com/attachments/1383469421732958208/1384627634662805504/6947d5cd-51a2-4b26-9a06-20401a445b30.png?ex=68531e79&is=6851ccf9&hm=e40ec816838843c03222a822d844777078b1681906a7af58f38baca5b579304d&

Could you please provide the phone numbers that you are configuring?