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

DTMF events #28

Open
benlangfeld opened this issue Apr 25, 2012 · 3 comments
Open

DTMF events #28

benlangfeld opened this issue Apr 25, 2012 · 3 comments
Milestone

Comments

@benlangfeld
Copy link
Member

The events should come from an input component (as with other signal detectors). Should one be started at the top of the call?

@benlangfeld
Copy link
Member Author

Solution: Input component w/ hotword detection (SRGS GARBAGE?) and repeat-on-match (send a match event and reset the buffer), started prior to answering incoming calls.

This means we need to specify repeat-on-match.

@crienzo
Copy link

crienzo commented Mar 28, 2013

Would this be a new kind of intermediate event where the input component continues to execute?

@benlangfeld
Copy link
Member Author

Yes it would, but there's still no consensus on wether it should be grammar
based or something else. This needs work.

Regards,
Ben Langfeld

Em 27 Mar 2013, às 23:00, Chris Rienzo [email protected] escreveu:

Would this be a new kind of intermediate event where the input component
continues to execute?


Reply to this email directly or view it on
GitHubhttps://github.com//issues/28#issuecomment-15564318
.

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

2 participants