mayseamsberry
05/27/2025, 9:13 AMVapi Support Bot
05/27/2025, 9:15 AMcall.in-progress.error-sip-telephony-provider-failed-to-connect-call
means Vapi could not connect the call through your SIP provider.
A common cause is a misconfigured SIP trunk or missing network allowlist. Please double-check that your SIP provider is correctly configured in Vapi and that you have allowlisted the required Vapi IPs (e.g., 44.229.228.186/32
, 44.238.177.138/32
). Here’s a quick checklist:
markdown
- Verify SIP trunk credentials (username/password or IP-based)
- Ensure your SIP provider is routing calls to the correct Vapi SIP URI
- Allowlist Vapi's IPs in your firewall/SIP provider settings
If the issue persists, review your SIP trunk logs for authentication or routing errors.
Sources:
- [Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason)
- [Vapi SIP Trunking Setup](https://docs.vapi.ai/advanced/sip/sip-trunk)mayseamsberry
05/27/2025, 9:18 AMVapi Support Bot
05/27/2025, 9:19 AMExternal server (SIP URI): YOUR_VIRTUAL_NUMBER@sip.vapi.ai
Allowlist IPs: 44.229.228.186/32, 44.238.177.138/32
After updating, test several calls to confirm improved reliability.
[See full Zadarma integration steps](https://docs.vapi.ai/advanced/sip/zadarma)
Sources:
- [Vapi SIP Trunking Setup](https://docs.vapi.ai/advanced/sip/sip-trunk)
- [Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason)
- [Zadarma SIP Integration](https://docs.vapi.ai/advanced/sip/zadarma)Vapi Support Bot
05/27/2025, 10:30 AMKyle Brunker
05/28/2025, 1:30 AMSubrat Sagar
06/26/2025, 7:27 AMmayseamsberry
06/26/2025, 8:41 AMSubrat Sagar
06/26/2025, 9:04 AMKyle Brunker
06/28/2025, 6:55 AMmayseamsberry
07/04/2025, 8:54 AMKyle Brunker
07/08/2025, 1:39 AMmayseamsberry
07/09/2025, 2:03 PMmayseamsberry
07/09/2025, 2:03 PMKyle Brunker
07/10/2025, 2:29 PM