Silence Timeout on Custom Transcriber WebSocket

I’m currently building a custom transcriber using the Deepgram SDK, and we’ve been experiencing an issue where the WebSocket connection unexpectedly closes with the endedReason = silence timeout.

This has happened in multiple calls, including the following examples:
• Call ID: 6eb7d45e-7db2-4064-81a4-817671875b01
• Call ID: d046a7e7-9275-40d8-8216-a4b9adb87b77

We suspect that the issue might be related to the connection with Deepgram because the WebSocket is closing while the customer is still speaking. Since no more data reaches the transcriber after this point, the call ends with a silence timeout.

We would appreciate your help reviewing your logs to confirm whether this behavior is being triggered by Vapi or if it might be caused by the Deepgram connection.

Additionally, we would like to better understand how Vapi’s backoff plan works. Specifically:
• How does Vapi detect that the transcriber has been disconnected?
• What information or signals are required from our side to ensure proper reconnection behavior?

Thank you in advance for your support — any guidance or recommendations you can provide will be very helpful.

Best regards,
Vinicio from Aivora Solutions
Was this page helpful?