Is this a frequent error- I mean previous to this call, my client spoke for over 5 mins, and then in the middle after 30 seconds silence timeout it ended call. in the voice recording i could not see any input from client after 5:24 time so it ended call stating the reason. However client is saying he spoke https://cdn.discordapp.com/attachments/1356159472434806784/1356159696624680970/image.png?ex=67eb8da3&is=67ea3c23&hm=da2f5eb91eb5a95a3d212dba02b35c89f541c2831b51a097ba1d5b7be31ec067&

Hi there! 👋 I can't verify what specifically happened with your client's call after the 5:24 mark, but I can definitely help explain the error and silence timeout behavior you're seeing. Regarding the frequency of the "call.in-progress.error-assistant-did-not-receive-customer-audio" error, this is actually reported by several users with varying frequency. According to information I found, some users experience it "on almost all calls" while others find it "not so common." There are reports of this issue affecting certain phone numbers significantly enough that some users had to "route ALL calls through human agents" as a result of this issue. The 30-second silence timeout functionality is a default setting in Vapi that ends a call after 30 seconds of detected silence. This timeout is configurable between 10-3600 seconds and provides a graceful fallback when users don't respond. The system uses this parameter to determine how long to wait for user input before ending the call. What likely happened in your case is that the assistant didn't detect any audio from the customer after the 5:24 mark, triggering the silence timeout after 30 seconds. This could be due to several possible causes: 1. Audio quality issues - weak recordings or background noise can affect transcription 2. Transcription inaccuracies - the system might not have properly transcribed what was said 3. Endpointing issues - the system might have incorrectly determined when the user finished speaking 4. Network problems - there could have been issues with the audio stream 5. Microphone permission issues - though less likely in this case since audio was working earlier When analyzing voice recordings for this issue, it's helpful to check for audio quality problems, compare the live audio to recorded audio, and investigate silence detection behavior. The system might not have registered the client's speech if it was too quiet or if there were issues with the audio processing.

the client message in the recording was also cut down while he was talking. And post that, it was ended. Can share teh recording in private dm for the same.

+1

Hey Ress and Snow, this issue is on us, and it's related to SIP. We are aware of it. The team is working on it, and as soon as it is resolved, you will get to know about it through status pages and through Discord.