dead-brownD
VAPI•6mo ago
dead-brown

Issues with Silence Timeouts and Batch Calling via API

I’m writing to report two issues we’re experiencing:
  1. Unexpected Silence Timeouts
We’re experiencing an issue where several calls are being terminated due to a silence timeout, even though our assistant’s configuration and the recorded audio indicate that this shouldn’t be happening. For instance, in one example call, the callee finishes speaking a sentence, and immediately afterward, the call ends with a silence timeout status. This is unexpected, so I’m currently reviewing the RTP analysis to see if it provides any useful insights.

  1. Batch Calling and Concurrent Limit Errors
    We also need a way to schedule batch calling. Right now, we’re triggering calls through Go High Level, but we’re hitting concurrent limit errors. We’d like to continue scheduling triggers and calls from Go High Level using the API, but we need a plan or best practice for handling batch calls without exceeding concurrency limits.
Specifically:
• What do we need to include in our API calls to manage batch logic?
• Is there a parameter or recommended method to ensure calls are queued or processed batch by batch to stay within concurrency limits?
• Are there built-in queuing or throttling mechanisms in VAPI we should be using?

Thanks in advance for your help in resolving these issues. Let me know if you’d like call IDs or logs for the silence timeout examples.

callId: be26e316-8e05-4e3d-951a-0f2357652f92

c1e8fa53-f5d8-49d2-8109-315a6aaab986
Was this page helpful?