Sean_Lindsay | 2018-10-25 09:15:41 UTC | #1
HI
I have been trying to get the Amazon Lex Integration working on our dev org in order to demo this to customers, sadly we have not been successful. I have spoken with the help-desk and they recommended I post here to seek assistance.
Details
I have created a AWS account and setup the bot, Testing on the application itself seems to work as expected however when I route a call in Architect and call the data action it does not seem to respond and goes down the failure path. I have gone through all the help guides and ensured the setup has been done correctly, I have also spoken to the genesys pre-sales team and they have the same issues with physical edges.
The only time I have seen this working is with the BYOC solution.
Could anyone assist with some additional information on how we can resolve this, your help will be greatly appreciated.
Regards Sean Lindsay
MelissaBailey | 2018-10-25 18:24:10 UTC | #2
Hi Sean,
What's the error type or message? (Add variables to the Failure Outputs and then play them in a Play Audio action).
Sean_Lindsay | 2018-11-06 17:37:36 UTC | #3
HI Melissa
I have added some variables to the Failure Outputs within architect and I get the following messages
- That my bot may be incorrectly configured/Installed, please review ad try again.
- No Xbot resource
I have checked the documentation and the AWS configuration, this is all correct.
Please note I am using the "BookTrip" Template provided by AWS with no customisation at all. Any further details will be greatly appreciated.
Regards Sean
MelissaBailey | 2018-11-06 18:34:33 UTC | #4
What build are your edges using? If it's later than 7532, roll back to 7532 or earlier. There's a known issue using lex with later builds.
system | 2018-12-07 18:34:35 UTC | #5
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 3815