Call Transfer not working
# support
r
Call transfer is not working. We can hear the message send to the control URL to do the transfer, but the transfer doesn't happen. Debugging done so far: No errors were found on the VAPI side. Twilio side doesn't seem to have received the transfer request at all. Followed the debugging steps mentioned in the docs (https://docs.vapi.ai/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops). Noticed that call status does show "phoneCallProviderBypassEnabled" as true, but was unable to find how this was getting set or how to remove it. Followed suggestions from the AI assistant and converted transfer set up from using VAPI call transfer tool to live call control, but still no luck Example call id: 019bf251-55b1-7ff5-93b2-0f8cad84e62c as a example to debug. The call initially started with Twilio, and gets transferred to VAPI through TwiML. This TwiML has  phoneCallProviderBypassEnabled set to true, otherwise that transfer does not work correctly.  This information was also send to support@vapi.ai but haven't received any response so far.
v
Action Required: To enable Vapi to manage call transfers, set
phoneCallProviderBypassEnabled
to
false
in your call setup. For example, in your API or TwiML configuration, ensure:
Copy code
json
{
  "phoneCallProviderBypassEnabled": false
}
This allows Vapi to send transfer requests to Twilio and resolve the issue where transfers do not occur ([see documentation](https://docs.vapi.ai/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops)). Source: - [Debug call forwarding drops](https://docs.vapi.ai/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops)
j
I see the transfer isn’t completing even though the control URL is hit, and Twilio never receives the request. It sounds like the phoneCallProviderBypassEnabled flag might be blocking the transfer flow. I can help dig into why the call isn’t reaching Twilio and ensure the live call control setup works reliably. Can you confirm if there are any other intermediate call hooks or custom TwiML affecting this call path? @Ramesh Verve