Hi Vapi support team, We are facing this problem for a few days now: Error processing batch call 690e116e391f552a500bad95: VapiError: "timeout" at Calls. (/app/node_modules/@vapi-ai/server-sdk/dist/cjs/api/resources/calls/client/Client.js:191:27) at Generator.next () at fulfilled (/app/node_modules/@vapi-ai/server-sdk/dist/cjs/api/resources/calls/client/Client.js:41:58) at processTicksAndRejections (node:internal/process/task_queues:95:5) { statusCode: undefined, body: undefined, rawResponse: { headers: Headers {}, redirected: false, status: 0, statusText: 'Unknown Error', type: 'error', url: '' } }

Suggestion: This type of timeout and "call not triggered" issue is a known intermittent problem with Vapi, often linked to SIP misconfigurations or webhook/network instability. As a first step, please review any recent changes to your SIP trunk or webhook configurations. If you haven't changed anything recently, try reverting to a previous working configuration and monitor if the issue persists. If the problem continues, consider reaching out to Vapi support with your call ID and a summary of your troubleshooting steps for further assistance ([see discussion](https://discord.com/channels/1211482211119796234/1372358449761091584)). Source: - [Vapi Discord: Outbound call not executed and no webhooks sent](https://discord.com/channels/1211482211119796234/1372358449761091584)

We are triggering batch calls, from 2 to 100 customers. Some batches seem to fail randomly. There was no change in sip configuration, and also no recent change in any other logic.

Hi KAYRA HAN, If you're experiencing issues with calls dropping after initiating a transfer, you can follow a systematic troubleshooting approach outlined in our guide [here](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops). Here are the key steps: 1. Check Vapi Initiation: - Use the Vapi API to verify if the forwarding was successfully initiated. Ensure the

endedReason

is

"assistant-forwarded-call"

. 2. Assistant Configuration: - Ensure your assistant configuration does not contain

"phone-call-control"

unless implementing custom logic. Set

"phoneCallProviderBypassEnabled"

to

false

for standard Vapi-managed transfers. 3. Telephony Provider Logs: - Retrieve the

phoneCallProviderId

from your Vapi call object and check call logs on your telephony provider's dashboard for transfer errors. 4. SIP Trunking (if applicable): - If using SIP, analyze the REFER packet data with Wireshark to verify if Vapi sent the transfer request. Common causes include misconfigured destination numbers, errors in call logs, or unsupported transfer scenarios like web-to-phone. If the

endedReason

is anything other than

"assistant-forwarded-call"

, there might be configuration issues to resolve. For detailed information, please refer to the [troubleshooting guide](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops).

Hi Aniah, no, in the batch 690e116e391f552a500bad95 the complete batch just failed with "timeout" error. We've experienced this several times and as we do not have any other response, we can't troubleshoot on our end. What else can we check? Most batches seem to go through, and some batches fail.

Hi Kayra, Thanks for the additional details. There was some recent SIP-related degradation on our side, so what you experienced may have been a rare occurrence tied to that incident. Please try running a few new calls to see if the issue persists. If it happens again, feel free to share the individual call IDs that show up in your call logs — we’re able to investigate those directly. Unfortunately, we can’t inspect or debug batch IDs themselves, only the specific call IDs generated within a batch. Happy to take a deeper look if you encounter another failure.