Hi, I previously had this SIP (382932@sip.zadarma.com) registered with another organization within Vapi. I later changed the password in Zadarma, deleted the trunk in Vapi, and tried to recreate it in my current organization. And now when I try to connect the SIP trunk I had again, I get an error. The information I entered is correct, but Vapi tells me it can't connect the SIP trunk. https://cdn.discordapp.com/attachments/1403087705713152121/1403088025759514674/Captura_de_pantalla_2025-08-07_a_las_18.49.55.png?ex=6896470d&is=6894f58d&hm=12c90f4623b9c789d8084c8f3abcad949ce924da2c2416faba9b3fd16df1c5dc&

Thank you for the details. To help diagnose the issue, could you please share the exact error message or code that Vapi displays when you try to connect the SIP trunk? This will help pinpoint the cause and guide the next troubleshooting steps. Sources: - [Zadarma SIP Integration Documentation](https://docs.vapi.ai/advanced/sip/zadarma) - [SIP Trunking Guide](https://docs.vapi.ai/advanced/sip/sip-trunk)

this , failed to create SIP trunk credential https://cdn.discordapp.com/attachments/1403087705713152121/1403088452462969027/Captura_de_pantalla_2025-08-07_a_las_18.49.55.png?ex=68964773&is=6894f5f3&hm=8932ff9b9948b74c9c9da32dcc38b18a49e9feb5d835a6fda1fe29fa16552418&

Suggestion: Double-check that your Zadarma SIP credentials (username and password) are correct and up to date in both Zadarma and Vapi. Then, try creating the SIP trunk using the following API call, replacing the placeholders with your actual details:

bash
curl -L 'https://api.vapi.ai/credential' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_PRIVATE_KEY' \
  -d '{
    "provider": "byo-sip-trunk",
    "name": "Zadarma Trunk",
    "gateways": [{ "ip": "sip.zadarma.com", "inboundEnabled": false }],
    "outboundLeadingPlusEnabled": true,
    "outboundAuthenticationPlan": {
      "authUsername": "YOUR_SIP_NUMBER",
      "authPassword": "YOUR_SIP_PASSWORD"
    }
  }'

If the error persists, ensure your password change in Zadarma is fully propagated and not cached in Vapi, and consider using a new trunk name to avoid conflicts. [See full Zadarma SIP integration guide](https://docs.vapi.ai/advanced/sip/zadarma) Source: - [Zadarma SIP Integration Documentation](https://docs.vapi.ai/advanced/sip/zadarma)

Also please try using the IP address of the domain instead of the resolved name ([sip.zadarma.com](http://sip.zadarma.com))