Hi there, we're having a consistent issue for some reason within our application, which we host in a lovable front end using the VAPI SDK. Our users are calling in using the Conversation AI agent and then it cuts off at 10 minutes. We don't know why. It's not 10 minutes on the dot. It's kind of like 9 minutes 20, it could be just over 10 minutes, but in and around that 10 minute mark. And it's frustrating because users need at least 20 minutes to speak to the AI agent. We're hosting it in a lovable front end. We use SuperPace in the back end. We're using N8N to connect the workflows. It's powered by CloudSonic 4.5. We've got a variety of tools. Can anyone think of what might be going wrong? @JP | Exited Founder

Thanks for sharing the details. Based on Vapi's default settings, calls are typically limited to 10 minutes (

maxDurationSeconds: 600

). Could you please check if your assistant or call configuration has this limit set, or if you've customized the

maxDurationSeconds

parameter in your Vapi dashboard or code? This will help pinpoint if the cutoff is due to this setting. Let me know what you find! Source: - [Vapi Assistant API Reference: maxDurationSeconds](https://docs.vapi.ai/api-reference/assistants/create)

Hi JP | Exited Founder, If you're experiencing issues with call forwarding where calls drop immediately after initiating a transfer, here's a systematic approach to troubleshoot: 1. **Verify Forwarding Initiation**: - Use the Call API to check the call logs and

endedReason

field. A successful forwarding should show

"assistant-forwarded-call"

. You can use this [API endpoint](https://api.vapi.ai/call) to retrieve the information. 2. **Configuration Check**: - Make sure the

serverMessages

configuration does not include

"phone-call-control"

, unless you're handling custom call logic. - The

phoneCallProviderBypassEnabled

should be set to

false

for standard Vapi-managed transfers. 3. **Supported Scenarios**: - Confirm that your transfer scenario is supported. For instance, web-to-phone and PSTN-to-SIP are not supported. 4. **Telephony Provider Check**: - If the call logs indicate a successful forwarding, but the call still fails, you might need to check your telephony provider's logs for errors using the

phoneCallProviderId

. For detailed troubleshooting steps and solutions based on common root causes, refer to the [call forwarding guide](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops). If issues persist with specific providers, like 11labs not synthesizing audio, they might be temporarily affected, similar to past incidences you've encountered. Understanding the specific error code or reason why calls drop can significantly narrow down the troubleshooting focus. More on possible

endedReason

values can be found [here](https://docs.vapi.ai/calls/call-ended-reason). If the problem continues or you're observing patterns, employ alerts for calls with unexpected

endedReason

values to catch these issues early. Feel free to tweak your configurations or delve into more advanced analyses if needed.