Inconsistent Server Messages
# support
p
I am not getting status-update and end-of-call-report on my specified url, for some of the calls, causing a lot of issues, in my system. Call_id, for such an example: 0199c8db-9ddb-7554-ac44-2fd98acf7740 Another call_id, with the same issue: 0199b314-06d6-7eeb-a4ef-d2401f2a7330 Now, i undestans that these calls were not picked, up, hence status_update might not be sent, but atleast end-of-call-report needs to be sent, so that we can complete the loop on our end, and mark the call accordingly.
v
Suggestion: This is a known intermittent issue with Vapi, often related to SIP misconfigurations, network instability, or platform issues. As a first step, please review any recent changes to your SIP trunk or webhook configurations, as these can impact webhook delivery. If you haven't changed anything recently, consider reaching out to Vapi support with your call_id for further investigation. Tip: Double-check your webhook URL and ensure it is reachable and correctly configured in your Vapi dashboard. (Reference: information found in Vapi support discussions) Source: - [Vapi outbound call not triggering (Discord)](https://discord.com/channels/1211482211119796234/1341449578100031488)
p
@Vapi @Shubham Bajaj @Sahil @User can you please help raise this issue with the team. It was working correectly, some time back, and, now it is not.
Hi @Vapi Support Bot @VAPI Tech @Vapi, Any response on this ??
THe issue is still presisting
c
Hi ParwaanVirk (BotMast), To enable server messages, ensure that your
serverMessages
property is set correctly when creating or updating an assistant. You must define which types of messages your assistant should send to the server. The
serverMessages
array can include types like
conversation-update
,
end-of-call-report
,
function-call
,
hang
,
speech-update
,
status-update
,
tool-calls
,
transfer-destination-request
, and
user-interrupted
(see [docs](https://docs.vapi.ai/changelog/2025/5/1)). If you encounter any issues, verify that the message types you set in the
serverMessages
array match the schema and include all required fields. Additionally, look into the most recent updates or changes in the server messaging API that could impact your settings.
3 Views