call.in-progress.error-providerfault-transport-nev...
# support
c
I've been getting this error a bunch over the last few days. Any ideas why?
v
This error occurs when your telephony provider fails to connect the call within the 300-second timeout period. The most common cause is an issue with your SIP configuration or the telephony provider not responding in time. Troubleshooting step: Check your telephony provider logs to identify why calls aren't connecting, and verify your SIP configuration is correct (authentication, IP whitelisting, and proper URI formatting). Sources: - [Discord conversation about transport never connected error](https://discord.com/channels/1211482211119796234/1340144301132353637) - [Discord conversation about telephony provider issues](https://discord.com/channels/1211482211119796234/1333747605628391434)
c
Okay!
k
checking if this is resolved/solved for you?
c
It is not
@Kings_big💫
k
To help track down this issue, could you share one or two: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
c
17bddd82-3061-4814-9778-832d43443524
9e97892c-b40d-4783-9e64-151b0b5505cb
441799bd-19ef-4e7c-bd38-9ece641132f3
a0973c3e-f1f3-47be-9e29-d5215eb326d4
@Kings_big💫
k
Looking into it
c
Ty
Any update? @Kings_big💫
k
No update yet, I'll ping you
These calls weren't connected from Twilio's side. So you will have to use the call SIDs of Twilio and check with them why they didn't connect in the required time. And then come back to us and we'll continue further investigation. Post their responses. For the missing call ID, you have deleted the numbers, which is why we cannot continue further investigation. https://cdn.discordapp.com/attachments/1365414659833724968/1366350058177560586/image.png?ex=6810a027&is=680f4ea7&hm=2c46e18c375fc051626f4f921d20890f17a3bbb153b8bed03a0f9406f0f6f065&
5 Views