Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bridge fails on LaunchRequest #7

Open
devedse opened this issue May 31, 2018 · 8 comments
Open

Bridge fails on LaunchRequest #7

devedse opened this issue May 31, 2018 · 8 comments

Comments

@devedse
Copy link

devedse commented May 31, 2018

I tried setting up the AlexaBridge locally but I ran into some errors:

image

For some reason whenever I type "start bridge" in the amazon alexa test suite a LaunchRequest message is being sent to the bridge. However the bridge doesn't seem to be able to handle this.

I want to create a conversational bot using the Bot Framework.

@Endeavour-BRM
Copy link

I see there is no condition in the bridge script to handle Launch Request. Does this require fix.

@devedse
Copy link
Author

devedse commented Jun 6, 2018

I did do some fixes in my own fork of this repository. I'm not sure which of the changes we want to include:
devedse@2d6cad8

Furthermore it might be good to look at pointing the Azdeploy script to CatalystCode instead of daltskin:
devedse@3ba927d

@Endeavour-BRM
Copy link

@devedse Thanks. That helped. Request is going to bot framework. But get "timeout from alexa" and session ends before bot responds. Even with basic echo bot hosted in azure facing the same issue. I can see in the console after the session is ended message is received by the bridge from bot.

Even the bridge is hosted in cloud to avoid network latency.

Any ides how can I resolve this.

Please find the console output from the alexa bridge

Alexa utterance: jenkins
alexaIntent response time: 11
connector response time: 392
Subscribe event: Fdcra5NQUiHJc3wopizAiL|0000008 from: tcgbotwebapp message: You said jenkins
Alexa says:
SessionEndedRequest
closing the session
Alexa message out: You said jenkins.
Alexa Response Duration: 30001

@devedse
Copy link
Author

devedse commented Jun 8, 2018

Did you enable the direct channel and configure that?
Also the BotId is the name of the bot, not a guid.

@Endeavour-BRM
Copy link

@devedse yes. Direct channel is enabled. And you can see after the session closed because of timeout, bridge receives the message from bot "You said jenkins" and Alexa message out is constructed. But session is already closed. So message is not received by alexa.

@devedse
Copy link
Author

devedse commented Jul 6, 2018

What we did was rebuild this in C# using the AlexaSkillsKit Nuget package as this implementation is missing verification anyway. The effort was about 1 day of work.

@GhostAtom
Copy link

GhostAtom commented Oct 2, 2018

@devedse did you pushed the c# version to github?

@devedse
Copy link
Author

devedse commented Jan 8, 2019

@GhostAtom I don't have the IP of the c# version, sorry :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants