Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Hotword detection #9

Open
lpradovera opened this issue Nov 5, 2011 · 5 comments
Open

Hotword detection #9

lpradovera opened this issue Nov 5, 2011 · 5 comments

Comments

@lpradovera
Copy link

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!

@loopingrage
Copy link
Member

I don't understand the issue. Can you provide an example please?

@benlangfeld
Copy link
Member

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 <nomatch/>. We don't want the input to terminate, and instead continue to run until it receives valid input, times out, or is stopped.

@lpradovera
Copy link
Author

To further clarify, this is the GRXML grammar example I am using: https://gist.github.com/659518c6f941c9a6e47c
I would need Input to be able to ignore DTMF input that is not in the one-of.
Thanks!

@loopingrage
Copy link
Member

Gotcha. That behavior is often referred to as 'hotword' recognition. I'll look into getting it added next week.

@wchen
Copy link

wchen commented Nov 7, 2011

revisit this (hotword detection) issue when we visit signal detection work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants