Lex slot input not sent after third try with AudioCodes VoiceAI integration

Question

I have a Lex bot integrated with AudioCodes VoiceAI.
One of my slots (CartConfirmation) accepts 3 values: Submit / Reject / Repeat. I allow users to say "Repeat" a maximum of 2 times in a row.

Here’s what happens:
On the first attempt, if the user says "Repeat", AudioCodes recognizes the speech and forwards it correctly to Lex.
On the second attempt, if the user again says "Repeat", AudioCodes again recognizes and sends the input to Lex.
On the third attempt, if the user says "yeah submit", AudioCodes correctly recognizes the speech, but the recognized input is not sent to Lex at all.

My slot configuration:
Slot name: CartConfirmation
Advanced options → Bot elicits information →
     Users can interrupt prompt: **Disabled**
     Invoke Lambda code hook after each elicitation: **Enabled **(for slot validation)
     Maximum number of retries: **1**
Dialog code hook: **Disabled**

I am using Lambda for slot validation and to handle business rules.
The issue is: after two “Repeat” inputs, the third input (even if valid, e.g., Submit) is blocked and never reaches Lex.

When I test the same flow in the Lex console simulator, everything works as expected (the 3rd input Submit is accepted). But When I test via TFN with AudioCodes VoiceAI, the 3rd input is recognized at AudioCodes STT but never forwarded to Lex.

Is there any configurations I need to change on Lex side or is it something to be checked within AudioCodes side?

re:Post Agent · Answer

Based on your description, this appears to be an integration issue between AudioCodes VoiceAI and Amazon Lex rather than a problem with your Lex configuration itself. Since the same flow works correctly in the Lex console simulator but fails when using AudioCodes, the issue is likely on the AudioCodes side.

The behavior you're describing suggests that AudioCodes might be implementing its own retry logic or session management that's interfering with Lex's native retry mechanism. After two "Repeat" inputs, AudioCodes may be incorrectly handling the session state or not properly forwarding the third input to Lex.

Here are some potential areas to investigate:

1. Check if AudioCodes has any specific timeout settings or retry limitations in its Lex integration configuration. The issue might be related to how AudioCodes handles speech timeouts or session management.

2. Verify if there are any session attributes being set by AudioCodes that might be affecting the conversation flow. Session attributes can influence how inputs are processed.

3. Examine the AudioCodes logs to see if the third input is being recognized but not forwarded to Lex due to some internal logic or error.

4. Consider adjusting your Lambda function to include specific session attributes that might help control the flow between AudioCodes and Lex, particularly around retry handling.

Since the issue doesn't occur in the Lex console, your Lex configuration (maximum retries set to 1, Lambda validation enabled) appears to be working as expected. The problem is more likely in how AudioCodes is managing the conversation session or forwarding inputs to Lex after multiple retries.  
**Sources**  
[How to get out of the RETRY loop for Lex Slot Confirmation | AWS re:Post](https://repost.aws/questions/QUuuPe7AoRSpOPx71XOtgT9Q/how-to-get-out-of-the-retry-loop-for-lex-slot-confirmation)  
[Amazon Connect Lex Integration – Need Control Over Lex Timeout for Spelling Inputs | AWS re:Post](https://repost.aws/questions/QU1KeGTU4mTPuz9MwcEQfJFQ/amazon-connect-lex-integration-need-control-over-lex-timeout-for-spelling-inputs)

Lex slot input not sent after third try with AudioCodes VoiceAI integration

Add your answer

Relevant content