ivy
03/10/2025, 10:45 AMVapi Support Bot
03/10/2025, 10:47 AMtransferCall function is properly configured with the correct destination number in E.164 format. For example:
json
{
"function": {
"name": "transferCall",
"parameters": {
"destination": "+1234567890"
}
}
}
3. Check Call Logs
Examine the call logs for your specific call ID to see if there are any error messages indicating why the transfer failed. [This can provide valuable insights](https://discord.com/channels/1211482211119796234/1211483291191083018/1340813822193041499).
4. Network Settings
Verify network configurations for any latency or restrictions that might affect call transfers. [Network issues can sometimes prevent successful transfers](https://discord.com/channels/1211482211119796234/1211483291191083018/1332133296347549797).
5. Try Different Transfer Mode
Ensure you're using the correct transfer mode - either blind transfer (default) or warm transfer. [Different modes may work better for your use case](https://docs.vapi.ai/call-forwarding).
If you're still experiencing issues, it could be related to one of the known issues with call transfers, such as inconsistent transfers, silent failures, or configuration problems with external systems.
Let me know if any of these steps help or if you need more specific guidance!
Sources:Vapi Support Bot
03/10/2025, 10:47 AMVapi
03/11/2025, 1:20 PMCA0a74de4368ff33becba2c5f2c8c52161ivy
03/12/2025, 1:25 AMVapi
03/14/2025, 1:13 AMivy
03/14/2025, 4:36 PMVapi
03/15/2025, 4:18 PM