An error occurred in this call: call.in-progress.e...
# supports
Snow
04/22/2025, 8:51 AMAn error occurred in this call: call.in-progress.error-sip-telephony-provider-failed-to-connect-call
https://cdn.discordapp.com/attachments/1364161626089193502/1364161626395115560/image.png?ex=6808aa04&is=68075884&hm=132ea9c708ef197f6a3fc6836215c8f6b2090ce6b905212f8ad8b77485030301&
s
Sahil
04/22/2025, 9:22 AMTaking a look, can you send me the call_id?
s
Snow
04/22/2025, 9:24 AM019616d4-832f-4177-8557-0c2d785704d6
Snow
04/22/2025, 9:24 AMVapi sip has problem. kindly fix it.
s
Sahil
04/22/2025, 9:36 AMThanks, will get back to you soon.
v
Vadym
04/22/2025, 9:50 AMHi @Sahil
I hope it's okay to jump in. I've been integrating with VAPI only recently but I also started experiencing this error this morning.
Here's one example call_id: a0fb606e-4921-4b33-9952-079174613906
Thank you in advance.
Vadym
04/22/2025, 10:18 AMJFYI, calls go through now. 🤔
s
Sahil
04/22/2025, 10:32 AMCan you try again is it working now? @Snow @Vadym
Sahil
04/22/2025, 10:32 AMcan you make few more test calls? @Vadym
v
Vadym
04/22/2025, 10:33 AMSure, I'll try now
Vadym
04/22/2025, 10:35 AMThe problem is back on the first try: call_id = 2910ba66-a5a7-4fc4-b2e0-aeb3f790128a
Vadym
04/22/2025, 10:36 AMBut the second time it worked 🤔
Vadym
04/22/2025, 10:38 AM3. error 4. works. 5. error 6. works
Vadym
04/22/2025, 10:38 AMSeems to be erroring every second attempt
s
Sahil
04/22/2025, 10:39 AMtry once more please we just restarted the server so it is reflected in all the instances
v
Vadym
04/22/2025, 10:39 AMOkay
Vadym
04/22/2025, 10:44 AMMade seven attempts in a row after the server restart:
1. Works
2. Works
3. Works
4. That error a3d78730-ea12-46b2-974b-1626eede819f
5. That error d6cdc457-e548-4e2e-a7f5-f4805a405823
6. Works
7. Works
s
Sahil
04/22/2025, 10:46 AMThis is a different issue, like the request is getting timed out
v
Vadym
04/22/2025, 10:50 AMCould it be something in my Twilio SIP trunk configuration making it time out?
Vadym
04/22/2025, 10:55 AMThere are no related errors or even logs for those errored calls in Twillio.
And these are the allowed IP addresses (as per the docs): 44.229.228.186, 44.238.177.138
Vadym
04/22/2025, 10:57 AMI can whitelist all IPs for testing to see if it makes a difference.
Vadym
04/22/2025, 11:03 AM> I can whitelist all IPs for testing to see if it makes a difference.
JFYI, It didn't
s
Sahil
04/22/2025, 5:40 PMIt should be fixed as well
Sahil
04/22/2025, 5:40 PMCan you try again?
r
Rw1
04/22/2025, 5:42 PMI have the same problem! Do I need to create a new post?
s
Sahil
04/22/2025, 6:09 PMsend me the call_id pls
r
Rw1
04/22/2025, 7:19 PM3a65303a-54a5-4778-99c7-0712eac293b1
s
Sahil
04/23/2025, 12:19 AMIt is fixed.
v
Vadym
04/23/2025, 9:01 AMI've made 5 back-to-back calls and everything worked flawlessly. Thank you so much for your awesome support, Sahil! 🙏
l
Leo
04/29/2025, 12:42 PMComo foi solucionado? Também estou passando pelo mesmo problema
332809c8-95cb-4ee6-8b4f-0e18111866ea
k
Kyle Brunker
04/30/2025, 9:37 AMThis 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.
2 Views