I have integrated a Vapi agent with a Make.com scenario, the scenario takes contacts out of a google sheet and passes the data bundles through an https request to the agent with all the dynamic data, on my end all the data is getting transferred and the agent is receiving everything. The JSON code is all correct but I am facing the error message shown in my Vapi call logs, I have tried changing the number the agent uses to make the calls. With the same I have tried running the Make.com scenario and also manually dialing the numbers in the actual Vapi UI...Still no luck. Call ID- b5e93612-1b9c-4f19-9f10-7db8f236dc20 Start time: (Says N/A) Expected response: Outbound call to actually be made to the number. Received response: The call did not get placed and returned the error "call.in-progress.error-sip-telephony-provider-failed-to-connect-call" https://cdn.discordapp.com/attachments/1363864693890093087/1363864694468644915/Screenshot_2025-04-21_151006.png?ex=6807957a&is=680643fa&hm=d9c3fed13b30d4cf0b70f8f29d79ce7b74408d937c5a9c8867c52728197b776a&

To help track down this issue, could you share one or two: - 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!

There are no timestamps, I expected the agent to actually place the call to the desired number, I got the error : "call.in-progress.error-sip-telephony-provider-failed-to-connect-call" and the call was not placed... https://cdn.discordapp.com/attachments/1363864693890093087/1363873589962473595/Screenshot_2025-04-21_152417.png?ex=68079dc3&is=68064c43&hm=c85f7c837927aabf3bdb00fd8a438432313094a42590bee8e4cc631373d0320d&

🔵 12:57:38:561 Call

b5e93612-1b9c-4f19-9f10-7db8f236dc20

Waited 300s But Transport Never Connected.

646a0be1-d764-4cba-bf70-78d4f3c4b712 31156bd0-493b-43be-bad5-b3ebca7d6793 3f47afc7-1ba8-43f4-b253-c41fa5485d41 b39c48a7-e32a-4e1b-b23e-2c6d5c40ba19 0279451f-316e-4c20-89dc-5d023144b0b3 2452e3cb-efd3-4f53-a8a4-1049a70db84a 84d1e04f-f71c-4422-a4d7-be0b6c7b8823 0bdadb82-9a78-4c01-bc8f-b3ff9b4190b9 7597b914-1151-4cd0-90cf-fef515e9ce76

looking into it.

Issue has been solved thanks Shubham!