sip-gateway-failed-to-connect-call
# support
j
I'm using a VAPI phone number to do outbound qualification calls and I've been getting this error for 3 days now cc74d2b2-4d7c-4b65-9e67-85ed39ba8ef2 f93b15a3-d578-4988-8cf8-9aeb6ec884d8 caf9a2a7-4a2c-4c80-93c6-39cf3b7c23e3
j
I'm still getting the same error for the 4th day now
7d1661c8-0be6-4976-a7dc-959acd0ad7e3
1c7453c9-95a3-4701-b654-16c645191db1
v
Copy code
πŸ”΅ 21:51:58:657 Received Phone Number Call Status Update: {
  "call_sid": "7c9e0c87-b276-4b77-bc07-a637db970163",
  "direction": "outbound",
  "from": "+xxxxx",
  "to": "+xxxxxx",
  "call_id": "36d2b15f-7faf-123e-e692-cad4a4ad4806",
  "sip_status": 500,
  "sip_reason": "Server Internal Error",
  "call_status": "failed",
  "account_sid": "c033b672-5bxxxxx----e9a522fb",
  "trace_id": "xxxxxxxxx",
  "fs_sip_address": "17xxxxx:5060",
  "api_base_url": "http://api.awsxxxxxxxxi/v1"
}
@jap Issue is on our end. I will suggest you to acquire another VAPI number and then try making a call, and it will work. let me know how it goes for you.
j
Hello I acquired another VAPI number but issue still persist
670ec6cc-f6b0-43f9-9bda-c744692b10e4
c602d8c3-5146-4164-b2e6-002e6b606a8d
@User @Shubham Bajaj can you please give me an ETA of when this issue is gonna get fixed, this has been the 6th day I got sip-gateway-failed-to-connect-call error using VAPI number
g
I also have the same issue here. I saw that the VAPI SIP has been degraded, when would this get back up @User @Shubham Bajaj ?
s
No VAPI SIP has not been de graded its something else for his account only.
Allow me sometime to check I am away from keyboard.
j
I don't think it's just something for my account only because I just tried it on another separate account with new vapi number and still got the same sip-gateway-failed-to-connect-call error
bfd3a283-1a5b-44c4-a7df-1881e7513975
6f3ba7be-368f-46ab-a568-aee196870bcf
8e193c0d-3a7b-4725-9b81-9580166a73f1
88977058-e720-4f98-8e15-c1ca7470fb90
312a2a40-8ef1-4353-9772-5147976ecb18
I don't why but for some reason it can receive inbound calls but can't do outbound even tho it hasn't reached the 10 calls per day limit it's always just sip-gateway-failed-to-connect-call
@User @Shubham Bajaj
s
@jap looking into it.
πŸ”΅ 21:48:30:886 Call
8e193c0d-3a7b-4725-9b81-9580166a73f1
Waited 300s But Transport Never Connected. πŸ”΅ 21:43:33:217 CallId: 8e193c0d-3a7b-4725-9b81-9580166a73f1 Determined Update: { "status": "ended", "endedReason": "sip-gateway-failed-to-connect-call" } πŸ”΅ 21:44:22:052 Call
312a2a40-8ef1-4353-9772-5147976ecb18
Waited 300s But Transport Never Connected. πŸ”΅ 21:39:24:978 CallId: 312a2a40-8ef1-4353-9772-5147976ecb18 Determined Update: { "status": "ended", "endedReason": "sip-gateway-failed-to-connect-call" } @jap Hey, the issue is with us. Initially, I thought it was on a phone number which you have created. But no, it's with all of the numbers. I'll get back to you on this by tomorrow once the team is online. Until then, I suggest you use Twilio and Vonage for numbers to unlock yourself
j
Okay thanks I'll be waiting on your update
s
fyi
@jap I have shared your issue with the team.
@jap Can you make another call and share the call ID? We were doing our investigation, and we require a recent call ID. It would be great if you can do it, and it will be very helpful as well to us.
j
Thanks for the update @Shubham Bajaj
Okay I'll try and do another call later today, I'm away from keyboard rn I'll send new call ID later
@Shubham Bajaj I did some test calls today and still got the same error
f715b60b-5c52-4c22-b689-92d80b26b2dd
69a20c8a-ae5b-48d6-8c1d-57df931df3ad
62bc0d1a-9bf6-4538-8e91-39f04f74772f
af29b11a-a06d-4ed7-bd00-29e34f11f72c
d25ecffe-9719-4779-8cf7-b0ad275f84d6
I also had 2 instances where it said "customer ended call" but the call was all silence
a7f87ed4-b80b-436e-90b0-a3a604fb2615
9375c3c6-7247-465f-a334-41c21de407d6
@Shubham Bajaj
g
@User any updates with this? I'm also facing the same issue here with sip-gateway-failed-to-connect-call error using vapi number for outbound calls
s
@gypson can you also share the call Ids?
g
8a3cbb51-0cc0-4472-82bc-de992ad4fbdf
ab378892-7a6e-44ff-aacc-3da200426c25
dce1a68b-3428-475a-baed-2b8da2df6be0
30a111c2-04fb-4ccd-8e06-c454986dbdf7
1398e505-cb8a-4a99-a8d6-1b31103accd6
c9804be8-f8aa-4cf2-a336-be868e25802a
5587531d-b89a-4d3a-9c54-c884e03231c0
5413b676-fdf3-4ac5-9bbe-bd42f753fb2c
s
Thanks @jap @gypson for sharing the call IDs. I have shared them with the team.
j
Thanks @Shubham Bajaj I'll be waiting for your update, this issue has been going on for almost 2 weeks now
v
Hey Jap, The team acknowledges your issue and is aware of problems with your account. I've shared your call IDs. Your ticket is prioritized and labeled (SIP and debugging), so don't worry, it's being worked on. In the first week, I tried to find a solution, thinking it might be one of chance, something is not working but in the second week after realization, I shared it with the team, who are now investigating why it's only affecting you.
a
It’s affecting me too
c
Getting same error in addition to "Sip telephony provider failed to connect call" with outbound qualification calls. Call IDs: 8c2f96fc-19c1-46a6-8fa1-f0a1ea4b5e5f (sip gateway) b5d66d70-9acb-4c54-9944-c2d90d48d73c (sip telophony provider)
j
@Shubham Bajaj I'm getting "sip-telephony-provider-failed-to-connect-call" error now instead of "sip-gateway-failed-to-connect-call", I'm assuming it's the same error?
86a2d9c2-53dc-4056-bb04-1747dfd852c0
85952565-84e2-45ed-afb5-3f519974dc4f
2abad732-4617-4cf7-b788-007fce194ee7
227acf89-461a-4b19-877a-48243aee5f94
90f561fa-1d07-4deb-8484-794ad46de7e5
10d50948-2d2f-4e93-a57e-958fb4327237
v
Hey @jap, team is working on it meanwhile can you try making few calls using the other telephony. for some unknown reason, happening with you only, that's why it's taking me a little longer to get fixed. I will suggest to use other telephony until its fixed for you to unblock yourself.
p
Hi! I'm also seeing the same "Sip telephony provider failed to connect call" error when trying to make an outbound call with a VAPI phone number so it's not just jap who is affected. My first request worked (8e3daa9a-9f47-461a-9ae8-a2cdac55537f) but all calls have been failing with the same error since (159b2fb1-17a2-495b-92b1-734ab5db7528, fca3ce4e-0dbd-4b1c-b0d8-88557c7e7f91). I tried a second phone number too and it didn't work (26878c93-4fb7-405d-a9e3-5b217a4dfa2e).
v
Hey, thanks for sharing those call IDs. I have marked your ticket as high priority item to the team.
g
Any updates on this @Shubham Bajaj? Having an ETA would be cool tho
j
@Shubham Bajaj @User
v
Pinging the team again on this....
g
Thanks @Shubham Bajaj, I'm still getting a lot of "call.in-progress.error-vapifault-transport-never-connected" and "call.in-progress.error-sip-telephony-provider-failed-to-connect-call" errors
v
Hey @gypson. Could you share the recent call IDs? This issue has been solved by our team, and if it's still occurring for you, I can take a look and now resolve it for you.
a gentle reminder to continue this thread.
g
Hello @Shubham Bajaj b2f683a3-7135-48fb-9d5b-122f0bd870cd cb46cfa0-2246-4457-8a43-4603119a98c1 26452f65-49ec-428d-95b4-55cf8bc138cd 37cc5f8d-a7cb-4b50-b1e6-1418be060bf5 4ebabcfd-2cd0-42f1-bc3c-3630187cac0d 0fd18716-acb1-4121-845e-c2d8da743e30
all of these calls have error "call.in-progress.error-sip-telephony-provider-failed-to-connect-call"
v
πŸ”΅ 21:01:07:952 Received Phone Number Call Status Update: { "call_sid": "4c37cd82-4df1-4d6f-9b5f-49e36b9028f6", "direction": "outbound", "from": "+18549990221", "to": "+12144284781", "call_id": "3c5b0a69-934d-123e-26be-0629ea94f37d", "sip_status": 404, "sip_reason": "Not Found", "call_status": "failed", "account_sid": "c033b672-5b99-42ae-9ce2-b231e9a522fb", "trace_id": "1f7bc06b705bfdceace80587b1bf4eda", "fs_sip_address": "172.32.0.102:5060", "api_base_url": "" }
You will need to check with your telephony provider.
g
I'm using the free vapi phone number
v
Can you register a new number?