just did 2 test calls with this testing agent ive been using forever (just changed prompt) and the 'endCall' function seems to have this issue where it runs and the call does end from vapis side, the bot says the 'endCallMessage' and in the logs it the result is:

"name": "endCall",
  "role": "tool_call_result",
  "time": 1728349173633,
  "result": "Success.",

but on my [caller] side the call is still there and the bot isn't there, it seems like its not actually diconnecting the call. before today the function was working fine, havent touched anything and have been using this tool a while additionally, the end reason is:

"status": "ended",
  "endedReason": "assistant-ended-call"

so im assuming the function itself is fine but just not actually hanging up the call properly * call ids: - bf86b310-f3f6-4542-ad16-b5730328e978 - fe94c418-4938-4ac9-9869-24127676f6e7

@Luka I'm sorry to hear that you're experiencing issues with the 'endCall' function. It sounds like the function is being triggered correctly and the logs are showing a successful execution, but the call isn't disconnecting as expected on the caller's side. To assist you further, I would need to check the system logs and configurations to understand why the 'endCall' function isn't terminating the call properly. However, since I don't have access to the system logs or configurations, I recommend reaching out to the support team with the call IDs you've provided. They will be able to investigate the issue in more detail and provide a resolution. In the meantime, please ensure that there are no changes in your network or system that might be affecting the call disconnection process. If you have any additional information or if there have been any recent updates or changes to your system, please provide them to the support team as it may help with the investigation. If you need anything else or have further questions, feel free to ask.

@Vapi just did 2 more tests and it looks like the issue above is only for Inbound calls (worked fine on outbound) - 9a4943cd-d14d-410f-8fba-469b431d6a51 (outbound worked) - a1a8ba5c-976a-47f3-b44a-217a640a7a17 (inbound didnt work)

@Luka Thank you for providing additional details. It's helpful to know that the issue is specific to inbound calls, as this can narrow down the potential causes. Since outbound calls are working fine, it suggests that the 'endCall' function is operational, but there might be a configuration issue or a recent change that is affecting inbound calls specifically. Given this new information, I would recommend the following steps: 1. Review any recent changes to the configurations for inbound calls to ensure that they are correct and have not inadvertently affected the 'endCall' function. 2. Check if there are any differences in the handling of inbound versus outbound calls within your system that could be causing this discrepancy. 3. If possible, test with different inbound numbers or settings to see if the issue persists across various scenarios. Since I cannot directly access or modify your system configurations, I advise reaching out to the support team with the new test call IDs and the specific detail that the issue is occurring only with inbound calls. They will be able to perform a more in-depth analysis and assist you in resolving the issue. If you have any further questions or need additional assistance, please let me know.

turns out someone was playing around with the twilio settings all good now! 🤙 @Vapi

@Luka Sweet. Have a great day!