https://vapi.ai/ logo
Join Discord
Powered by
Call forwarding not working on inbound calls
# support
e
Call forwarding isn't working on inbound calls. I've checked the logs and they say the call has been transferred successfully.
Copy code
{
  "name": "transferCall",
  "role": "tool_call_result",
  "time": 1740577000249,
  "result": "Success.",
  "toolCallId": "call_54tlWPNr54t5AIKoC7EC0J5p",
  "secondsFromStart": 61.191
}
This is through the default call forwarding function. Assistant says she's forwarding the call, then there's silence and the call suddenly ends. It's working as expected with outbound calls. Are there any specific twilio requirements/settings? 0a434527-f2b4-40ab-9ba9-e21b41ed9e88
Copy code
"toolCalls": [
                        {
                            "id": "call_54tlWPNr54t5AIKoC7EC0J5p",
                            "type": "function",
                            "function": {
                                "name": "transferCall",
                                "arguments": "{\"destination\": \"+49157--------\"}"
                            }
                        }
                    ]
k
Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!
e
Hey, the call id was 0a434527-f2b4-40ab-9ba9-e21b41ed9e88
@User
k
🟡 13:38:25:302 Couldn't Transfer Twilio Call. Error: The requested resource /2010-04-01/Accounts/ACca71ca5d89bdb8e7eefb25057d2b4da6/Calls/CA8587d3f76b6de06890db580a95054617.json was not found 🔵 13:38:25:146 Transferring Twilio Call...TwiML:<Response><Dial><Number>+49xxxx070</Number></Dial></Response> @Enes the call was transfered to the request destination but your twilio account has some limitations or something else because of it twilio didn't transfered your call. @Enes can you check in your twilio logs why the call was not forwarded. Twilio Call SID: CA8587d3f76b6de06890db580a95054617
e
This is what i found on Twilio for another call: @User
Copy code
PROPERTIES

Who Hung Up
-
Post-Dial Delay
0.48 seconds
Last SIP Response
487 Request Terminated
Call State
noanswer
Twilio RTP Latency (ms)


-
METRICS (Carrier Edge)

Codec
-
Packet Loss Detected
false
Jitter Detected
false
High Post-Dial Delay
false
Edge Location (Region)
Frankfurt (de1)
https://cdn.discordapp.com/attachments/1344306983263670303/1346074413573079052/Untitled.jpg?ex=67c6dcfd&is=67c58b7d&hm=7ee33301f49facf5a577ce743c25e456ea3d52ce6a8d6cb3fd61a75ea65636db&
I contacted Twilio Support regarding this, too and they said this:
Copy code
From what I saw it appears that the call cancellation came from the origin, as you can see in the print below:
 
Outbound-dial
Twilio ID: CAbd941e52d8b421830baaf057290a1377
Direction: Twilio to Carrier
Status: no-answer
Start Time: 2025-02-26 13:53:01 UTC
Date Created: 2025-02-26 13:53:01 UTC
Duration: 0 seconds
From: +4973XXXXXXXXX
To: +491578XXXXXXXXX
They have now activated Voice Trace and will continue to investigate this. @User https://cdn.discordapp.com/attachments/1344306983263670303/1346511306240426065/fChFfVXZ3bKvy00Lj0IQhRAI5.png?ex=67c873e0&is=67c72260&hm=94a841621efe118438047eac406f83ee52059a667e8185e97b04798a004e5769&
k
@Enes so your saying that Twilio took a closer look at the outbound leg of the forwarded call (CAbd941e52d8b421830baaf057290a1377), and they sees the call going out , but it’s reported as “no-answer” and ended with zero duration. what we do today doing the typical “REFER and release” approach, which hands off the call to the telephony carrier to handle the forward. If the far end isn’t answering or Twilio is seeing a “no-answer” result, there’s not much else you can do from our side by default.
Now let me know, how can I help you next?
PreviousNext
Powered by