### Answer This appears to be a synchronization issue between Twilio and Retell where the call status didn't properly update on Retell's side after Twilio ended the call. Troubleshooting steps: 1. Check your telephony provider logs - Since you're using Twilio with Retell, check the logs in your telephony provider to see what occurred on their side. [(1) ]() 2. Verify your SIP trunk configuration - Double-check your configuration and make sure you imported the correct information. If the configuration is incorrect, delete the imported number and re-import it. 3. Review the call detailed log - The call detailed log in Retell contains the disconnection reason, SIP error code, and error message, which should help identify the root cause. For this specific stuck call issue: The available documentation doesn't cover manually clearing stuck call states. This type of issue typically requires direct support intervention. Next steps: - Visit [Contact Sales]() - Visit [) When contacting support, share the specific call ID and mention that the call shows as ongoing in Retell but completed in Twilio. They can investigate the backend state and help resolve the stuck call.

​ To learn more, see the sources I considered: [[1] Custom Telephony Overview](https://docs.retellai.com/deploy/custom-telephony) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.