We're seeing an increased number of silence-timed-...
# support
c
Call IDs: 6830fb38-a846-4b88-b24f-75b52874c0ac f992dad9-faea-4a20-98c8-bb290f32a740 06d14213-6405-4677-bbb8-c5a55ac63449 ca42029b-d92a-4f32-adbf-a0f2cb003f82 cb340dfb-93d5-4fca-b188-6ed93aeab51c 241dc232-d15c-4ff5-915e-032ee8fc4a0f 0a9b3709-a82c-42c5-8b77-421f345b9a9c
d
please @Chris push the button! ⁠#1293690685781839933. We are facing the same issue
c
done
I just can't tell if its the STT, LLM or TTS
c
Hey Chris, I wanted to let you know that we're managing a high volume of support requests at the moment, so our response time might be a bit slower than usual. I truly appreciate your understanding and will get back to you as soon as possible!  Thanks again for your patience!
c
Thanks @Shubham Bajaj for your support! I have two distinct Call IDs from the same phone. And one call worked great the other the transcriber didn't most of the callers conversation. Good: bf025689-4643-4e92-bdf5-d9df8520b2e7 Bad: b27ade9c-cf4e-443b-8a53-d36b4c0aaf17 Should we try with different transcribers?
c
set
silenceTimeoutSeconds
to 15,
idleTimeoutSeconds
to 5, ensure the assistant speaks first, and consider switching to a more stable STT like Azure..