Are there any system logs for this Twilio error for call id e92fdcb2-99da-450d-8796-0c74e03a7807? https://api.twilio.com/2010-04-01/Accounts//Calls/CA691fc92afeae89e2dc2785db99d62721.json 2025-03-31 15:44:34 UTC { "message": "Call is not in-progress. Cannot redirect. ", "code": 21220, "user_error": true, "params": {}, "httpStatusCode": -1 }

Hi there! 👋 I don't have direct access to your specific Twilio logs for call ID e92fdcb2-99da-450d-8796-0c74e03a7807, but I can definitely help you with how to find these logs and troubleshoot the error code 21220 you're experiencing. Here's how you can access the system logs for this specific Twilio error: 1. Check the Twilio Dashboard - According to the [information I found](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313643338427273268), you can look at the error logs in your Twilio dashboard to see specific error messages related to your call failure. 2. Use the Twilio Debugger - The [Twilio Debugger and console logs](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336432457943351358) can provide errors or warnings that might give more insight into your issue. 3. Search by Call SID - Use the Call SID (CA691fc92afeae89e2dc2785db99d62721) from your error message to locate the specific call in your Twilio logs. Regarding error code 21220, this indicates that the "To" phone number is improperly formatted. Here are some troubleshooting steps: - Ensure your

forwardingPhoneNumber

is in the correct E.164 format (e.g., +15558675309) as mentioned in [this resource](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335869152535121960) - The error message "Call is not in-progress. Cannot redirect" suggests you might be trying to redirect a call that has already ended or hasn't been properly established. - Check your Twilio webhook configuration to ensure it's correctly pointing to Vapi's server. If you're still having trouble after checking the logs, you might want to contact Twilio support with your Call SID for a more detailed analysis of what went wrong. Is there anything else you'd like to know about accessing these logs or troubleshooting this error? Sources:

These error messages are safe to ignore, so I will suggest you to ignore them.