Licenses and gRPC Status: Connect Failed

70 views
Skip to first unread message

Felipe Lohnefink

unread,
Nov 16, 2018, 8:41:52 AM11/16/18
to UniMRCP
Hi, Arsen.

I have updated the trial license files for GSR and GSS. I stop having the License Expired error but I am still not able to use GSS and GSR. That is the exact point in the Log where things start to get ugly. In that Warning of the gRPC.

   9204 MRCP/2.0 187 SPEAK 1^M
   9205 Channel-Identifier: 6bf17946cf2544d4@speechsynth^M
   9206 Content-Type: text/plain^M
   9207 Voice-Name: pt-BR-Standard-A^M
   9208 Content-Length: 37^M
   9209 ^M
   9210 Olá.
   9211 2018-11-16 11:24:05:719440 [INFO]   Assign Control Channel <6bf17946cf2544d4@speechsynth> to Connection 172.29.102.12:1544 <-> 172.29.101.63:39079 [0] -> [1]
   9212 2018-11-16 11:24:05:719477 [INFO]   Process SPEAK Request <6bf17946cf2544d4@speechsynth> [1]
   9213 2018-11-16 11:24:05:719527 [INFO]   Start Async Synth: encoding=1, sampling-rate=8000, language=pt-BR <6bf17946cf2544d4@gss>
   9214 2018-11-16 11:24:12:043883 [WARN]   gRPC Status: Connect Failed<6bf17946cf2544d4@gss>

Can you help me understand what is going on? Does it have anything to do with the new licenses? Where can I find more information about this warning?
Right after that I get this Error on the Log file:

   9214 2018-11-16 11:24:12:043883 [WARN]   gRPC Status: Connect Failed<6bf17946cf2544d4@gss>
   9215 2018-11-16 11:24:12:043985 [INFO]   Process SPEAK Response <6bf17946cf2544d4@speechsynth> [1]
   9216 2018-11-16 11:24:12:044041 [INFO]   Send MRCPv2 Data 172.29.102.12:1544 <-> 172.29.101.63:39079 [110 bytes]
   9217 MRCP/2.0 110 1 407 COMPLETE^M
   9218 Channel-Identifier: 6bf17946cf2544d4@speechsynth^M
   9219 Completion-Cause: 004 error^M
   9220 ^M
   9221 
   9222 2018-11-16 11:24:12:046529 [INFO]   TCP/MRCPv2 Peer Disconnected 172.29.102.12:1544 <-> 172.29.101.63:39079

I tried a couple of things to solve this but none of them did.
I even looked in the GSS Manual and found this line of configuration in my umsgss.xml file:

<umsgss license-file="umsgss_*.lic" gapp-credentials-file="*.json">

Do I also need a new license from the Google API?

Any help would be great.
Thanks!

Arsen Chaloyan

unread,
Nov 16, 2018, 12:47:06 PM11/16/18
to UniMRCP
Hi Felipe,

You do not need to update your Google credentials. I see that gRPC connection to the service could not be established. Assuming the access to the service is OK, I would suggest to check the date/time on your server, which needs to be strictly synchronized; otherwise TLS handshake to the service will fail.

--
You received this message because you are subscribed to the Google Groups "UniMRCP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unimrcp+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
Arsen Chaloyan
Author of UniMRCP
http://www.unimrcp.org
Reply all
Reply to author
Forward
0 new messages