I am writing to raise a concern regarding the concurrency handling of outbound calls through your platform. Currently, my account is provisioned with 10 channels, and when I initiate multiple outbound calls, all channels are utilized simultaneously. However, my SIP trunk provider (Tata Communications) allows only 1 concurrent call. Because of this, calls beyond the single allowed channel are rejected by Tata, which causes operational issues. To resolve this, I would like to request the following: An option in the VAPI platform to adjust or limit the number of concurrent outbound calls. Ideally, a configuration where I can specify the maximum concurrency (e.g., 1 call at a time) to match the limitations of my SIP trunk. This feature will prevent unnecessary call rejections and ensure smooth call handling aligned with the SIP trunk capacity. I would appreciate it if you could prioritize enabling such a setting, or let me know if there is an existing method/workaround available in VAPI to achieve this. Thank you for your support, and I look forward to your response.

To ensure only one outbound call is active at a time, you can implement a simple batching loop in your code to initiate calls sequentially. For example, in Node.js:

js
for (const customer of customers) {
  await makeVapiCall(customer); // Wait for each call to complete before starting the next
}

This approach ensures that only one call is dialed at a time, matching your SIP trunk's single-channel limit. Adjust your batch logic to use

await

or similar mechanisms to prevent concurrent calls from being initiated simultaneously. Reference: See Vapi's concurrency and queue management documentation for more details on handling call limits programmatically: [Vapi Call Queue Management](https://docs.vapi.ai/calls/call-queue-management). Source: - [Vapi Call Queue Management](https://docs.vapi.ai/calls/call-queue-management)

no but there is a option in vapi itself by adjusting my concurrecny to 1 and i dont have to write and all

Hi raja, outbound campaigns and concurrent calls are managed based on your Vapi organization's concurrency limits. Here's what you need to know: 1. Concurrency Behavior: - When making outbound calls, Vapi will start a maximum number of calls equal to your concurrency limit - Additional calls are queued and retried later as concurrency slots become available 2. Important Note: - Concurrency limits are on the Vapi side - Your telephony provider (in this case, Tata Communications) may have different rate limits To work with your Tata Communications 1-call limit, you have a few options: 1. Use Twilio's Call Queue Management to handle the concurrent calls: - Set up a queue system that respects your SIP provider's limits - Process calls one at a time - Queue excess calls for later processing 2. Consider requesting a feature from Vapi to add provider-specific concurrency limits. This would help match your SIP trunk's capabilities. In the meantime, you might want to implement a queue management system to ensure calls are processed one at a time to match your SIP trunk's limitation.

SO WE CANT DIRECTLY SET THE CONCURRENCY LIMIT IN VAPI?

If you would like to launch a campaign with 1 call at a time, use the phone numbers outbound section instead of outbound campaigns. This will allow you to upload a CSV file with leads/contacts and it will call each number one at a time.