Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: New Amazon Echo Support
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Can you hit our web server via the external IP address that you have the Amazon stuff pointed at? You can also do some testing from the Amazon side in the skill section, to send a test message and it'll show you want you got back (if anything.) That can give you hints as to what's going on. You can also test from the Lamba side using the sample message that was created in the skill area.
Can you hit our web server via the external IP address that you have the Amazon stuff pointed at? --- Yes

You can also do some testing from the Amazon side in the skill section, to send a test message and it'll show you want you got back (if anything.) --- Did that and it worked.

You can also test from the Lamba side using the sample message that was created in the skill area. -- Did that and it worked too

I am unable to get the Echo to load the configuration. I have seen many different ways to tell her to do so...not sure what the correct way is...and how she knows to load it from the [cqc]\CQCData\Server\Data\Echo\EchoCfg.Txt
location.
Well...as always, once I post, I get it to work. Apparently it didn't like my Invocation Name...Control worked. CQC and Root didn't for me.

Let the fun begin!
EST Wrote:Well...as always, once I post, I get it to work. Apparently it didn't like my Invocation Name...Control worked. CQC and Root didn't for me.

Let the fun begin!

Alexa is very twitchy with regard to the control word. They have a bunch of reserved ones, and then add speech recognition on top of it. I think Dean mentioned that two syllable words work the best.
Dean,

I'm trying to get Alexa to connect securely. I had it working unsecured via port 80. I'm pretty sure I have everything in place now. This is what the log is capturing. Any hints to further trouble shoot this?


09/12 16:07:32-CQCMaster, CQCWebSrv, CQCWebSrvWorkerThread0
{
CIDSChan, CIDSChan_SChan.cpp.759, Failed/Cannot Do, Error: 5003/0/0
Could not acquire credentials. Name=Secure Server Data Source, Code=2148074254
<CQCWebSrv> CIDSChan_SChan.cpp - 790

}
When configuring the secure webserver it asks for the certificate location.

Here is what I have currently per instructions in the websocket client doc

MStore,My:home.zradomain.com

Now, and here in might lie my problem. The certificate that I created matches the above domain address, but that is not the name of the computer that the webserver is running on.

Does that matter?
It indicates it couldn't acquire the security credentials from the other side, which typically means they ain't talking or ain't talking right-like. Are you using a dynamic DNS system or have a fixed DNS address? The security certificate will only work when connecting to the exact host as the certificate was created for.

Oh, and also make sure the javascript is using the https prefix as well, since by default it's using the http prefix, which won't work. There is I think a thing at the top of the javascript file, but make sure it's getting used. If it's not, then it's probably just doing an HTTP connection.
zra Wrote:When configuring the secure webserver it asks for the certificate location.

Here is what I have currently per instructions in the websocket client doc

MStore,My:home.zradomain.com

Now, and here in might lie my problem. The certificate that I created matches the above domain address, but that is not the name of the computer that the webserver is running on.

Does that matter?

That's some externally visible domain name that maps to your public IP address right? If so, you will need to port forward the port you selected, to the CQC internal address of the CQC web server. So, when the javascript connects to that domain name, it gets your router's public IP, and then the port forward gets you to the CQC web server.
Dean Roddey Wrote:That's some externally visible domain name that maps to your public IP address right?

Correct

Dean Roddey Wrote:If so, you will need to port forward the port you selected, to the CQC internal address of the CQC web server. So, when the javascript connects to that domain name, it gets your router's public IP, and then the port forward gets you to the CQC web server.

All accomplished. It's getting through hence the error log message.

Clearly, though, I have something misconfigured.

Ignoring the java script(and yes, I have updated to "home.zrasdomain.com","443", "https", "ABCDEF"), another poster mentioned earlier in this thread to just try connecting to http://home.zrasdomain.com and looking for the CQC version of 404. I'm not getting that.
Does the security certificate need to use the name of the computer that it will ultimately be identifying?

It seems logical that it would and that is not what my certifcate currently issued does. Maybe this is the problem?

CQCMaster.zrasdomain.local = actual computer name

home.zrasdomain.com = internet DNS name mapped to my WAN IP.

home.zrasdomain.com = what i named the certificate.

Does this seem correct?