Call Forwarding not working in Europe
# support
n
Using the provided transferCall tool, the call terminates itself shortly after being "forwarded" by VAPI to another number. Expected behavior: transferCall tool transfers the call from the assistant to another number successfully Actual behavior. The call gets terminated after the tool has been called.
v
Based on similar issues reported by other users, try disabling the call control server message on your assistant and changing your Twilio routing region to US. This solution has resolved the same problem for other European users experiencing call termination after transfer attempts:
Copy code
1. Disable the call-control server message on your assistant
2. In Twilio settings, change the routing region to US
These configuration changes have successfully fixed call forwarding issues for users in Europe. Source: - [Discord Channel](https://discord.com/channels/1211482211119796234/1339614362742165606)
n
I now disabled the call control server message and routed twilio over US.
Issue continues: Call-ID: d87a8642-3a61-44f1-a4b9-511ce908e1b6
Another example: 90833b3d-3392-4549-a360-59cdfeb3d2e9
Please suggest a fix or detailed docs for this
s
Hey NOEMA, could you remove this phone call control server event from your Assistant Server Messages. When you select this event, you are asking VAPI to let the phone call control for call forwarding pass to you, so that's why we never forward the call, we just mark the status as Assistant Forwarding the Call. So remove this server event from your assistant server messages, and then it will work.
n
Recently it does not seem to update properly unusually often
When I get the assistant I see it was removed
On the logs I still see this
How could I handle this event on my server otherwise?
@User We are losing money by not being able to forward the calls. Call control is being made even after it was removed from the server messages via API.
please check the assistant cef97a29-4a5d-4ce9-af2f-4974937a4dd1
@User We will need a fix within the next 24 hours, I would really appreciate you looking into this. Remaining issue: After removing the "phone call control server event" Vapi is still calling our server. The payload it uses demonstrates that the assistant was updated correctly and should absolutely not be exhibiting this behavior.
k
cc: @Shubham Bajaj
n
Hi @User We’re still experiencing a critical issue: Even after the call control server message was removed correctly via API, call control events continue to hit our server instead of Vapi forwarding, as confirmed by incoming payload logs. This issue is breaking our call flow and has a direct financial impact, as we're unable to forward calls properly. Any ETA for a fix? This has been open since 4/25. Appreciate urgent attention here.
@Shubham Bajaj
s
@Noema apologies it got missed from my side.
@Noema I believe this was resolve in office hours, where i have shared with you have to set the
"phoneCallProviderBypassEnabled": true,
to false.