-
Notifications
You must be signed in to change notification settings - Fork 4
Hotword detection #9
Comments
I don't understand the issue. Can you provide an example please? |
In order to implement output interruption, it is necessary to run an input in parallel with an output. We run the input with a grammar which restricts DTMF. If invalid DTMF is received, the input terminates with |
To further clarify, this is the GRXML grammar example I am using: https://gist.github.com/659518c6f941c9a6e47c |
Gotcha. That behavior is often referred to as 'hotword' recognition. I'll look into getting it added next week. |
revisit this (hotword detection) issue when we visit signal detection work. |
Hello,
as of now, an Input component getting passed a one-of grammar with only some allowed digits stops execution anyway, returning a NoMatch event.
While in some situations this is needed, in some others it would be convenient to not return and just ignore not matching characters from a grammar.
Maybe this could be implemented as an option to Input to keep both functionalities.
Asterisk behaves that way with the STREAM FILE dialplan function.
Thanks!
The text was updated successfully, but these errors were encountered: