API endpoints appear to be incorrect - not working about asterisk-speech-recog HOT 5 CLOSED

Hello,

yes the script is still using the old Speech API 'https://www.google.com/speech-api/v2/recognize'
The end points are not incorrect as pointed out, the API is still functional so is the speech recognition script. I am aware of the new Speech API from Google and as soon as I find some free time there will probably be an update or a new version that will utilize the 'Cloud speech API'.

from asterisk-speech-recog.

Oh, OK. I just can't find how to generate an API key for the old endpoints, so they were rejecting it.

Sit back and take a break for a few hours - I've now got a fully functioning python implementation that uses the new Cloud Speech API.
I'm doing a bit of code cleanup and a quick tutorial, but I'm not a python programmer so if I post it here, I'd greatly appreciate your help in cleaning it up. :)

from asterisk-speech-recog.

The process to get a key for this API is completely obscured by Google. Among other things to get the Speech API option on your API console you have to join the Chromium dev list group https://groups.google.com/a/chromium.org/forum/#!forum/chromium-dev

It was covered in detail in previous discussions, please see issue #9 and issue #10

from asterisk-speech-recog.

Oh no! I have just discovered the pull request from @invitecomm in your repo!
It is almost exactly the same conclusion I came to at 2am this morning - for anyone else struggling, please see this fork https://github.com/invitecomm/asterisk-speech-recog/tree/master/v1beta1

from asterisk-speech-recog.

A new branch (cloud_api) with support for the Cloud Speech API has been added. All AGI and CLI scripts are converted to use the Cloud API.

from asterisk-speech-recog.