Dev
10/03/2025, 10:08 AMVapi Support Bot
10/03/2025, 10:10 AMDev
10/03/2025, 10:13 AMGIDEON
10/03/2025, 1:37 PMDev
10/03/2025, 2:42 PMChiranjeet Mishra
10/06/2025, 7:50 PMendedReason value in your call logs or via the API. This will help diagnose whether the issue arises from the assistant, customer line, or telephony provider.
2. **Phone Number Format**: Ensure the phone numbers are in the E.164 format, including the country code (e.g., +14151234567).
3. **Outbound Configuration**: Verify your setup for outbound calls. You should have correctly configured the assistant and phone number. Refer to [Outbound Calling](https://docs.vapi.ai/calls/outbound-calling) for detailed guidance.
4. **Configuration Dependencies**: Make sure phoneCallProviderBypassEnabled is set to false unless you're managing call control within your telephony provider. Also, check that the "phone-call-control" isn’t overriding Vapi's call handling.
5. **Logs and Errors**: Analyze your telephony provider's logs for any errors or unsuccessful transfer attempts. If using Twilio, Vonage, or similar, check their specific error logs.
6. **Concurrency Limits**: If scheduling multiple calls, ensure your Vapi concurrency limit is adequate for the volume of calls being sent. For any limits from your telephony provider, ensure they aren't being exceeded.
Review these points, and it should help narrow down or resolve the issue. If the call shows successful forwarding but still drops, or you have another specific problem, please provide more details so I can assist further.
You can learn more about handling such issues in the [Debug call forwarding drops guide](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops).Saad
10/08/2025, 10:51 AMGIDEON
10/08/2025, 11:45 AMGIDEON
10/08/2025, 11:46 AMSaad
10/08/2025, 12:39 PMGIDEON
10/08/2025, 12:44 PMassistantId 1a93fe38-c2de-4237-a130-febabe4921b9 Does Not Exist."GIDEON
10/08/2025, 12:46 PMChiranjeet Mishra
10/10/2025, 5:41 AM