call forwarding to a +61 number not purchased but ...
# support
o
I can't seem to get Vapi to forward/transfer calls. We're encountering an issue with the call forwarding functionality on our voice assistant. Agent ID: 56e2e72a-b6e9-411a-8327-701fe9a5f28b Latest Call ID: a98a4a5c-4c02-4012-950b-26042003cba8 Here’s what we've tried so far: Set the Forwarding Phone Number in the UI to +61 437 836 091 Included direct instructions in the prompt: "Then call the transferCall function with the destination set to +61437836091." Added the full transferCall tool definition and schema in the JSON configuration, following the Vapi documentation precisely Patched the agent with a clean JSON payload containing only valid, editable fields Despite all of the above, the assistant still fails to forward the call when prompted. Could you please investigate and advise what might be causing the failure to transfer? https://cdn.discordapp.com/attachments/1362302486915973171/1362302487087943741/Screenshot_20250417-134305.png?ex=6801e68f&is=6800950f&hm=57ef3b83be8db8b816b14359bee74f9d5aef10ea583da0a0931124e2645b7198&
k
To help track down this issue, could you share one or two: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
o
Call ID: 067888de-ccb9-42a1-8b52-9f47a393b0cc When exactly this happened (the timestamp) 13:19:19:531 [LOG] Model called tool: transferCall({"destination":"+61*********"}) What response you expected to get Expected it to transfer the call to the provided number What response you actually got instead It ended the call without transferring the call. Thank you for the swift response 😊 https://cdn.discordapp.com/attachments/1362302486915973171/1362418109939585184/image.png?ex=6802523d&is=680100bd&hm=ba167f4285a175c5eda4ae6a3386b06cbe2e1bdd50574f1bcf38e6a7ba21702b& https://cdn.discordapp.com/attachments/1362302486915973171/1362418110296228082/image.png?ex=6802523d&is=680100bd&hm=a6b0629c35eba4df5473a6bccfc5bc0576b6bef5c17b777fd1434c86e7e32dbd&
Anything else needed, let me know.
k
We are looking into it
s
Where did you purchase the number from?
k
@on_RAM
o
The agent number is from Twilio, the number I want it forwarded to is a general Australia mobile number purchased from a normal phone provider
@Sahil @Kings_big💫
s
Understood, did you enable international transfer permission?
o
Ooh, no I didn't. Haven't found that yet
s
You will need to do in order to transfer call properly on twilio end.
o
Hmm, I can't seem to find it
Are you talking about a setting withing Vapi or twillio ? I am trying to use the native transfercall function within Vapi. Should I not use that and instead build a make.com workflow to use twillio ?
@Sahil
s
Telephony things are handled by the twilio side. So, you need to enable that on their end. https://help.twilio.com/articles/223179948-Does-Twilio-Support-Dialing-International-Phone-Numbers-
I checked Twillio and it is already enabled and ticked for Australia
@Sahil
s
check DM
o
Hello 👋, I really need this resolved 🙏
@Kings_big💫
k
Sahil messaged you in your dm ?
o
He did, but hasn't responded again. I don't mean to pester, just need to get this sorted for the client
k
checking if this is resolved/solved for you?
o
Not yet
@Kings_big💫 not yet, still waiting for Sahil to get in touch with me.
all sorted 🙂
k
Marking this ticket as Solved ✅
n
How was it solved?
o
I had to update my routing from AUS to US. The call forwarding takes a long time but it still forwards.
k
This ticket has been marked as solved, and as a result, you will no longer receive any further responses. Kindly create a new support ticket to escalate your inquiry. 
o
@Sahil @Kings_big💫 any ETA on when we can use Australia for call routing instead of using USA ?
s
There is no ETA for it for now, would suggest you the SIP route which I mentioned during the call.
2 Views