Calls failed: silence timeout, no transcript, no s...
# support
m
We have a few calls with issues today. Call ids: - e3f8cfae-e49f-44e6-b17b-1dae26b4f9c6 - bf20b3e2-8ab0-4cfa-ba4e-ce5beffe9ea6 - 8221ecf4-f1cc-4bfe-8e88-75c8b7d8f74a They all ended with
silence-timed-out
reason and now transcript, sumary available. Also another call that ended in `silence-timed-out`: d91a33b9-5ded-42ce-aa94-a57c8fd6ca32 This one has transcript. Is there a system outage going on?
v
message has been deleted
@marem I'm sorry to hear that you're experiencing issues with the calls. There is no current information about a system outage, but I can certainly help you investigate the issue further. For the calls that ended with
silence-timed-out
and have no transcript or summary available, it's possible that the callers did not speak or there was an issue with the audio input which led to the timeout. For the call with ID
d91a33b9-5ded-42ce-aa94-a57c8fd6ca32
that has a transcript but also ended with
silence-timed-out
, it could be that the caller stopped speaking, and after a period of silence, the call was ended as per the timeout settings. If you believe these incidents are not due to caller behavior and might indicate a technical problem, I recommend contacting support with the call IDs and your account email address so they can investigate the matter thoroughly. If you'd like, I can assist you in closing the support ticket once the issue is resolved. Would you like me to proceed with that?
You can continue this conversation by mentioning me in the message.
m
Issue seems to be with tts: talkscriber -> whisper. Is it down? I switched to deepgram now and agents work fine
Also I think it should be monitored somewhere. Status page has no details on it
s
i had a call with no summary as well. rest of the call was OK.
s
It happened because the LLM did not respond within 2500ms, resulting in the failure to generate a transcript. You can extend the time through the API.
"analysisPlan": { "summaryPrompt": "string", "summaryRequestTimeoutSeconds": 20, "structuredDataRequestTimeoutSeconds": 20, "successEvaluationPrompt": "string", "successEvaluationRubric": "NumericScale", "successEvaluationRequestTimeoutSeconds": 20, "structuredDataPrompt": "string", "structuredDataSchema": { "type": "string", "items": {}, "properties": {}, "description": "string", "required": [ "string" ] } } https://api.vapi.ai/api#/Assistants/AssistantController_create
m
is this the reason why I don't have call analysis as well? And why does the calls ends with a
silence-timed-out
?
Also these properties are not yet available in the vapi web api (1.4.0) @Sahil I think that default timeout should rather be upgraded on vapi side and have a better error management when such errors occurs https://cdn.discordapp.com/attachments/1250121450736713768/1250182332204449813/Screenshot_from_2024-06-11_22-17-27.png?ex=666a0287&is=6668b107&hm=7429dbfef450d95d1f575daae26521cc314020761cb1a2fa1355f2ccbd76f5b6&
s
I will update the web API
It didn’t detected your last message.
m
Thanks I submitted 2 type issues on the github repo, could be great to have a look if you have to update the web api: https://github.com/VapiAI/web/issues/41 https://github.com/VapiAI/web/issues/42
I created another one: https://github.com/VapiAI/web/issues/43 I wanted to upgdrade to "@vapi-ai/web": "^1.4.0", but I'll rollback my change and stay with "@vapi-ai/web": "^1.1.7", too many BC
s
I think nikhil already answered all the issues in github. So, do you still need help with anything?
m
yes please. I need you to release a new version of the web api that includes the missing parameters. (if not already done).
I mean the timeout params
s
Ah, sure.