assistant-waits-for-user
# support
j
When placing outbound calls, the assistant will generally fails to start speaking right after the first "Hello" from the user. The user can hear the set background noise (office) but until the user say a second Hello nothing happens. Would there be a timeout so the assistant starts speaking even if nothing is said? #1211483291191083018 @Shubham Bajaj
v
message has been deleted
@Jonas Yes, there is a parameter called
assistant.responseDelaySeconds
which defines the minimum number of seconds to wait after user speech before the assistant starts speaking. By default, this is set to 0.4 seconds. However, if the assistant is not starting to speak, it might be due to the
assistant.silenceTimeoutSeconds
which is the duration of silence the assistant waits for before ending the call, and this defaults to 30 seconds. If you're experiencing issues with the assistant not starting to speak after the initial "Hello," we might need to adjust the
assistant.responseDelaySeconds
to ensure the assistant starts speaking promptly. Would you like to modify this setting or is there another way I can assist you with this issue?
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
j
The responseDelay was already set to 0.1 and I do not believe the silence timeout setting has to do with this.
v
@Jonas I understand. It seems like the issue might be related to the detection of speech activity. The
machineDetectionSilenceTimeout
parameter could be relevant here. This parameter sets the number of milliseconds of silence after speech activity at which point the speech activity is considered complete. If this is set too high, the assistant might be waiting for additional speech that isn't coming, hence the delay. Would you like to adjust the
machineDetectionSilenceTimeout
to a lower value to see if that resolves the issue? The default is 1200 milliseconds, but you can set it anywhere between 500 to 5000 milliseconds according to your needs.
s
can you share call id.
because of no response closing this ticket.
5 Views