Posted: Thu Feb 22, 2007 5:35 pm Post subject: [asterisk-speech-rec] DTMF CRM:00170687
David,
The purpose of DTMF grammars is so that once the platform (in this case Asterisk) recognizes DTMF, you can get semantic interpretation from the Engine regardless of whether the user spoke or dialed. I.e. you can return the same semantic interpretation to your application regardless of whether your user said "One" or pressed 1. It sounds like this is what you would want for your application -- this way all semantic interpretation is handled in grammars and not by your application.
I am not sure how to pass recognized DTMF from Asterisk to the Engine for semantic interpretation. Perhaps Josh or somebody else on the list is more familiar with this?
Stephen Keller
LumenVox Technical Support
P: 877-977-0707, just say "Stephen Keller" or "Support"
F: 858-707-7072
support@LumenVox.com www.LumenVox.com
From:asterisk-speech-rec-bounces@lists.digium.com [mailto:asterisk-speech-rec-bounces@lists.digium.com] On Behalf Of David Brazier
Sent: Thursday, February 22, 2007 8:23 AM
To: Use of speech recognition in Asterisk
Subject: RE: [asterisk-speech-rec] DTMF
Joshua Colp wrote:
> Using the newest version of the speech API once a DTMF digit is received
Quote:
then Asterisk will stop doing speech recognition and switch strictly to
DTMF in itself. Once this happens the SRE is no longer involved as it is
not the one who detects or handles the DTMF. If everything is properly
setup then DTMF tones should never reach the SRE. In the case where
you've got DTMF going inband and you're not setup to process it inband,
then it would spill over to the engine but that's the only case I can
think of.
Thanks for the explanation. So this means there is no point loading a DTMF grammar in the SRE?
I'm actually driving this via AGI. For my current DTMF-based IVR, I use "STREAM FILE" and "WAIT FOR DIGIT", which both allow me to get the digits(s) pressed. For the ASR version, I'm using "EXEC" to call SpeechBackground, but I don't think that would return the digit as a result. As the application logic is quite complex, I don't want to handle DTMF in the dialplan in the traditional Asterisk IVR manner, so it looks as though I'll have to abandon trying to allow both speech and DTMF at the user's choice, and the application will have to be in one mode or the other.
You can post new topics in this forum You can reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum