Chirag Arora

Results 3 comments of Chirag Arora

I'm facing a similar issue, 2025-10-28T16:10:12.043+0000 - DEBUG - CA16237d8e8e54774d5e2f6fa9337e5933 - > TranscriptLogger: UserStoppedSpeakingFrame#55 2025-10-28T16:10:12.048+0000 - DEBUG - CA16237d8e8e54774d5e2f6fa9337e5933 - > TranscriptLogger: LLMFullResponseStartFrame#16 2025-10-28T16:10:13.241+0000 - DEBUG - CA16237d8e8e54774d5e2f6fa9337e5933 - OpenAILLMService#1...

> It sounds like there may have been an interruption cause by background noise. This is a common issue and requires a noise cancellation solution to filter out background noises...

these are the logs after that, you can see no interruption when bot stopped speaking, and you can see the timestamps as well, 20 secs after that an interruption frame...