OND Posted October 23, 2020 Author Report Share Posted October 23, 2020 I ran curl https:speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY and it responded with curl: (3) Illegal port number I'm assuming that's probably not what I want to see? Link to comment Share on other sites More sharing options...
Support Posted October 23, 2020 Report Share Posted October 23, 2020 That's right. You will have to look further into that. Try : wget https:speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY Link to comment Share on other sites More sharing options...
OND Posted October 23, 2020 Author Report Share Posted October 23, 2020 I ran that command, here's what it replied: --2020-10-23 15:33:52-- ftp://https/speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY => ‘.listing’ Resolving https (https)... failed: Name or service not known. wget: unable to resolve host address ‘https’ Link to comment Share on other sites More sharing options...
Support Posted October 23, 2020 Report Share Posted October 23, 2020 It's not supposed to ftp on http Try it without https then because it's FTP'ing for some reason Link to comment Share on other sites More sharing options...
OND Posted October 23, 2020 Author Report Share Posted October 23, 2020 I ran it again without the https like this: wget speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY and it replied with this: --2020-10-23 15:39:11-- http://speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXYResolving speech.googleapis.com (speech.googleapis.com)... 172.217.5.74, 172.217.11.74, 142.250.68.106, ...Connecting to speech.googleapis.com (speech.googleapis.com)|172.217.5.74|:80... connected.HTTP request sent, awaiting response... 404 Not Found2020-10-23 15:39:11 ERROR 404: Not Found. Link to comment Share on other sites More sharing options...
OND Posted October 26, 2020 Author Report Share Posted October 26, 2020 Is the reply that I got from the server what I should have gotten, or is this not right? Link to comment Share on other sites More sharing options...
Support Posted October 26, 2020 Report Share Posted October 26, 2020 Was your system not able to find the URL or the google's server wasn't? Link to comment Share on other sites More sharing options...
OND Posted October 26, 2020 Author Report Share Posted October 26, 2020 I SSH'ed into my server, which is in Google's cloud when I ran this command Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 26, 2020 Report Share Posted October 26, 2020 It is wget https://speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY Link to comment Share on other sites More sharing options...
netbit Systems Posted December 28, 2020 Report Share Posted December 28, 2020 I'm having this same issue hoping to add some input as well as help in getting a resolution. My System Centos Vodia 66.0.6 Hosted on Google Cloud Platform What I tried: The Cloud-speech-to-Text is enabled I'm not restricting the API key till I get it working. I do however have it restricted to the Speech service. See below. Reloaded Certificates Made sure the API was enabled properly on Vodia system. Below is a log on the matter Link to comment Share on other sites More sharing options...
OND Posted December 28, 2020 Author Report Share Posted December 28, 2020 And I was still never able to get it working. I kinda kicked to the back burner because I wasn’t getting anywhere, but I’d definitely like to get it working for my customers Link to comment Share on other sites More sharing options...
netbit Systems Posted December 28, 2020 Report Share Posted December 28, 2020 19 minutes ago, OND said: And I was still never able to get it working. I kinda kicked to the back burner because I wasn’t getting anywhere, but I’d definitely like to get it working for my customers Where is your system being hosted? I spoke to another guy that has it and he does not have this issue. Link to comment Share on other sites More sharing options...
OND Posted December 28, 2020 Author Report Share Posted December 28, 2020 My system is hosted in Google’s Cloud Link to comment Share on other sites More sharing options...
netbit Systems Posted December 28, 2020 Report Share Posted December 28, 2020 2 minutes ago, OND said: My system is hosted in Google’s Cloud Alright we have that in common. Based on everything it seems to be relevant to Google Cloud. As I said the other guy does not have the issue and neither does Vodia that I'm aware of. Link to comment Share on other sites More sharing options...
Support Posted December 29, 2020 Report Share Posted December 29, 2020 If possible can you please take a snapshot of the PBX and upgrade to the latest version 66.0.7 which maybe have fixed an issue with Google's API. Here's the update http://portal.vodia.com/downloads/pbx/version-66.0.7.xml Link to comment Share on other sites More sharing options...
netbit Systems Posted December 30, 2020 Report Share Posted December 30, 2020 On 12/28/2020 at 4:52 PM, OND said: My system is hosted in Google’s Cloud What OS do you have it installed on? I was able to get to work on a system that was not hosted on Google platform. So the API is setup correctly. It's now between the OS on the instance or something goofy with Google platform. Link to comment Share on other sites More sharing options...
OND Posted December 30, 2020 Author Report Share Posted December 30, 2020 1 hour ago, netbit Systems said: What OS do you have it installed on? I was able to get to work on a system that was not hosted on Google platform. So the API is setup correctly. It's now between the OS on the instance or something goofy with Google platform. I've got mine running on Debian64 on Google's cloud. I recently installed the a Single Tenant Vodia PBX on a customer's Windows PC at their request, I'm thinking I might try getting the transcriptions working on that to see if we can further narrow down the issue to the OS. Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 30, 2020 Report Share Posted December 30, 2020 There is also a 66.0.7 available for Win64 — though this is not a release this might also help narrowing it down. Link to comment Share on other sites More sharing options...
netbit Systems Posted December 31, 2020 Report Share Posted December 31, 2020 Sounds good. Mine is a Centos8 (64) instance (I have two instances). The common thread aside from Google Platform is the Linux base. I will also note the system I tried on-prem was also Windows based running 66.0. I believe support is out on that license so I could not try 66.0.7 on it. However I loaded 66.0.7 on the Centos machines with no success. I also reverted to 66.0 per another suggestion but it had the same result. Lastly, I tried to contact Google Platform. It's not very good news. You have to pay extra to receive any kind of support (phone or chat) unless an error was thrown from Google Platform itself. The model is largely for developers and they are the ones to troubleshoot any problems. Based on the information I have gathered the OS is the next best thing to troubleshoot. Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 2, 2021 Report Share Posted January 2, 2021 I would really just pay attention to the web client log level 9 on the PBX, maybe also log level 9 for the TLS messages. Then it should become clear where the problem is. E.g. it took us also some time to figure out what needed to be enabled in the Google console to make this API work — it was helpful to see how many requests actually were received for the API Key. Link to comment Share on other sites More sharing options...
fred.bloggs Posted January 21, 2021 Report Share Posted January 21, 2021 Hi, we have the same issue. Complete new installation on Ubuntu Server 20.04. We are comming form version 66.0.6 and I also tried with version 66.0.7. Same error: Quote Certificate for speech.googleapis.com could not be verified On google cloud console we only see a cryptic "compute" error when the vodia tries to access the API. With level 9 we get this log: [7] 21:05:50.673 https:speech.googleapis.com:443: DNS A returned 216.58.210.10ⓘ [7] 21:05:50.673 https:speech.googleapis.com:443: Connect to 216.58.210.10ⓘ [9] 21:05:50.677 https:speech.googleapis.com:443: Send request (158710 bytes)ⓘ POST https://speech.googleapis.com/v1/speech:recognize?key=xxxxxxxxxxxx HTTP/1.1 Host: speech.googleapis.com Content-Type: application/json; charset=utf-8" Content-Length: 158527 {"config":{"encoding":"LINEAR16","sampleRateHertz":8000,"languageCode":"de-DE","maxAlternatives":1,"profanityFilter":true,"model":"phone_call","enableAutomaticPunctuation":true,"enableWordTimeOffsets":false},"audio":{"content":"xxxxxx} [9] 21:05:50.677 Initialize TLS connectionⓘ [9] 21:05:50.677 HTTP 216.58.210.10: Send Client Hello(03036009..00020017)ⓘ [9] 21:05:50.690 HTTP 216.58.210.10: Receive Server Hello(03036009..00020100)ⓘ [9] 21:05:50.690 HTTP 216.58.210.10: Receive Certificate(000B7500..9D9CF5CA)ⓘ [9] 21:05:50.690 HTTP 216.58.210.10: Received chain with 2 certificatesⓘ [4] 21:05:50.690 Unknown DSA hash algorithm 2A864886F70D01010Bⓘ [5] 21:05:50.690 HTTP 216.58.210.10: Certificate for speech.googleapis.com could not be verifiedⓘ [9] 21:05:50.690 HTTP 216.58.210.10: Send Alert(022e)ⓘ [7] 21:05:50.694 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 21:05:50.694 https:speech.googleapis.com:443: Return code 500ⓘ [8] 21:05:50.694 https:speech.googleapis.com:443: Return content (0 bytes)ⓘ [7] 21:05:50.694 Transscript for 7s failed with code 500ⓘ [7] 21:05:50.696 Closing connection https:speech.googleapis.com:443ⓘ From the console (CURL) we can communicate with the API without an issue. Looks like google implemented ECC certificates and Vodia can't handle the new encyption algorithms of curves. Link to comment Share on other sites More sharing options...
OND Posted January 21, 2021 Author Report Share Posted January 21, 2021 Sorry I hadn't had a chance to post an update, but I also updated my PBX version to 66.0.6 as recommended, and it's still not working. Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 22, 2021 Report Share Posted January 22, 2021 Can you try 66.0.7? Link to comment Share on other sites More sharing options...
fred.bloggs Posted January 22, 2021 Report Share Posted January 22, 2021 Quote Can you try 66.0.7? We did: Quote We are comming form version 66.0.6 and I also tried with version 66.0.7. Same error. Link to comment Share on other sites More sharing options...
Support Posted January 22, 2021 Report Share Posted January 22, 2021 Under /reg_security.htm , for the "TLS max version" setting, can you try to set it to the highest version available and try this again on 66.0.7? Link to comment Share on other sites More sharing options...
Recommended Posts