Server Events - Status Updates - Missing Events
# support
a
I am trying to determine when a call has been sent directly to voicemail. I found events "queued", "ringing" and "in-progress" in the Status Updates Server Events https://docs.vapi.ai/server-url/events#status-updates (also se pic). However, on testing, queued and ringing status's are not received, therefore I am not able to measure this KPI. How can this be resolved please? @Shubham Bajaj @AJH https://cdn.discordapp.com/attachments/1415229656600154124/1415229656990482432/image.png?ex=68c272d3&is=68c12153&hm=8b529544b0362722bd45bff72fd672004014c42b5a113631172f8078f8e6ce29&
v
Suggestion: Since missing "queued" and "ringing" events is a known intermittent issue in Vapi (often related to SIP or webhook configuration), the recommended first step is to review any recent changes to your SIP trunk or webhook settings. If you haven't changed anything, try reverting to a previous working configuration or reach out to Vapi support with your callId for further investigation. Example troubleshooting step:
Copy code
text
1. Double-check your SIP trunk and webhook configurations for recent changes.
2. If unchanged, contact Vapi support and provide a callId for deeper analysis.
According to the documentation, there is currently no definitive fix, but support may be able to assist further ([Discord reference](https://discord.com/channels/1211482211119796234/1372358449761091584)). Source: - [Vapi outbound call not triggering (Discord)](https://discord.com/channels/1211482211119796234/1372358449761091584)
c
The problem is that status updates are only sent to your server URL when the call ends, not during the "queued" or "ringing" phases. If you want to get current updates, you could set a cron job to poll the /call endpoint with GET for the call id
a
Thanks Kyle
c
No worries. We’ve closed this ticket, but your input is very valuable to us. Please take a moment to complete the survey, which should appear in a couple of days—your feedback directly helps us improve our support.
2 Views