transfer call tool not work everytime
# support
r
Call Id : 4ae25c6c-a3fa-49e5-a7f9-2509b1d902f5
v
Thank you for sharing the Call ID. To help diagnose why the transfer call tool does not work every time, could you briefly describe what happens when the transfer fails (e.g., does the call drop, is there an error message, or does nothing happen)?
r
@User @Vapi Support Bot I don't have more details but at above call call tarsfer not worked.
v
Thank you for confirming the issue. To help us investigate further, could you let us know if the call simply ends, stays connected without transferring, or if you see any error message when the transfer fails?
r
it's disconnected
c
In the logs we are seeing that the assistant triggered the endCall function due to the endCallPhrase being said.
Copy code
"endedReason": "assistant-said-end-call-phrase",
Also in this specific call, it appears that there was nothing said to indicate the user wanted to be transferred, so the transfer tool was never called.
r
cc14f44e-8e21-4ca4-a2ac-81728053fd7b, works ae8e679e-fb10-4a69-b995-1032599a0287, not works
@Vapi Support Bot
v
Suggestion: Please ensure your
transferCall
tool includes the required
"destination"
property in its parameters. Here’s a sample configuration you can use:
Copy code
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 your tool with this structure and test again. This often resolves transfer issues where the call disconnects instead of forwarding. [See reference](https://discord.com/channels/1211482211119796234/1372460612499804270) Source: - [Vapi SIP Trunking Telnyx external number call forwarding troubleshooting](https://discord.com/channels/1211482211119796234/1372460612499804270)
r
@User
c
Thanks for the call Ids. We will be reviewing the PCAP file and will get back to you shortly with an analysis
r
any update ?
c
We apologize for the delay in responses lately. We are in process of making some changes to our workflow in how we handle support requests. The good news is that we are starting to get back on track of having a 48 hour response time and we would like to start cleaning up anything old. With that being said, just wanted to check in with you to see if you have made any progress or changes to your project since support has last reached out.
4 Views