Shaun, One advantage is consistency with speech recognition; if I have an interface where you can say "yes" or "no", or press 1 or two, I can simply instruct asterisk to load equivalent speech and DTMF grammars and the rest of my logic in dealing with matching, timeouts, etc is unified. Another in the case of only DTMF input is that I can use a well-defined logic framework, rather than implementing buffering and validation in an ad-hoc manner. As for implementation, Matt has put forward some background info on this and I will respond in more detail to his email, but this is not so much a change at all as an addition of a built-in recogniser for those who wish to use it. Ben On 12 December 2013 10:19, Shaun Ruffell <sruffell at digium.com> wrote: > On Wed, Dec 11, 2013 at 06:22:21PM -0500, Ben Langfeld wrote: > > The vast majority of IVR platforms (mainly VoiceXML) permit handling DTMF > > in a consistent manner to speech recognition, that is by way of a DTMF > > grammar. Asterisk, to my knowledge, does not currently include an > > SRGS-based DTMF recognizer. > > Hi Ben. I'm not that familiar with the use of speech recognition > engines with Asterisk. One question I had is what is the advantage > of specifying a grammar for DTMF? How would making this change look > in practice? > > Thanks, > Shaun > > -- > Shaun Ruffell > Digium, Inc. | Linux Kernel Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > Check us out at: www.digium.com & www.asterisk.org > > _______________________________________________ > asterisk-app-dev mailing list > asterisk-app-dev at lists.digium.com > http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20131212/04ed1006/attachment.html>
