Call id: 226fe5b9-222b-43bd-8841-5e806dbb671b The endcall funciton is being logged - but the call isn't ending on the userside - it just stays stuck is something interfering with the tool call also the endcall function doesn't always work reliably i used trigger endcall function in prompt

message has been deleted

@Vapi sure Call ID : 226fe5b9-222b-43bd-8841-5e806dbb671b prompt:

12. After all questions have been asked, be sure to trigger the endCall function.

@Irfan Thank you for providing the call ID and the context of the prompt. It seems like the end call function should be triggered after all questions have been asked. If the call is not ending on the user side and the function is not working reliably, there could be several reasons for this issue: 1. There might be a bug in the code where the end call function is implemented. 2. The function might not be receiving the correct parameters to execute properly. 3. There could be a network or API issue that is preventing the function from completing its task. To resolve this, we should first ensure that the end call function is being called with the correct parameters and at the right moment in the code. If everything seems correct on your end, it might be necessary to look into the logs or error messages for more detailed information about what is going wrong. Since I am here to assist, let's try to trigger the end call function now. If you have specified an end call message or phrases, please provide them so I can include them in the function call. If not, I will proceed without them. Shall we go ahead and try to end the call?

can you give me an example of the correct parameters

@Irfan Certainly! The correct parameters for an end call function typically depend on the specific API or system you're using. However, a common parameter set might include: - `callId`: A unique identifier for the call session that needs to be ended. - `reason`: An optional description of why the call is being ended. - `timestamp`: The time at which the call is being ended. For example, if you're using a hypothetical end call function, the parameters might look something like this:

json
{
  "callId": "226fe5b9-222b-43bd-8841-5e806dbb671b",
  "reason": "All questions answered, ending the call.",
  "timestamp": "2023-04-14T12:34:56Z"
}

Please note that this is just a generic example. The actual parameters and their format can vary based on the system you're working with. If you're experiencing issues with the end call function, it's important to refer to the documentation for the specific API or system you're using to ensure you're providing the correct parameters. If you need further assistance with the actual parameters for your specific end call function, please let me know, and I can help guide you through it.

@Shubham Bajaj help please

Hey @Irfan can you set your end call tool async to false and then try again.

logs

🔵 16:11:14:963 No Sync Tool Calls to Say Start.

@User hey we don't specify any end call tool on our end - we use Vapi's built in one

logs

🔵 16:11:26:041 Deleting Daily Room... 🔵 16:11:26:041 Process

receive

Exited. Code: null. 🔵 16:11:26:030 Live Call Manager Ending...(assistant-ended-call) 🔵 16:11:26:030 Conversation Buffer Appending Tool Result. Emitting "conversation-update"... [ { "role": "tool_call_result", "time": 1731427886029, "secondsFromStart": 89.691, "name": "endCall", "result": "Success.", "toolCallId": "call_7h72zzarKmOTk4V3GoegDfPp" } ] 🔵 16:11:26:029 Say Request Finished 7 (say: "Goodbye") Hey @Irfan my bad I mixed up two call ids as you can observer from the logs the call was ended by the assistant using endCall function. It came from daily side, can you share other call ids for whcih it's not working so i can try to reproduce and eventually raise the issue.

Hey @Shubham Bajaj , I've noticed that the endCall tool is not working for me too, neither on web calls nor phone calls. Here is an example phone call: 1e21691d-1f57-4348-b59c-68ddc368acd4

Hey @Ricardo Basto please allow me sometime to get back to you on this. @Irfan Apology for hijacking your thread

Was this ever resolved?

Hey Mr.OOO, yes it's resolved.