Transfer call error: call.in-progress.error-vapifa...
# support
m
We notice that on our Call logs some of the calls has this error. Can you explain why this keeps happening? Also check some SS attached. Here are the error call logs ID: 0199e5e3-ec91-7dda-84d0-0003e987e863 0199e5e3-4dbd-7eec-85dc-fef14f280f02 0199e5e2-c661-733f-b000-cfafc9075175 0199e1d4-8679-788e-849d-e132ab142bb4 0199e1d2-4118-7663-b8c4-594f9ac87d74 0199e1d1-f4aa-700c-bc93-5c3a175c2506 0199e1d0-5d2a-7883-9686-bc9e5746d42c 0199e1d0-4fdd-7883-9686-ac3a80663d71 0199e1ce-90cb-7663-b8c1-4102551af2ca 0199e1cd-3a84-7773-84cb-cae39335d467 0199e1cc-09f2-7883-967e-e5a5770e446a 0199e1ca-fb99-7221-b16a-4f19a056fab9 0199e1ca-96a6-7ee9-9b95-ec884f0a0159 https://cdn.discordapp.com/attachments/1427885001235497051/1427885001567113307/image.png?ex=68f07d09&is=68ef2b89&hm=6ac4ef525b2d65d6acb3c1b63071889ff36b706504ea56e5306477abc2b0c82d& https://cdn.discordapp.com/attachments/1427885001235497051/1427885002183544955/image.png?ex=68f07d09&is=68ef2b89&hm=d97ddde31726efa0c72489d285cd53337386eb2f843e5ce831a862b93d4963eb&
v
Suggestion: The
call.in-progress.error-vapifault-worker-died
error indicates a failure in the Vapi processing pipeline, often due to configuration issues or unexpected inputs. As a first step, review your assistant and workflow settings in the Vapi dashboard to ensure all required fields are correctly filled and no misconfigurations exist. Tip: Pay special attention to model selection, prompt fields, and tool configurations, as missing or invalid values can cause immediate call failures. If the issue persists after verifying your configuration, consider reaching out to Vapi support with your call IDs for deeper investigation. Sources: - [Call ended reasons (Vapi documentation)](https://docs.vapi.ai/calls/call-ended-reason) - [Debugging voice agents (Vapi documentation)](https://docs.vapi.ai/debugging)
m
@Shubham Bajaj Eyy Boss, can you help me on this?
s
it is an temp issue from our end which is fixed.
r
"Could you please run these two telnet tests from your side and let me know the results? I'm getting the exact same behavior." telnet 44.238.177.138 5060 (Should CONNECT ✅) telnet 44.229.228.186 5060 (Should FAIL or TIMEOUT ❌) "I need to confirm if the second IP is unreachable for you too, which would indicate a routing issue outside of my local network."
c
Both the ip address are correct but you will usually get a request from the first IP.
2 Views