https://vapi.ai/ logo
Join Discord
Powered by
Call Transfers not Transferring
# support
m
Hello, when the call is supposed to do a call transfer, the transfer does not complete. It just does a few dial tones, but then no transfer. https://cdn.discordapp.com/attachments/1367197415169589258/1367197415685361789/Screenshot_215.png?ex=6813b551&is=681263d1&hm=dd9b5a05a0697e16a3775c07a07fab6d16aa00ac2502d683b9908cb4b65a0d65&
v
The issue may be related to SIP REFER handling between Vapi and Twilio. According to [Discord discussions](https://discord.com/channels/1211482211119796234/1337383511329345588), this is a common problem with SIP transfers. Try using a Twilio phone number instead of a SIP URI for the transfer destination:
Copy code
json
{
  "type": "transferCall",
  "destinations": [{
    "type": "number",
    "number": "+1XXXXXXXXXX",  // Replace with Twilio phone number
    "transferPlan": {
      "mode": "warm-transfer-wait-for-operator-to-speak-first-and-then-say-message",
      "message": "Customer call being transferred from Vapi."
    }
  }]
}
Sources: - [Discord discussion on call transfers](https://discord.com/channels/1211482211119796234/1337383511329345588) - [Discord discussion on SIP URI issues](https://discord.com/channels/1211482211119796234/1338285744090906756)
m
it does the same thing even when we use a number
u
Hi @MadHatMedia , Could you share your vapi call log and twilio log?
m
sure, here are the 2 vapi call logs
851270e7-49fb-41d3-a4e8-681c46c81ef1
d80263e2-a7d8-401a-8590-7a5400931d99
I am not sure how to share the twilio log with you
u
Just screen shot your twilio call logs.
m
c
Hey Madhat Media, for the above calls could you share the following information:- - 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!
m
We expected the call to be transfered. The call was not trasnfered. We heard what sounded like buttons being presssed by the AI then there was silence for about 10 seconds. then the AI asked if we are still on the line.
c
we are in the process of updating how we handle SIP transfers. we expect an update that addresses this issue within the next day or two. please test it over the weekend and let us know if it works
Hey MadHatMedia, for the shared call IDs starting with D802, the DTMF tool surpassed the transfer tool call, causing the unexpected behavior you described. To resolve this, rework your prompt and change your model from Open AI Models such as GPT 4.0. This should improve your call functionality and results. Let me know your thoughts. 
Copy code
{
  "role": "tool_calls",
  "time": 1746034129476,
  "message": "",
  "toolCalls": [
    {
      "id": "call_dpve",
      "type": "function",
      "function": {
        "name": "dtmf",
        "arguments": "{\"keys\": \"3301\"}"
      }
    },
    {
      "id": "call_adeg",
      "type": "function",
      "function": {
        "name": "transferCall",
        "arguments": "{\"destination\": \"+14804489173\"}"
      }
    }
  ],
  "secondsFromStart": 5.406
}
2 Views
PreviousNext
Powered by