blank-aquamarine•4h ago
Critical: Struggling with a transferCall error
Ended Reason: call.in-progress.error-transfer-failed
Status: queued
I'm using a dynamic transient setup which previously has worked fine like this. This is the function setup:
{
"type": "transferCall",
"destinations": [
{
"type": "number",
"number": "{{19.
20}}",
"callerId": "{{decodeURL("%7B%7Bcustomer.number%7D%7D")}}",
"message": "One moment. Please stay on the line."
}
]
}
The assistant is saying the message, but then the call never rings like it used to and so the forwarding never actually gets pushed through.
I'm looking through the vapi logs and not really finding anything.
Tried removing the callerId and message and hard coding the phone number in and it still didn't work. The phone number that the calls are forwarding to are fully functional - have continued to test and verify.
Have also tested in other organizations and getting the same issue.
OrgId:
- 2955326d-c7db-412f-aeed-c89b1cc1ef21
Call IDs:
- 019a2b8f-50a1-7dd6-8a87-6f599d85c3c9
- 019a2b7f-6bce-7ffa-8a8b-6763bea20add
- 019a2b75-6f04-7cc4-89bc-5302439c31d8
- 019a2b70-d2d0-7bbc-971f-80acc7a2dc6a
- 019a2b64-590a-733d-abd6-efb3cb6d28ab
- 019a2894-2f6e-7889-9975-b85185b6595f4 Replies
Thanks for sharing the details. To help narrow down the cause of the transferCall error, could you confirm if your assistant's configuration has
serverMessages set to include "phone-call-control" or if phoneCallProviderBypassEnabled is set to true? These settings can prevent Vapi from managing transfers and are a common source of this issue (see troubleshooting guide).
If you're unsure, you can check your assistant's JSON config for these fields. Let me know what you find!
Source:
- Debug call forwarding drops⤵️ Mention @Vapi Support Bot for follow-ups 🐥
blank-aquamarineOP•4h ago
is this a new feature requirement because it worked fine prior @Duckie
If your transferCall setup worked previously but now fails, check if your assistant's configuration has
Review your assistant's JSON config and ensure: If either setting is incorrect, update it and test your transfer again. Source: - Debug call forwarding drops
serverMessages set to include "phone-call-control" or if phoneCallProviderBypassEnabled is set to true. These settings can prevent Vapi from managing transfers and are a common source of this error. This requirement is documented in the Vapi troubleshooting guide.
Action:Review your assistant's JSON config and ensure: If either setting is incorrect, update it and test your transfer again. Source: - Debug call forwarding drops
blank-aquamarineOP•3h ago
@Tim
@Vapi