call.in-progress.error-sip-telephony-provider-fail...
# support
p
Hello Vapi Team, A few days ago, everything was working correctly when making outbound calls. However, I started noticing that only 1 out of every 3 or 4 attempts would go through successfully. Despite the inconsistency, at least some of the calls were connecting. But as of today, none of the call attempts are working — I am not receiving any INVITE on the Asterisk side, and the calls do not appear to reach the server at all. Here is one of the recent Call IDs I’ve tested with: 4a061fe3-c896-4f36-b21a-71a14d8ee93a Additionally, I am seeing a "Status OK" in Postman after sending the call request, but no call is being received by Asterisk. It would be extremely helpful if you could provide any insights into why this is happening or if there’s any issue on the routing or delivery side from Vapi. Thank you in advance for your support. Best regards,
k
Hey! To help track down this issue, could you share: When exactly this happened (the timestamp) This would really help us figure out what went wrong!
p
{ "id": "49d92bcd-3879-4d18-a7c9-f6443038402a", "assistantId": "6d6b40bd-2590-4fc3-87c9-90e9e3856fb3", "phoneNumberId": "1f2040c3-243f-4f8a-a799-6b6f236d762e", "type": "outboundPhoneCall", "createdAt": "2025-04-18T20:48:41.126Z", "updatedAt": "2025-04-18T20:48:41.126Z", "orgId": "2d887915-ebda-46b2-8b93-9a1be0e98a4d", "cost": 0, "customer": { "number": "+5930993388972", "numberE164CheckEnabled": false }, "status": "queued", "phoneCallProvider": "vapi", "phoneCallProviderId": "8d411f10-f0c7-4f24-8c1d-79985abc436f", "phoneCallTransport": "pstn", "phoneCallProviderDetails": { "sbcCallId": "5a0b1673-9739-123e-0e9c-0263fe811d8f" }, "monitor": { "listenUrl": "wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/49d92bcd-3879-4d18-a7c9-f6443038402a/listen", "controlUrl": "https://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/49d92bcd-3879-4d18-a7c9-f6443038402a/control" } } Call ID: 49d92bcd-3879-4d18-a7c9-f6443038402a
k
Looking into it
p
Did you find the issue?
n
@paolobertini When you say "Asterisk" do you mean a vanilla installation or are you using a FreePBX distro installation? If you are using FreePBX (or any of its derivatives, such as PBX-In-A-Flash or issabel), these normally have Fail-2-Ban installed by default. The way VAPI sends calls to remote servers, specifically if you setup user/password challanges, may cause fail-2-ban to put VAPIs IP numbers into a jail, preventing them from properly signalling the Asterisk server.
This is a normal behaviour for these machines, which are designed to work as a PBX - not as a carrier inter-connect.
r
Same here...
s
@Reuben @paolobertini A gentle reminder to continue this thread and Also, clarify the following asks: https://discord.com/channels/1211482211119796234/1362891390312382794/1363505074608934932
p
I am using Issabel and a gateway, so all calls are free because we're leveraging the existing infrastructure from their call center.
12 Views