----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Function Calling]() * [Call Ended Reason]() * [Create Assistant]() * [Outbound Sales Example]() -----------------------------

### Answer This issue might be related to specific instances where the assistant encounters errors or conditions leading to unintended call termination, despite the

endCallFunctionEnabled

being disabled. The

Call Ended Reason

documentation details various reasons why a call might end, including assistant-related errors or issues within the AI processing pipeline [(1)]() . For instance, issues like

assistant-error

,

pipeline-error-***

, or even

unknown-error

could potentially cause the call to end unexpectedly. Additionally, there might be specific circumstances under which the assistant could interpret conditions in a way that triggers call termination. If you're encountering this issue frequently or under peculiar conditions not documented, it may warrant further investigation into the assistant's logic or error handling mechanisms. Given the information provided, the best course of action would be to review your assistant's configuration, particularly focusing on any error handling or conditions that might inadvertently trigger call termination. If the problem persists and doesn't align with the documented reasons for call endings, consider reaching out to the platform's support or community forums for further assistance or to report a potential bug.

I've now fixed my backend and haven't noticed any issues