1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
Since the bot is working fine from the Lex console, sounds like it more of an issue with the link up to Amazon Connect. Have you checked that it is calling the correct bot/alias from Connect CloudWatch Logs? In the log where you are getting an error on GetCustomerInput block, there is more details around the bot it is using, such as below. Make sure it is calling the correct botID/aliasID.
"Parameters": {
"NoInputTimeout": "3000",
"TextToSpeechType": "text",
"LexVersion": "V2",
"BotAliasArn": "arn:aws:lex:us-west-2:xxxxxxxxxxxx:bot-alias/XXXXXXXXXX/ALIASID",
"Parameter": "",
"Text": "How can I help you?",
"Voice": "Matthew",
"MaxSpeechDuration": "12000"
}
beantwortet vor 6 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- Wie verbinde ich verschiedene Zweigstellen mithilfe von AWS Site-to-Site VPN und AWS Direct Connect?AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
I did have the bot settings correct, but I found a way around it. I was able to rebuild the whole thing to work with one bot by setting an contact attribute so when they select 2 it's not actually directing to another bot, it just sets the attribute and then sends its to the main bot. I rebuilt the lambda function to handle the responses differently depending on what has been set. I also changed the voice for each response so that I can tell which one is responding and it seems to be working for the most part.