AT&T Module won't work

[Google Code Exporter]

I registered for an AT&T API account, created and App, and got an App Key and 
App Secret number. When I try to run OpenDial with the ATT module, following 
the guidelines in the wiki (ant run -Dmodules=opendial.plugins.ATTSpeech -Did=? 
-Dsecret=?)
the ATT module complains of having a "key" parameter missing, and when I run it 
with 
ant run -Dmodules=opendial.plugins.ATTSpeech -Dkey=? -Dsecret=? the module will 
complain of the pair key and secret even if they are correct.

Original issue reported on code.google.com by [e-mail] on 17 Feb 2015 at 7:56

[Google Code Exporter]

You're perfectly right, the online documentation contained a mistake, the 
parameters should be "key" and "secret" (and not "id" and "secret").  It's now 
corrected in the documentation. 

However, the module should work if you provide both the key and secret 
parameters. Are you sure that your application has activated the speech APIs on 
the AT&T portal? On the page with your application 
(https://matrix.bf.sl.attcompute.com/apps), you need to click on the edit 
button, and activate both "Speech - Speech to Text Custom" and "Speech - Text 
to Speech".

Original comment by plison2 on 17 Feb 2015 at 8:24

[Google Code Exporter]

They are both activated. I created two different apps, and the credentials from 
neither of them will work.

Original comment by [e-mail] on 17 Feb 2015 at 8:27

[Google Code Exporter]

This is the message OpenDial outputs when I start it:
 [java] [ATTSpeech] WARNING: Thrown exception: com.att.api.rest.RESTException: {"error":"invalid_scope"}
     [java] [DialogueSystem] WARNING: cannot attach ATTSpeech: opendial.arch.DialException: Cannot access AT&T API with the following credentials: ??? --> ???

Original comment by [e-mail] on 17 Feb 2015 at 8:37

[Google Code Exporter]

For some reason it won't work if I only activate those two options, but it will 
work if I check a third option "Speech - Speech To Text Custom". I guess the 
problem is on their side. Thanks very much for the help!

Original comment by [e-mail] on 17 Feb 2015 at 9:05

[Google Code Exporter]

Yes, the "Speech to text Custom" option must be activated as well. Note that in 
most cases, I would recommend using Nuance's speech API rather than AT&T's, 
which can be quite slow and have a lower recognition rate. 

Original comment by plison2 on 17 Feb 2015 at 9:18

• Changed state: Verified