Issue with VAPI End Call Reason: call.in-progress....
# support
f
Hello, I'm experiencing an issue with VAPI related to call termination. When calls end, I'm receiving the following end call reason: call.in-progress.twilio-completed-call I have reviewed the documentation but could not find any information clarifying what this status means. This appears to be causing a problem because: - We are not receiving the end-of-call-report webhook when this specific end call reason occurs - This is disrupting our call tracking and reporting processes Could you please provide clarification on what this end call reason indicates, why the end-of-call-report webhook is not being triggered and any recommended steps to resolve this issue? Thank you for your assistance. Best regards https://cdn.discordapp.com/attachments/1409489916005711873/1409489916185808957/screenshot_vapi.png?ex=68ad9147&is=68ac3fc7&hm=749393f2dc208c178104580ae98f59ae75e792e8cd0c0af8219702f08e05674b&
CALL IDS: cba10698-3c18-4408-b780-973b55a67522 2f43d684-7cec-4187-896f-b82a50a9c779 4acd68c2-8eaa-46ec-bc56-0e67e3db592f
t
The call went through on Twilio but unsuccessful on vapi? Is that what you mean @Fran
f
Yes, that’s what it seems, but the calls all end the same way and yet some end with this status (and therefore do not generate summary, transcription, etc.) while others end with a standard status that is indeed in the VAPI documentation. It is quite strange.
c
Hey Fran, we flagged this to our team and we are actively looking into this.
f
Thank you very much
I just noticed this happens when the assistants has structured data variables, don't really know if that's the problem but maybe it can help you to find the issue
c
Thank you for the additional information. I will pass this along to our team who is investigating this issue
w
I am also trying to understand how to handle this end reason... Following
c
Could you provide a call id so we can review the logs?
w
019a9d4e-e541-7bb2-a524-fc154e0afa9e
019a9c97-da11-722b-ad3e-53a3cee17fba,019a9c7a-16e0-722b-ad1c-8c82b2aaf49a,019a9c6e-741b-7557-b617-c722f487f755,019a9c61-8a24-7eee-9df0-17bc6706888d
c
This should be resolved now. If you are still encountering this error, please let us know
3 Views