OND Posted September 27, 2020 Report Share Posted September 27, 2020 Hello. I am trying to get my voicemail transcription via Google speech-to-text API working, but haven't been able to get it going. Documentation on this pretty limited, but I followed the instructions on this page: https://doc.vodia.com/voicemail_transcription I have Voicemail to text API enabled in the domain settings and have tried leaving some test messages to see if I get an email with the transcribed message, but I do not. I just get an email with a recording of the message attached. When I check the logfile of the test call, this is what I get: [7] 13:50:47.778 APP: No authentication of call because call comes from trunk [6] 13:50:47.779 MEDI: Port 67: Sending RTP to 67.231.9.93:45614, codec not set yet [5] 13:50:47.780 APP: Port 67: Incoming call in domain bws on port 67 trunk Bandwidth 2 (9) [5] 13:50:47.780 APP: Call 21: New call created with Call-ID 67 [4] 13:50:47.780 APP: Dial number +17029960700 [4] 13:50:47.780 APP: Dial number 801 from user 600 and dial plan Default [7] 13:50:47.781 MEDI: Port 67: Set codec preference count 5 [6] 13:50:47.781 MEDI: Port 67: Choose codec PCMU/8000 [7] 13:50:47.781 SIP: Use codec PCMU/8000 for call-leg 67 [7] 13:50:53.406 MEDI: Port 67: Received RFC4733 DTMF on codec 101 [6] 13:50:53.406 APP: Received DTMF 1, call type attendant [4] 13:50:53.406 APP: Dial number 8201 from user 801 and dial plan Default [5] 13:51:25.420 APP: MWI state 5/2 (0/0) on user 201@qts changed [5] 13:51:25.421 APP: Nothing changed in the MWI state 5/2 (0/0) on user 201@bws [5] 13:51:25.585 APP: Last message repeated 2 times [7] 13:51:25.585 WEBC: https:license.vodia.com:443: DNS A returned 54.175.147.78 [7] 13:51:25.585 WEBC: https:license.vodia.com:443: Connect to 54.175.147.78 [7] 13:51:26.079 WEBC: https:license.vodia.com:443: Return code 200 Date: Sun, 27 Sep 2020 20:51:25 GMT Server: Apache/2.4.29 (Ubuntu) Transfer-Encoding: chunked Content-Type: audio/mpeg [6] 13:51:26.080 APP: Wrote 17496 bytes for to recordings/msg33204.mp3 [7] 13:51:26.084 EMAI: smtp.office365.com:587: Start sending to <daniel@vrxrus.com> [7] 13:51:26.117 EMAI: smtp.office365.com:587: DNS A returned 52.96.70.130 [7] 13:51:26.117 EMAI: smtp.office365.com:587: Connect to 52.96.70.130:587 [7] 13:51:26.127 EMAI: smtp.office365.com:587: Connected [7] 13:51:27.412 EMAI: Sent email to <daniel@vrxrus.com> I may be wrong, but I would expect to see the server attempt the transcription somewhere in the logfile, probably starting with a WEBC, but there is nothing. Is there somewhere else in the system programming that I need to enable the speech-to-text API? Any help would be greatly appreciated! I am running Vodia multi-tenant hosted PBX version 66.0.2 (Debian 64), hosted on Google Cloud Platform Link to comment Share on other sites More sharing options...
OND Posted September 28, 2020 Author Report Share Posted September 28, 2020 I just tried again and pulled a logfile from the Administrator level this time and got this: [7] 21:48:54.943 https:speech.googleapis.com:443: DNS A returned 216.58.193.202ⓘ [7] 21:48:54.943 https:speech.googleapis.com:443: Connect to 216.58.193.202ⓘ [7] 21:48:54.943 Closing connection smtp.gmail.comⓘ [7] 21:48:54.958 Last message repeated 2 timesⓘ [4] 21:48:54.958 Unknown hash algorithm 2A864886F70D01010Bⓘ [5] 21:48:54.958 HTTP 216.58.193.202: Certificate for speech.googleapis.com could not be verifiedⓘ [7] 21:48:54.958 Closing connection smtp.gmail.comⓘ [7] 21:48:54.958 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 21:48:54.958 https:speech.googleapis.com:443: Return code 500ⓘ [7] 21:48:54.958 Transscript for 12s failed with code 500ⓘ [7] 21:48:54.959 Closing connection https:speech.googleapis.com:443ⓘ [7] 21:48:54.959 Closing connection smtp.gmail.comⓘ There must be something I'm missing. Any help would be greatly appreciated Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 28, 2020 Report Share Posted September 28, 2020 I would try to reset the lost of root certificates on your PBX. Maybe you have an old list on your installation (they are not automatically updated with a PBX software. upgrade). Link to comment Share on other sites More sharing options...
OND Posted September 28, 2020 Author Report Share Posted September 28, 2020 Thank you for your reply! I reset the certificates but still nothing. I noticed it says: [5] 21:48:54.958 HTTP 216.58.193.202: Certificate for speech.googleapis.com could not be verifiedⓘ Should speech.googleapis.com be in my list of certificates? It's not currently in there. If it should be, how would I go about adding it? Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 28, 2020 Report Share Posted September 28, 2020 I tried this here—worked. Try to rename the certificates folder to certificates2, restart the PBX service and see if that cleared it up? That would have been a "hard" reset of the trusted Root CA. Link to comment Share on other sites More sharing options...
OND Posted September 28, 2020 Author Report Share Posted September 28, 2020 Ok, I will try that tonight after business hours. Do you happen to know the directory or where that folder would be located? My PBX is hosted and I'm not super well versed on Linux, but I'm pretty sure I can figure it out if I know where to look. Link to comment Share on other sites More sharing options...
Support Posted September 28, 2020 Report Share Posted September 28, 2020 It should be inside /usr/local/pbx folder. Link to comment Share on other sites More sharing options...
OND Posted September 28, 2020 Author Report Share Posted September 28, 2020 Got it. I'll let you know what happens. Thanks again! Link to comment Share on other sites More sharing options...
OND Posted October 2, 2020 Author Report Share Posted October 2, 2020 I tried renaming the folder, but it won't let me. I keep getting a "permission denied" message. Do I maybe need to shut down the server first? Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 2, 2020 Report Share Posted October 2, 2020 You need to make sure that you have the right permission, e.g. use sudo in Linux. Link to comment Share on other sites More sharing options...
OND Posted October 9, 2020 Author Report Share Posted October 9, 2020 I finally got around to trying this again and was able to change the folder name to "certificates2". I restarted the server and all of the sudden I could no longer login to the PBX using my admin credentials. I instead was able to get in with the default credentials, but then the interface looked completely off, and none of my domains were showing up, and nothing in the portal in general was working correctly. I was however still able to make and receive calls. I logged back into the server via SSH and was that the system had created a new "certificates" folder. I ended up deleting it and renaming the "certificates2" folder back to "certificates", rebooted, and everything came back up as normal. I an still however not getting transcripts of messages. I check the logfile and still see this in the the log: [7] 22:57:47.310 https:speech.googleapis.com:443: DNS A returned 172.217.5.74ⓘ [7] 22:57:47.310 https:speech.googleapis.com:443: Connect to 172.217.5.74ⓘ [7] 22:57:47.310 Closing connection smtp.gmail.comⓘ [7] 22:57:47.345 Last message repeated 2 timesⓘ [4] 22:57:47.345 Unknown hash algorithm 2A864886F70D01010Bⓘ [5] 22:57:47.345 HTTP 172.217.5.74: Certificate for speech.googleapis.com could not be verifiedⓘ [7] 22:57:47.345 Closing connection smtp.gmail.comⓘ [7] 22:57:47.346 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 22:57:47.346 https:speech.googleapis.com:443: Return code 500ⓘ [7] 22:57:47.346 Transscript for 6s failed with code 500ⓘ [7] 22:57:47.346 Closing connection https:speech.googleapis.com:443ⓘ Any other suggestions? Did I do something wrong? Link to comment Share on other sites More sharing options...
OND Posted October 21, 2020 Author Report Share Posted October 21, 2020 I still haven't been able to get this working, any other suggestions? Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 21, 2020 Report Share Posted October 21, 2020 We tried this on our own server and it still works... Actually Google changed something in our API settings, and we had to re-enable the API on the Google console. Are you still getting those 500 codes, or now maybe something from Google that says "permission denied" or something like that? You can turn on the log level for the web client which should show you what the PBX is trying to send and what the cloud service responds. Link to comment Share on other sites More sharing options...
OND Posted October 21, 2020 Author Report Share Posted October 21, 2020 I just tried it again and here's what came up in the log: [6] 15:10:08.208 1 more requests pending to push.vodia.net:443ⓘ [6] 15:10:08.208 2 more requests pending to push.vodia.net:443ⓘ [7] 15:10:08.252 https:speech.googleapis.com:443: DNS A returned 172.217.14.106ⓘ [7] 15:10:08.252 https:speech.googleapis.com:443: Connect to 172.217.14.106ⓘ [7] 15:10:08.288 https:push.vodia.net:443: DNS A returned 54.175.147.78ⓘ [7] 15:10:08.288 https:push.vodia.net:443: Connect to 54.175.147.78ⓘ [7] 15:10:08.288 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 15:10:08.288 https:speech.googleapis.com:443: Return code 500ⓘ [7] 15:10:08.288 Transscript for 7s failed with code 500ⓘ [7] 15:10:08.288 Closing connection https:speech.googleapis.com:443ⓘ [5] 15:10:08.289 Last message repeated 2 timesⓘ [7] 15:10:08.289 https:license.vodia.com:443: DNS A returned 54.175.147.78ⓘ [7] 15:10:08.289 Last message repeated 2 timesⓘ [7] 15:10:08.289 https:license.vodia.com:443: Connect to 54.175.147.78ⓘ [7] 15:10:08.629 Last message repeated 2 timesⓘ [7] 15:10:08.629 https:license.vodia.com:443: Return code 200ⓘ Date: Wed, 21 Oct 2020 22:10:08 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 7632 Content-Type: audio/mpeg [7] 15:10:08.646 https:push.vodia.net:443: Return code 200ⓘ Date: Wed, 21 Oct 2020 22:10:08 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [7] 15:10:08.766 https:push.vodia.net:443: Return code 200ⓘ Date: Wed, 21 Oct 2020 22:10:08 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 4 Content-Type: application/json [7] 15:10:08.833 https:push.vodia.net:443: Return code 200ⓘ Date: Wed, 21 Oct 2020 22:10:08 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [7] 15:10:09.324 https:api.ipify.org:443: DNS A returned 54.235.182.194ⓘ [7] 15:10:09.324 https:api.ipify.org:443: Connect to 54.235.182.194ⓘ [7] 15:10:09.665 https:api.ipify.org:443: Return code 200ⓘ Server: Cowboy Connection: keep-alive Content-Type: application/json Vary: Origin Date: Wed, 21 Oct 2020 22:10:09 GMT Content-Length: 21 Via: 1.1 vegur [7] 15:10:23.654 Closing connection https:license.vodia.com:443ⓘ [7] 15:10:23.912 Closing connection https:push.vodia.net:443ⓘ [7] 15:10:24.292 https:api.ipify.org:443: DNS A returned 54.235.182.194ⓘ [7] 15:10:24.292 https:api.ipify.org:443: Connect to 54.235.182.194ⓘ [7] 15:10:24.707 https:api.ipify.org:443: Return code 200ⓘ Server: Cowboy Connection: keep-alive Content-Type: application/json Vary: Origin Date: Wed, 21 Oct 2020 22:10:24 GMT Content-Length: 21 Via: 1.1 vegur Link to comment Share on other sites More sharing options...
Support Posted October 22, 2020 Report Share Posted October 22, 2020 Hi, Did you re-enable the API on google's console (you will get the API URL in the error logs on our PBX as above) ? That generally is the issue. Link to comment Share on other sites More sharing options...
OND Posted October 22, 2020 Author Report Share Posted October 22, 2020 So here's how I have it setup on my Google Console Link to comment Share on other sites More sharing options...
Support Posted October 22, 2020 Report Share Posted October 22, 2020 Yes you can add the IP address of the PBX without the subnet mask as well. Also, after this point turn on the logs on PBX and it will give you the URl where you can enable the voicemail API from, and that should be the last step. Link to comment Share on other sites More sharing options...
OND Posted October 22, 2020 Author Report Share Posted October 22, 2020 Ok, I have the log on, here's what I get: [6] 8:00:26.465 1 more requests pending to push.vodia.net:443ⓘ [6] 8:00:26.466 2 more requests pending to push.vodia.net:443ⓘ [7] 8:00:26.534 https:speech.googleapis.com:443: DNS A returned 172.217.5.202ⓘ [7] 8:00:26.534 https:speech.googleapis.com:443: Connect to 172.217.5.202ⓘ [7] 8:00:26.570 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 8:00:26.570 https:speech.googleapis.com:443: Return code 500ⓘ [7] 8:00:26.570 Transscript for 9s failed with code 500ⓘ [7] 8:00:26.571 Closing connection https:speech.googleapis.com:443ⓘ [7] 8:00:26.571 https:push.vodia.net:443: DNS A returned 54.175.147.78ⓘ [7] 8:00:26.571 https:push.vodia.net:443: Connect to 54.175.147.78ⓘ [5] 8:00:26.571 Last message repeated 2 timesⓘ [7] 8:00:26.571 https:license.vodia.com:443: DNS A returned 54.175.147.78ⓘ [7] 8:00:26.571 Last message repeated 2 timesⓘ [7] 8:00:26.571 https:license.vodia.com:443: Connect to 54.175.147.78ⓘ [7] 8:00:26.879 https:push.vodia.net:443: Return code 200ⓘ Which part is the URI? Link to comment Share on other sites More sharing options...
Support Posted October 22, 2020 Report Share Posted October 22, 2020 Please enable to the level 9 and turn on (respectively): Webclient, trunk and call messages. Link to comment Share on other sites More sharing options...
OND Posted October 22, 2020 Author Report Share Posted October 22, 2020 Ok, here's what I got. I tried to get rid of anything that wasn't related to my test call, but a lot of calls are coming in: [5] 8:19:42.050 SIP Rx 67.231.8.195:5060:ⓘ INVITE sip:+17028577960@34.94.42.237 SIP/2.0 Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK1531.21abeb32.1 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B413dbeea9f9b06db From: "DAVID HINOJOS " <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90> Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282963 INVITE Max-Forwards: 68 Allow: INVITE,ACK,CANCEL,BYE,REFER,OPTIONS Accept: application/sdp Contact: <sip:+17023253253@192.168.5.233:5060> Content-Length: 330 Content-Disposition: session; handling=required Content-Type: application/sdp Remote-Party-ID: "DAVID HINOJOS " <sip:+17023253253@192.168.5.233:5060>;privacy=off;screen=no v=0 o=Sonus_UAC 768753 791015 IN IP4 192.168.5.233 s=SIP Media Capabilities c=IN IP4 67.231.9.93 t=0 0 m=audio 50648 RTP/AVP 0 18 96 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 iLBC/8000 a=fmtp:96 mode=30 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:30 [8] 8:19:42.051 Find trunk: Message RURI user +17028577960, host 34.94.42.237ⓘ [9] 8:19:42.051 Find trunk: Try expression for 3ⓘ [9] 8:19:42.051 Find trunk: Try expression for 5ⓘ [9] 8:19:42.051 Find trunk: Try expression for 7ⓘ [9] 8:19:42.051 Find trunk: Trunk 8 matches domain localhostⓘ [9] 8:19:42.051 Find trunk: Try expression for 8ⓘ [9] 8:19:42.051 Find trunk: Trunk 9 matches domain localhostⓘ [9] 8:19:42.051 Find trunk: Trunk 9 matches IPⓘ [9] 8:19:42.051 Find trunk: Trunk 9 matches IP and portⓘ [9] 8:19:42.051 Find trunk: Try expression for 9ⓘ [8] 8:19:42.051 Identify trunk (IP address/port and domain match) Bandwidth 2 (9)ⓘ [8] 8:19:42.051 Trying to match number 7028577960 with ERE (.*)ⓘ [8] 8:19:42.051 Send call to extension ERE returned +17028577960ⓘ [8] 8:19:42.051 Global trunk sends call into domain qtsⓘ [5] 8:19:42.052 SIP Tx 67.231.8.195:5060:ⓘ SIP/2.0 100 Trying Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK1531.21abeb32.1 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B413dbeea9f9b06db Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> From: "DAVID HINOJOS " <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282963 INVITE Content-Length: 0 [8] 8:19:42.052 Trying to match number 7028577960 with ERE (.*)ⓘ [8] 8:19:42.052 Send call to extension ERE returned +17028577960ⓘ [8] 8:19:42.052 Global trunk sends call into domain qtsⓘ [8] 8:19:42.053 Trying to match number 7028577960 with ERE (.*)ⓘ [8] 8:19:42.053 Send call to extension ERE returned +17028577960ⓘ [8] 8:19:42.053 Trying to match number 7028577960 with ERE (.*)ⓘ [8] 8:19:42.053 Send call to extension ERE returned +17028577960ⓘ [8] 8:19:42.053 Trying to match number 7028577960 with ERE (.*)ⓘ [8] 8:19:42.053 Send call to extension ERE returned +17028577960ⓘ [5] 8:19:42.055 SIP Tx 67.231.8.195:5060:ⓘ SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK1531.21abeb32.1 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B413dbeea9f9b06db Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> From: "DAVID HINOJOS " <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282963 INVITE Contact: <sip:+17028577960@34.94.42.237:5060;transport=udp> Supported: replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, INFO, UPDATE Allow-Events: refer Accept: application/sdp User-Agent: Vodia-PBX/66.0.2 Content-Type: application/sdp Content-Length: 249 v=0 o=- 1545553338 1545553338 IN IP4 34.94.42.237 s=- c=IN IP4 34.94.42.237 t=0 0 m=audio 54548 RTP/AVP 0 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv [5] 8:19:42.056 SIP Tx 67.231.8.195:5060:ⓘ SIP/2.0 200 Ok Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK1531.21abeb32.1 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B413dbeea9f9b06db Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> From: "DAVID HINOJOS " <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282963 INVITE Contact: <sip:+17028577960@34.94.42.237:5060;transport=udp> Supported: replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, INFO, UPDATE Allow-Events: refer Accept: application/sdp User-Agent: Vodia-PBX/66.0.2 Content-Type: application/sdp Content-Length: 249 v=0 o=- 1545553338 1545553338 IN IP4 34.94.42.237 s=- c=IN IP4 34.94.42.237 t=0 0 m=audio 54548 RTP/AVP 0 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv [5] 8:19:42.130 SIP Rx 67.231.8.195:5060:ⓘ ACK sip:+17028577960@34.94.42.237:5060;transport=udp SIP/2.0 Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK1531.21abeb32.3 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B4143fed110553c6f From: <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282963 ACK Max-Forwards: 69 Content-Length: 0 [5] 8:20:00.417 SIP Rx 67.231.8.195:5060:ⓘ BYE sip:+17028577960@34.94.42.237:5060;transport=udp SIP/2.0 Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bKe431.987f74b1.0 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B44515a2a10553c6f From: <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282964 BYE Max-Forwards: 69 Content-Length: 0 [5] 8:20:00.417 SIP Tx 67.231.8.195:5060:ⓘ SIP/2.0 200 Ok Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bKe431.987f74b1.0 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B44515a2a10553c6f Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> From: <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282964 BYE Contact: <sip:+17028577960@34.94.42.237:5060;transport=udp> User-Agent: Vodia-PBX/66.0.2 Content-Length: 0 [6] 8:20:00.420 1 more requests pending to push.vodia.net:443ⓘ [6] 8:20:00.420 2 more requests pending to push.vodia.net:443ⓘ [7] 8:20:00.438 https:speech.googleapis.com:443: DNS A returned 216.58.193.202ⓘ [7] 8:20:00.438 https:speech.googleapis.com:443: Connect to 216.58.193.202ⓘ [9] 8:20:00.439 https:speech.googleapis.com:443: Send request (129270 bytes)ⓘ POST /v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY HTTP/1.1 Host: speech.googleapis.com Content-Type: application/json; charset=utf-8" Content-Length: 129087 {"config":{"encoding":"LINEAR16","sampleRateHertz":8000,"languageCode":"en-US","maxAlternatives":1,"profanityFilter":true,"model":"phone_call","enableAutomaticPunctuation":true,"enableWordTimeOffsets":false},"audio":{"content":"AAAIAAAAAAD4//j/+P/w//j/+P/w//D/8P/w//D/+P8AAAAA+P8AAAAAAAD4//j/+P8AAAAAAAAIAAgAAAAAAAAACAAIAAAA+P8AAAAAAAAIAAAAAAAIAAAAAAAIgA [9] 8:20:00.439 Initialize TLS connectionⓘ [7] 8:20:00.453 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 8:20:00.453 https:speech.googleapis.com:443: Return code 500ⓘ [8] 8:20:00.453 https:speech.googleapis.com:443: Return content (0 bytes)ⓘ [7] 8:20:00.453 Transscript for 6s failed with code 500ⓘ [7] 8:20:00.454 Closing connection https:speech.googleapis.com:443ⓘ [5] 8:20:00.455 Last message repeated 2 timesⓘ [7] 8:20:00.455 https:license.vodia.com:443: DNS A returned 54.175.147.78ⓘ [7] 8:20:00.455 Last message repeated 2 timesⓘ [7] 8:20:00.455 https:license.vodia.com:443: Connect to 54.175.147.78ⓘ [7] 8:20:00.522 Last message repeated 2 timesⓘ [9] 8:20:00.522 https:license.vodia.com:443: Send request (9994 bytes)ⓘ POST /transcode?code=5NQRWETFB2QZ HTTP/1.1 Host: license.vodia.com Content-Type: audio/wav Content-Length: 9876 [9] 8:20:00.522 Last message repeated 2 timesⓘ [9] 8:20:00.522 Initialize TLS connectionⓘ [7] 8:20:00.657 https:push.vodia.net:443: DNS A returned 54.175.147.78ⓘ [7] 8:20:00.657 https:push.vodia.net:443: Connect to 54.175.147.78ⓘ [9] 8:20:00.724 https:push.vodia.net:443: Send request (536 bytes)ⓘ POST /fcm HTTP/1.1 Host: push.vodia.net Content-Type: application/json Content-Length: 439 {"code":"5NQRWETFB2QZ","message":"{\"notification\":{\"title\":\"\\\"David Hinojos\\\" <sip:201@qts>\",\"text\":\"\\\"David Hinojos\\\" <sip:201@qts> sent you a voicemail.\",\"tag\":\"vodia\"},\"data\":{\"message\":{\"action\":\"voicemail\",\"vmfrom\":\"\\\"David Hinojos\\\" <sip:201@qts>\"}},\"to\":\"a@293D91BF215EE7A841FA0C294F2A4799F7F43922C7DF373BAE2BB85B9E2274A4@1039CDC378534B24D1F964ACBC5F79E56ECF5549B7A672D9808FAA00D8337716\"}"} [9] 8:20:00.724 Initialize TLS connectionⓘ [9] 8:20:00.783 Last message repeated 2 timesⓘ [9] 8:20:00.783 Received 6328 bytesⓘ HTTP/1.1 200 OK Date: Thu, 22 Oct 2020 15:20:00 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 6192 Content-Type: audio/mpeg [9] 8:20:00.783 Last message repeated 2 timesⓘ [7] 8:20:00.783 https:license.vodia.com:443: Return code 200ⓘ Date: Thu, 22 Oct 2020 15:20:00 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 6192 Content-Type: audio/mpeg [7] 8:20:00.783 Last message repeated 2 timesⓘ [8] 8:20:00.783 https:license.vodia.com:443: Return content (6192 bytes)ⓘ [9] 8:20:00.973 Received 144 bytesⓘ HTTP/1.1 200 OK Date: Thu, 22 Oct 2020 15:20:00 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [7] 8:20:00.973 https:push.vodia.net:443: Return code 200ⓘ Date: Thu, 22 Oct 2020 15:20:00 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [8] 8:20:00.973 https:push.vodia.net:443: Return content (5 bytes)ⓘ false [9] 8:20:00.973 https:push.vodia.net:443: Send request (557 bytes)ⓘ POST /fcm HTTP/1.1 Host: push.vodia.net Content-Type: application/json Content-Length: 460 {"code":"5NQRWETFB2QZ","message":"{\"notification\":{\"title\":\"\\\"David Hinojos\\\" <sip:201@qts>\",\"text\":\"\\\"David Hinojos\\\" <sip:201@qts> sent you a voicemail.\",\"tag\":\"vodia\"},\"data\":{\"message\":{\"action\":\"voicemail\",\"vmfrom\":\"\\\"David Hinojos\\\" <sip:201@qts>\"}},\"to\":\"cTchbil1DFA:APA91bEVCIEdQLURgiuqOLaUnd6gs3An2Bt2qdJ_BiIst77DQxa8l7NdAg_3TRk2aaxToa4-g_StXxNlwmZTXAdZq2nTpwT_nUt5OVE8-pbxyj9ulr8FqyjNBYtr0Y-DhNeIbJLUuHCT\"}"} [9] 8:20:01.098 Received 143 bytesⓘ HTTP/1.1 200 OK Date: Thu, 22 Oct 2020 15:20:01 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 4 Content-Type: application/json [7] 8:20:01.099 https:push.vodia.net:443: Return code 200ⓘ Date: Thu, 22 Oct 2020 15:20:01 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 4 Content-Type: application/json [8] 8:20:01.099 https:push.vodia.net:443: Return content (4 bytes)ⓘ true [9] 8:20:01.099 https:push.vodia.net:443: Send request (536 bytes)ⓘ POST /fcm HTTP/1.1 Host: push.vodia.net Content-Type: application/json Content-Length: 439 {"code":"5NQRWETFB2QZ","message":"{\"notification\":{\"title\":\"\\\"David Hinojos\\\" <sip:201@qts>\",\"text\":\"\\\"David Hinojos\\\" <sip:201@qts> sent you a voicemail.\",\"tag\":\"vodia\"},\"data\":{\"message\":{\"action\":\"voicemail\",\"vmfrom\":\"\\\"David Hinojos\\\" <sip:201@qts>\"}},\"to\":\"a@293D91BF215EE7A841FA0C294F2A4799F7F43922C7DF373BAE2BB85B9E2274A4@AD5845087F3AF766567F4F90BE2D6E644D31E316F237A6116B0CDA3259047BFC\"}"} [9] 8:20:01.166 Received 144 bytesⓘ HTTP/1.1 200 OK Date: Thu, 22 Oct 2020 15:20:01 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [7] 8:20:01.166 https:push.vodia.net:443: Return code 200ⓘ Date: Thu, 22 Oct 2020 15:20:01 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [8] 8:20:01.166 https:push.vodia.net:443: Return content (5 bytes)ⓘ false Link to comment Share on other sites More sharing options...
Support Posted October 22, 2020 Report Share Posted October 22, 2020 Please upgrade to 66.0.3 and enter the transcript time to 30 secs on the PBX settings and try this again. It didn't give you the URL, maybe it is enabled, but it may send that out the next time. Link to comment Share on other sites More sharing options...
OND Posted October 22, 2020 Author Report Share Posted October 22, 2020 Ok, I’ll try that after hours tonight and let you know what happened. Thank you for all your help! Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 23, 2020 Report Share Posted October 23, 2020 Can you just try curl https:speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY from your machine? From the log it looks to me like there is no TLS negotiation going on at all. Maybe the firewall is just blocking traffic to that location. Link to comment Share on other sites More sharing options...
OND Posted October 23, 2020 Author Report Share Posted October 23, 2020 Sorry, I'm still relatively new to this. What do you mean by: 2 hours ago, Vodia PBX said: curl https:speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY from your machine? Is that something I would do in the firewall within my GCP interface? Or something I would do from a command prompt within SSH? Link to comment Share on other sites More sharing options...
Support Posted October 23, 2020 Report Share Posted October 23, 2020 2 hours ago, Vodia PBX said: just try curl https:speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY from your machine Just this part, and see if that goes all 200 OK which would mean your firewall is not an issue. You can also try it from your browser. Link to comment Share on other sites More sharing options...
Recommended Posts