silence timeout hit when it was not supposed to
# support
o
can you guys tell me why the call with this id bded5d35-ce07-4967-a68c-1f3c9f6c971b ended with silence timeout ? the silence timeout is set to 30 seconds plus the call ended when the Assistant was speaking
v
message has been deleted
@orange It seems there might have been an issue with the call handling process. The call should not have ended due to a silence timeout while the Assistant was actively speaking, as the silence timeout is intended to trigger only after a period of inactivity from the user's side. To investigate this further, I would need to check the call logs and system behavior for the specific call ID you've provided. However, since I don't have direct access to the call logs or system data, I recommend reaching out to support with the call ID and the details of the issue. They will be able to provide a more detailed explanation and help resolve any potential problems with the call handling logic. If you need assistance with anything else or have more questions, feel free to ask!
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
o
this is the call id bded5d35-ce07-4967-a68c-1f3c9f6c971b
s
@orange can you try now, and let me know how it goes.
o
Why did it happen though
That was the only time it happened
s
it happened because of race conditions.
o
Okay, that's the only time it happened