### Answer It sounds like the calls you mentioned were ended due to a "silence-timed-out" error. This usually happens when the system mistakenly detects prolonged silence, even if the speaker believes they were talking. This can be influenced by several factors such as background noise, poor microphone quality, or issues with the speech-to-text service not picking up the audio correctly [(1)]() . To investigate these specific instances and understand why the system ended the calls, it's recommended to look into the call logs or use the metadata associated with those call IDs. You can retrieve detailed information about each call by using the

Get Call

API endpoint. Here's how you can make a GET request to retrieve details about a specific call:

curl
curl --request GET \
  --url https://api.vapi.ai/call/{id} \
  --header 'Authorization: Bearer <token>'

Replace

{id}

with the call ID and

<token>

with your authorization token [(2)]() . If this issue persists, adjusting the

silenceTimeoutSeconds

setting in your call configurations might help to mitigate erroneous terminations due to supposed silence. Additionally, ensuring the audio quality and checking for any network issues could also be beneficial. For further detailed analysis, you might need to access the audio recordings if they are enabled and review them to verify the presence of audio during the supposed silence periods [(1)]() .

Got it. Tagging @User for additional help.