I'm noticing huge delays during outbound calls, it's been recurring up to 6s but my call outcome tool is async, so I'm lost 🙂 https://cdn.discordapp.com/attachments/1297990200940564531/1297990201096015922/image.png?ex=6717ef13&is=67169d93&hm=ecb7d4c02674d7acd5ba93538f7cea73930e18f7d58d94ddff4d5c7c4e15d98c& https://cdn.discordapp.com/attachments/1297990200940564531/1297990201355796540/image.png?ex=6717ef13&is=67169d93&hm=a0660d7cac9160200c387b4a777d27e879abd66f0ce11fda22d2e76c64cf028f& https://cdn.discordapp.com/attachments/1297990200940564531/1297990201637077083/image.png?ex=6717ef13&is=67169d93&hm=41a5cffa8910ffbaa096840373f8f37e18d8f165685da71621b6615438bdf4df&

@Jetsoccer Game I'm sorry to hear that you're experiencing delays during outbound calls. Delays can be caused by various factors, including network issues, server load, or configuration settings. Since you mentioned that your call outcome tool is asynchronous, it's unlikely to be the cause of the delay. To help you further, I would need to know more about your current setup. Could you provide more details about your call flow and the specific points at which you're noticing the delays? Additionally, please check if the

responseDelaySeconds

parameter in your configuration is set correctly, as it should be set to a low value like 0.4 seconds to minimize response delays. If everything seems to be configured correctly and you're still facing issues, it might be necessary to look into server performance or network latency problems. Please provide more information so I can assist you better.

@Vapi the response delay (wait seconds) is at 0.2s

@Jetsoccer Game A response delay setting of 0.2 seconds is quite low and should not be causing significant delays. Since you're still experiencing up to 6-second delays, this suggests there might be other factors at play. Here are a few steps you can take to troubleshoot the issue: 1. **Network Latency**: Check your network connection for any latency issues. You can perform a ping test to your API endpoint to see if there's a high round-trip time (RTT). 2. **Server Performance**: If you're self-hosting any part of your voice application, ensure that the server's performance is not the bottleneck. Look for high CPU usage, memory leaks, or other resource constraints. 3. **API Throttling**: Ensure that the API you're using for outbound calls is not throttling your requests, which can happen if there's a rate limit in place and you're exceeding it. 4. **Logging and Monitoring**: Implement detailed logging and monitoring to pinpoint where the delay is occurring. This could be before the call is initiated, during the call setup, or in the processing of the call outcome. 5. **External Services**: If your call flow involves external services or APIs, check if these services are experiencing delays. 6. **Voice API Provider Support**: Reach out to your Voice API provider's support team for assistance. They may have insights into current issues or be able to help you identify the cause of the delays. If you've already checked these areas and the problem persists, please provide more specific details about your call flow and any error logs or metrics you have. This will help in diagnosing the issue more effectively.

what additionnal info do you need?

@Jetsoccer Game Yes, when referring to network latency, it would include the latency on Twilio's network as well as the connection between your application and Twilio's servers. Here's what additional information would be helpful to diagnose the issue: 1. **Call Flow Details**: A step-by-step description of your call flow, including when the delay occurs (e.g., during call initiation, call connection, or at some point during the call). 2. **Twilio Configuration**: Any relevant configuration settings in your Twilio account that might affect call setup times. 3. **Application Logs**: Logs from your application that show the timing of each step in the call process. 4. **Network Metrics**: Data on the network latency between your application and Twilio's servers, which can be obtained through tools like

ping

or

traceroute

. 5. **Twilio Service Status**: Check Twilio's service status page to see if there are any reported issues that could be affecting call performance. 6. **Error Messages**: Any error messages or codes you're receiving from Twilio when the delays occur. With this information, we can better understand where the bottleneck might be and how to address it. If you're unable to gather this information or if you're not sure how to interpret it, reaching out to Twilio's support with your observations about the delay might be the best next step. They can provide more detailed insights into their network performance and help troubleshoot the issue from their end.

this is not helpful

Im experiencing the same and it is unusable, I would like to replace the part that is adding latency so i can replace it, but the bot is not giving any useful information. I'm new here so I don't know how this works. Is there a way to get a human to help us? @User @Shubham Bajaj @Sahil

create a different support ticket please.