Call IDs: -

bd06eaa4-f874-4096-9cf5-80f359567e72

(screenshot 1) -

d1faaf26-39bd-4b05-9f37-98ef120ddb99

(screenshot 2) -

d75e3762-7cda-4c1a-a6a7-6bbab69126aa

(screenshot 3) Recording contains callee speech, I can hear myself, but call just ends after the timeout setting. Tried adjusting silence timeout to 30 seconds, but that did not help. Messaging endpoint receives

'endedReason' => 'silence-timed-out',

Things seem to break only if I add a tool I created today (

appointment-reject-reason

). When it's in the assistant, call ends with silence timeout, when I remove it, calls work again. https://cdn.discordapp.com/attachments/1270436550907396096/1270436551201132594/image.png?ex=66b3b1bd&is=66b2603d&hm=948e79a68bebf316dd6ce706b58097fe3bf516c0d87795207145f31d4236e310& https://cdn.discordapp.com/attachments/1270436550907396096/1270436551566033037/image.png?ex=66b3b1bd&is=66b2603d&hm=222b882280b50bd18e21bec9b307e4c1239d087cffb0fba5c9ca0a88e1d06bee& https://cdn.discordapp.com/attachments/1270436550907396096/1270436551850983445/image.png?ex=66b3b1bd&is=66b2603d&hm=633a06aeba77451abec642f474364485307bfa2edca80dc877c0ae97b14bb746&

@edvordo It sounds like the issue may be related to the integration of your custom tool

appointment-reject-reason

within the assistant. Since the calls are ending with a 'silence-timed-out' reason, it's possible that the tool is not handling the audio input or output correctly, leading to unexpected silence which triggers the timeout. Here are a few steps you can take to troubleshoot the problem: 1. **Review the Custom Tool Code**: Ensure that your

appointment-reject-reason

tool is correctly processing the audio streams. Check for any bugs or logic errors that might cause it to not output any audio. 2. **Check for Conflicts**: Verify if there are any conflicts between your custom tool and other parts of the assistant. It's possible that the tool is interfering with the normal flow of the conversation. 3. **Test the Tool Separately**: Try testing the

appointment-reject-reason

tool in isolation to see if it functions as expected without the rest of the assistant's components. 4. **Logs and Debugging**: Review the logs for any errors or warnings that occur when the tool is added to the assistant. Debugging information can provide insights into what might be going wrong. 5. **Adjust Tool Configuration**: If there are configurable parameters for your custom tool, experiment with different settings to see if that resolves the issue. 6. **Contact Support**: If you've gone through these steps and the issue persists, it might be helpful to reach out to the support team with detailed information about the problem, including the call IDs and any relevant logs or error messages. If you need further assistance or if you'd like me to perform any specific actions, please let me know!

@Vapi The appointment-reject-reason tool configured endpoint is never called. The tool is also set as an async tool and is just supposed to extract a reason patient reject offered appointment date.Tool works fine in isolation (call id: a2984f8c-efc2-4412-9380-05439ed9bf98).

@edvordo Given that the

appointment-reject-reason

tool works fine in isolation, the issue might be with how it's integrated into the assistant's workflow or how the assistant handles asynchronous tools. Here are some steps you can take to further investigate and resolve the issue: 1. **Check Integration Points**: Ensure that the tool is correctly integrated into the assistant's workflow. The assistant should be configured to call the tool at the appropriate time and handle its asynchronous nature properly. 2. **Review Assistant Configuration**: Make sure that the assistant is set up to handle asynchronous tools and that there are no configuration errors that could prevent the

appointment-reject-reason

tool from being called. 3. **Examine Call Flow**: Look at the call flow to see if there's a logical point where the tool should be invoked but isn't. There might be conditions or branches in the flow that are inadvertently bypassing the tool. 4. **Check for Errors**: Review any error logs or messages that might indicate why the tool's endpoint isn't being called. This could provide clues about what's going wrong. 5. **Test with Simplified Flow**: Try simplifying the assistant's call flow to include only the necessary components to reach the

appointment-reject-reason

tool. This can help isolate the issue. 6. **Endpoint Accessibility**: Verify that the endpoint configured for the

appointment-reject-reason

tool is accessible from the assistant's environment. There might be network or permission issues preventing the call. 7. **Contact Support**: If you're still experiencing issues after these steps, it may be necessary to contact support with detailed information, including the call IDs where the tool worked in isolation and where it failed when integrated. If you would like me to take any specific actions or if you have any other questions, please let me know!

@Vapi I adjusted the assistant definition, things work now. Thanks.

@edvordo Sweet. Have a great day!