Mohammad Anas Ahmad
11/04/2025, 3:48 PMVapi Support Bot
11/04/2025, 3:51 PMendedReason for your call using the Vapi API. Run the following command (replace {call_id} and YOUR_API_KEY):
bash
curl -X GET "https://api.vapi.ai/call/{call_id}" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json"
If the endedReason is not assistant-forwarded-call, review your assistant's configuration—ensure phoneCallProviderBypassEnabled is set to false and remove "phone-call-control" from serverMessages if present. This will help you pinpoint if the issue is with your configuration or the telephony provider.
For more details, see the [Debug call forwarding drops guide](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops).
Source:
- [Debug call forwarding drops](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops)Mohammad Anas Ahmad
11/04/2025, 5:42 PMVapi Support Bot
11/04/2025, 5:44 PMphoneCallProviderBypassEnabled property is not a direct setting in the dashboard UI, but is part of the transfer tool's configuration when defined via API or JSON. To ensure your call transfer works, make sure your transfer tool includes the required destination parameter, like this:
json
"parameters": {
"type": "object",
"properties": {
"destination": {
"type": "string",
"enum": ["+1234567890"], // Replace with your target number in E.164 format
"description": "The destination to transfer the call to."
}
},
"required": ["destination"]
}
Also, remove "phone-call-control" from your assistant's serverMessages if present. This should resolve most transfer issues. For more, see the [call forwarding guide](https://docs.vapi.ai/call-forwarding).
Sources:
- [Vapi documentation: call forwarding](https://docs.vapi.ai/call-forwarding)
- [Debug call forwarding drops](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops)Chiranjeet Mishra
11/06/2025, 6:01 AM