If a call ended because of an error does the end-o...
# support
m
I'd like to provide this information for followup calls so the assistant knows that the last call ended because of dropped call or some other technical issue and apologize for the inconvenience
v
@MaxKnox Absolutely, I can help with that. To ensure the assistant is informed about the reason for the call ending, you can update the end-of-call report with the specific reason such as "dropped call" or "technical issue." This information can then be used to tailor the assistant's response in follow-up calls, including an apology for any inconvenience caused. Would you like to proceed with updating the end-of-call report with this information? If so, could you please provide the specific reason for the call ending that you'd like to be noted?
You can continue this conversation by mentioning me in the message.
m
Hmm after looking at my endpoint, I see that in the end-of-call-report there is a parameter: endedReason, would this normally indicate that there was an error or a pipeline error?
@Vapi After looking at my endpoint, I see that in the end-of-call-report there is a parameter: endedReason, would this normally indicate that there was an error or a pipeline error?
v
@MaxKnox Yes, the
endedReason
parameter in the end-of-call report is designed to indicate why the call ended. If the call ended due to an error, the
endedReason
would reflect that with one of the error-related options, such as
assistant-error
,
db-error
,
no-server-available
, or one of the
pipeline-error
options. If you have an
endedReason
that indicates a pipeline error, it would be one of the following: -
pipeline-error-extra-function-failed
-
pipeline-error-first-message-failed
-
pipeline-error-function-filler-failed
-
pipeline-error-function-failed
These indicate that there was an issue within the processing pipeline of the call, which could be due to various reasons such as a malfunctioning function or a problem with the message handling. Would you like to take any specific actions based on the
endedReason
you have observed?
m
@User are those all of the potential errors that would result in a dropped call?
s
Hey @MaxKnox , only call which are ended properly are sent via end-of-call-report server message. If you want to get error logs as well you will need to use status-update server message for it.
m
Hi @Sahil thanks for the reply. I've been getting dropped calls after say 15 min with pipeline error and I still do get the end-of-call-report... are you saying errors are only sent via the status-update? Which param?
s
Yes, you can get those event through status-update but can you send me the call_id so that we can take a look?