Caller Inputs and Telephony System Responses

Application Testing by Simulation > Using the Avaya Application Simulator to Simulate Applications > Simulating Run-time Scenarios > Caller Inputs and Telephony System Responses

	Caller Inputs and Telephony System Responses

Usually, a speech application works by prompting a caller for inputs and then interpreting and responding to those inputs. Inputs can be in the form of DTMF (touchtone) key presses or spoken replies. In Dialog Designer, you can simulate those responses when you test applications.

Simulating DTMF Inputs

To simulate DTMF inputs:

During simulation, the AAS prompts for a response in which a DTMF key press is an option. To indicate that the AAS is waiting for a DTMF input, the Waiting DTMF indicator in the Input tab turns green.

Click the key or keys on the DTMF keypad that correspond with the DTMF input you want to submit.

As you click the keys, the AAS simulates the corresponding DTMF tone. At the same time, the AAS displays the digits in the field below the keypad.

Click Send Digits.

Note:

The Send Digits button is located below the DTMF keypad in the Input tab. Depending on your monitor size and resolution, you might have to increase the size of the Avaya Application Simulator view to see this button.

Simulate Spoken Inputs with a Microphone

Note:

Before you can use a microphone to simulate ASR input, you must have the Microsoft Speech SDK installed and properly configured. The Microsoft Speech SDK should have been installed during the Dialog Designer installation process. See Configuring the Microsoft Speech SDK for Microphone Input.

To simulate spoken inputs with a microphone:

During simulation, the AAS prompts for a response in which a spoken response is an option. To indicate that the AAS is waiting for a spoken response, the Waiting ASR indicator in the Input tab turns green.

With a microphone attached to your computer and turned on, speak the response.

When the AAS recognizes the input, Dialog Designer automatically moves on to the next node of the call flow. If the AAS does not recognize the input, the application throws a No Match event and the AAS responds with the appropriate No Match prompt.

You can also simulate barge-in using AAS. By default the barge-in feature of the AAS is disabled, but you can enable it be checking the Enable Barge-in detection option (Click Windows > Preferences > Dialog Designer > Avaya Application Simulator preference screen).

Note:

It is recommended to use a headset when running AAS with barge-in enabled, since a standard PC microphone can easily pick up sounds from the PC speakers.

Simulating Spoken Inputs without a Microphone

To simulate spoken inputs without a microphone:

You need not have a microphone to simulate ASR inputs to an application. The AAS provides a mechanism to type the response you want to use for simulated ASR input and submit it in place of input from a microphone. Note that the AAS does not evaluate the ASR response to see if it is valid. The AAS assumes that whatever ASR response it receives in this manner is valid and treats it accordingly. This fact is one reason it is better to simulate with a microphone, if possible.

During simulation, the AAS prompts for a response in which a spoken response is an option. To indicate that the AAS is waiting for a spoken response, the Waiting ASR indicator in the Input tab turns green.

In the Recognition field, type the input that you want to simulate.

(Optional) if you want to simulate the confidence level of the ASR server response, enter in the Confidence field a number between 0.0 and 1.0.

Click Send ASR.