ShinyChee
09/03/2025, 5:31 PMVapi Support Bot
09/03/2025, 5:33 PMdestination property in its parameters, which is a common cause for transfer failures.
Try updating your tool's parameters section as follows:
json
"parameters": {
"type": "object",
"properties": {
"destination": {
"type": "string",
"enum": ["+1234567890"], // Replace with your external number in E.164 format
"description": "The destination to transfer the call to."
}
},
"required": ["destination"]
}
Update this in your tool configuration and test again. If the issue persists, check that your SIP provider supports SIP REFER for transfers.
Source:
- [Vapi documentation: call forwarding](https://docs.vapi.ai/call-forwarding)ShinyChee
09/03/2025, 5:54 PMAlishba_imran
09/04/2025, 9:46 AMAlishba_imran
09/04/2025, 9:46 AMShinyChee
09/04/2025, 4:09 PMAlishba_imran
09/04/2025, 4:20 PMChiranjeet Mishra
09/05/2025, 12:55 AMendedReason in your call logs. If it's not assistant-forwarded-call, review your assistant configuration.
2. Check Server Message Configuration: Ensure your assistant’s serverMessages does not include "phone-call-control" unless implementing custom transfer logic. It could be overriding Vapi's management.
3. Phone Call Provider Bypass: Confirm that phoneCallProviderBypassEnabled is set to false for Vapi to handle call transfers.
4. Validate Transfer Scenarios: Certain types of transfers may not be supported. For instance, web-to-phone transfers are not supported.
5. Telephony Provider Logs: Examine your telephony provider’s logs for transfer-related errors. You may need to check Twilio, Vonage, or others for issues with transfer execution.
6. SIP Calls: If applicable, analyze SIP packets using a tool like Wireshark. Look for "REFER" packets which indicate transfer requests to your SIP provider.
For more detailed troubleshooting, refer to the [Debug call forwarding drops guide](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops).
I hope this helps resolve the issue.