Unknown call termination reason.
# support
b
I'm triggering an assistant from Make.com. Looking at the logs, it seems the call is failing before it connects, but the assistant is still trying to connect. What am I doing wrong? Example call: 43603943-dc0a-468e-ab49-b4a0b63386e1
v
message has been deleted
@battletram It sounds like there might be an issue with the configuration or the way the assistant is being called from Make.com. To assist you better, I'll need a bit more information: 1. Can you confirm that the assistant ID you're using is correct and that the assistant is properly configured within the VAPI platform? 2. Have you checked if there are any specific error messages in the logs that could give us more insight into why the call is failing? 3. Is this a new integration or has it worked previously? Once we have more details, we can troubleshoot the issue more effectively. If the assistant ID is correct and there are no clear error messages, it might be necessary to review the integration setup on Make.com to ensure it's aligned with VAPI's requirements. If you're unsure about the assistant ID or the configuration, please ask support for more info on this.
You can continue this conversation by mentioning me in the message.
b
@User 1. Yes, as far as I can tell it's configured correctly. Web calls work ok. 2. Yes, the logs look like it is trying to talk before the call connects screenshot attached. Also looks like a 400 error for status updates. 3. Brand new, never worked. https://cdn.discordapp.com/attachments/1285639021963382867/1285640229814009866/image.png?ex=66eb0144&is=66e9afc4&hm=e98709fa1f7f236ce4809a3e5c5b9c1d6a72b64a148757ccc7f5530c6cfc870d&
s
are you sure call is failling before it's connected, check call id again please.
b
Ahh thanks, I guess the termination hadn't updated yet - thanks
2 Views