call.in-progress.error-sip-telephony-provider-fail...
# support
t
We get this error now on all calls: call.in-progress.error-sip-telephony-provider-failed-to-connect-call Any changes done? New ip addresses? What can I check to find the root cause? @Shubham Bajaj
v
Hi there! Sorry to hear you're experiencing connection issues with all your calls šŸ˜• I don't have information about any recent changes or new IP addresses specifically, but I can definitely help you troubleshoot this "call.in-progress.error-sip-telephony-provider-failed-to-connect-call" error. Here are several potential root causes and things you can check: ### Network & Firewall Configuration - Verify your network allows SIP protocol traffic and that firewalls/NATs are configured to allow SIP messages through - Check if any firewall settings are blocking SIP traffic on relevant ports - Ensure proper IP whitelisting - some users needed to whitelist specific IPs (44.229.228.186 and 44.238.177.138) to resolve similar issues ### SIP Configuration Issues - Check the SIP URI format in the
sipUri
attribute within the
forwardingPhoneNumbers
array - Verify the
forwardingPhoneNumber
is in the correct E.164 format (e.g., +15558675309) - If using a Vici system, confirm it can handle SIP REFER messages ### Authentication Problems - Double-check that credentials provided to Vapi are correct if your SIP endpoint requires authentication - Ensure your SIP provider is sending username/password entries for sip.vapi.ai - When Vapi sends a 401 challenge, the system needs to respond with valid credentials ### Telephony System Issues - Your telephony system might not be responding in the required time - Check telephony logs to investigate further - Verify that your SIP server or PBX is configured to accept calls from Vapi's servers ### Other Potential Causes - Codec compatibility issues (ensure codecs used by Vapi are supported by your SIP endpoint) - Database outages (e.g., with Supabase) - Concurrency limits being exceeded - SIP trunk configuration problems - Incorrect SIP registration - Issues with call transfers or call forwarding ### Troubleshooting Steps 1. Check server and telephony logs for specific error details 2. Verify your internet connection is stable
3. Check the call provider's status for any issues on their end 4. Review recent updates from your SIP provider that might require adjustments 5. Perform ping and traceroute tests to identify network connectivity issues Is there anything specific from these areas you'd like me to elaborate on further? Sources: - [Root cause of call.in-progress.error-sip-telephony-provider-failed-to-connect-call](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340144301132353637) - [Troubleshooting SIP telephony provider connection failures](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334651376743092355) - [Impact of IP address changes on SIP telephony](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339949961491644447) - [General troubleshooting steps for SIP telephony connection issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336713212233515089)
m
Same thing is happening to me. My phone call connection was fine yesterday and days before that but today im unable to call through to my vapi number via my phone which was strange as its only happening today.
c
The SIP server has been down since yesterday, and I'm getting SIP trunk UNREACHABLE messages from several PBXs. Can Support look into this urgently? @User
p
+1
s
+1
g
+1
k
This is started recently. Previously, we resolved it, but we didn't close the incident as it was under monitoring, so it came again today. It's all when we have an unexpected amount of calls on the network, this comes up. Currently, we are doing what we can to upgrade everything so that this never shows up again
p
Totally understand that you're working on this. This seems like a pretty important issue to resolve. Few questions that might help us: - Do you expect this to happen again in the future? - Does this issue only impact Vapi phone numbers? Or all incoming/outgoing calls even via Twilio etc?
k
This issue basically originates from our SIP stack, not from the core VAPI itself. We don't expect this to happen again in the future, and it has affected all of the SIP calls. For now, we are doing an RCA first that will evaluate other options for our SIP stack, and then we'll choose a better mode for it. A stable stack within a win for it.
d
+1
k
Hey guys, please try now. This issue has been resolved, and SIP calls must be working for you.
k
+1
m
We still get the same error throughout the entire day. @Shubham Bajaj Call IDs: b3f056f6-9fb7-4810-a822-785bd709ed67 f1410c77-6b8d-4c4e-82dd-08a7fdbd4695 e26f0b39-660d-4ba4-b2e2-0e4d794ca2f0 and many more. An error occurred in this call: call.in-progress.error-sip-telephony-provider-failed-to-connect-call
k
looking into it.
update: checking with the team what's the possible failure reason? As per my understanding, till now it's because of your SIP configuration, but to be sure I'm checking with ourt team again.
p
Hello eveyone, I am also geetting this error constantly. Call ids: a9e2dde7-537b-4535-b632-39286b5d2bdb 07fd693f-9656-4424-b1a4-4cd3bbd818bc Has anyone solved it yet?
k
Hi, checking if this is resolved/solved for you?
p
@Shubham Bajaj this is still happening all the time for me
g
same with me here @Shubham Bajaj
k
šŸ”µ 22:08:58:307 Processing
phoneNumber
Deletion... { "id": "70e63263-ea00-4824-9672-d4a803f87d7a", @pabl0ro Can you share a call ID with whose phone number is not deleted?
@gypson can you share the call ID?
g
@Shubham Bajaj 13c7d5dc-3465-462d-8351-3a7f44c07f2b 651b783c-aab7-4385-b2ea-1a475bb81750 767403d6-6673-4410-afc4-a3a281f29d13 c2ae0767-e1d6-4681-b2bb-5d3e01535d4e a26597e6-8a7f-4f82-a5b9-ae491da7b8ed
k
looking into it.
šŸ”µ 21:01:00:373 Received Phone Number Call Status Update: { "call_sid": "4f695803-543b-4e75-aad2-fd888ffb934a", "direction": "outbound", "from": "+16023650219", "to": "+14692885467", "call_id": "0b383b04-9284-123e-ffb3-0ae563bc2ea9", "sbc_callid": "0b39ec0c-9284-123e-0bb8-02615329b2f9", "sip_status": 480, "sip_reason": "Temporarily Unavailable", "call_status": "failed", "account_sid": "c033b672-5b99-42ae-9ce2-b231e9a522fb", "trace_id": "c35375114da163431bc52b2ae6fa7561", "fs_sip_address": "172.32.32.68:5060", "api_base_url": "" } Can you check once again?
g
still getting a lot of "call.in-progress.error-sip-telephony-provider-failed-to-connect-call" errors
7dc7d20c-6414-4d7d-80e2-7ba69237d4ad b4a0e76b-0110-4dd7-8ff6-b6c8b255ef42 9bfe90f3-3b93-474d-861f-f0b271dc8db6 1050713c-da2e-4b54-afd7-b93953d9184b 93553065-aff0-4bd2-91e3-06154c227a1d 28a3a2a5-8b8b-427a-bf03-607e96e91e4e c703ab7b-656e-43a3-8264-f696884cc1d6 4ec646af-2970-42b2-a012-81941162408a 277b2296-da40-4c0a-9fde-efc8fb4c9d92 ce1dea15-d7b9-4403-9a06-c7f44e064b0a
@User this error disappeared a couple of days ago but it's back again
p
Hello Vapi Team. I am getting this error also. Few days ago it worked all fine. But today not anymore. Here is my call ID : 4a061fe3-c896-4f36-b21a-71a14d8ee93a Ple And if you have more insights on why it is not working would be very helpfull.
@Shubham Bajaj Would be very helpfull if you can take a look on it asap.
k
Copy code
{
  "callStatus": [
    {
      "call_sid": "f6ddbbb5-8c09-4b61-bf9b-e614ddcf7fad",
      "direction": "outbound",
      "from": "+593958665659",
      "to": "+5930993388972",
      "call_id": "49361fc0-9728-123e-36ad-062a20bd352d",
      "sip_status": 100,
      "sip_reason": "Trying",
      "call_status": "trying",
      "account_sid": "5b80093d-1409-4c38-a0ea-a240eccdc03b",
      "trace_id": "041570896cd6ed36ea924f042c60e354",
      "fs_sip_address": "172.32.12.150:5060",
      "api_base_url": "http://sip-web.vapi.ai/v1"
    },
    {
      "call_sid": "f6ddbbb5-8c09-4b61-bf9b-e614ddcf7fad",
      "direction": "outbound",
      "from": "+593958665659",
      "to": "+5930993388972",
      "call_id": "49361fc0-9728-123e-36ad-062a20bd352d",
      "sip_status": 408,
      "sip_reason": "Request Timeout",
      "call_status": "failed",
      "account_sid": "5b80093d-1409-4c38-a0ea-a240eccdc03b",
      "trace_id": "041570896cd6ed36ea924f042c60e354",
      "fs_sip_address": "172.32.12.150:5060",
      "api_base_url": "http://sip-web.vapi.ai/v1"
    }
  ]
}
It is getting response timed out from your telephony provider side.
p
ok thanks a lot!
k
Nice
p
@Shubham Bajaj : here is a call I just tried c1b233fc-1ebf-4815-a52a-fbaa7244576b no matter how much I tried, no luck
k
This ticket has been marked as solved, and as a result, you will no longer receive any further responses. Kindly create a new support ticket to escalate your inquiry.Ā 
m
Hi @Shubham Bajaj I am trying to make outbound call using VAPI and Plivo (I have purchased indian number and destination number is also indian) { "id": "0f1c1751-c734-424f-89ef-15200963ba9a", "assistantId": "52739d19-cdce-4903-8563-a1476d2d0d39", "phoneNumberId": "ba4e0f4e-fe1e-444d-b715-638e71703230", "type": "outboundPhoneCall", "createdAt": "2025-05-06T02:59:39.799Z", "updatedAt": "2025-05-06T02:59:39.799Z", "orgId": "a55e28be-be19-4ff3-bb9a-d2aae6511e42", "cost": 0, "customer": { "number": "+917814064561", "numberE164CheckEnabled": false }, "status": "queued", "phoneCallProvider": "vapi", "phoneCallProviderId": "141cb4ce-a6ba-4071-b639-f0fce8089f01", "phoneCallTransport": "pstn", "phoneCallProviderDetails": { "sbcCallId": "fe45f893-a4c8-123e-4fbb-06496812ecbf" }, "monitor": { "listenUrl": "wss://phone-call-websocket.aws-us-west-2-backend-production2.vapi.ai/0f1c1751-c734-424f-89ef-15200963ba9a/listen", "controlUrl": "https://phone-call-websocket.aws-us-west-2-backend-production2.vapi.ai/0f1c1751-c734-424f-89ef-15200963ba9a/control" } } here is the response of call/phone api endpoint. getting this error An error occurred in this call: call.in-progress.error-sip-telephony-provider-failed-to-connect-call Please help me
@Vapi @User Please help me
k
Hey Madhav, please create a new support ticket for your issue. This ticket has been closed, so you won't be getting any support help here.