Type
Template (composite) node
Purpose
The purpose of this node is to prompt a caller for a response and collect that response in the form of a spoken reply or DTMF (touchtone) key presses.
Behavior
When you place this node in the workspace, Dialog Designer automatically creates a variable with the same name. This variable contains the following fields:
The returns from all these variable fields can be used or manipulated later in the
application. For example, if you wanted to ascertain the range of recognized
utterances as received by the ASR server, you might have the contents of the
utterance field written to a database. You can use this information later to refine
and improve the functioning of your application.
- confidence - A number in the range 0.0 to 1.0 that indicates the degree to which the ASR server is confident that it has correctly recognized the spoken response. 0.0 indicates minimum confidence and 1.0 indicates maximum confidence.
- utterance - The raw string of words that the ASR server recognized. The presentation and spelling of these words is platform specific. For example, the ASR server might present the number 530 as "five hundred thirty," "5 hundred 30," or even "530." If DTMF key presses were used, this field contains the string of matched digits.
- inputmode - The mode in which the caller input was provided, either voice or DTMF.
- interpretation - The interpretation, by the ASR server, of the spoken response. This interpretation is determined by the programming of the ASR server itself. This field also contains the tag of the grammar item that the ASR server recognized. The ASR server must be set to interpret the response, including the tag, correctly.
When you want to use the spoken response of a caller to control the flow of the
call, use the interpretation field, rather than the utterance field. Avaya
recommends that you use the interpretation field in this type of conditional
branching situation, because the tag of the grammar item is not language
dependent. This fact means that it does not matter whether the actual utterance
of the caller was "yes," "oui," "ja," or some other language form. If the grammar
tag was set to interpret each of these responses as "true," the interpretation field
maps the response to a value of "true" in each of these cases. Thus, this tag
mapping helps the application to use the response correctly, no matter what form
the caller uttered.
- value - If the ASR server returns a value for the interpretation field, this field contains the same value. If the ASR server does not return a value for the interpretation field, this field contains the value of the utterance field (or other optional fields depending on the Record Utterance and Collect Mark Data properties).
Properties
- Name - Enter a name that reflects the central purpose of the node. Use naming conventions for Java components. See Naming Java Components.
- Comments - Enter any comment you want to add as a reminder or description of the purpose or content of the node. You can leave this field blank.
Dialog Designer uses the text you enter in this property field for the pop-up hint
that appears when your mouse hovers over the node icon in the workspace. If
you leave this blank, Dialog Designer uses the name of the node for the pop-up
hint.
- Record Utterance - (True/False). When true, additional fields are added to the variable that store the recording of the caller's utterance, the size of the recording (in bytes) and the duration of the recording (in milliseconds).
- Collect Mark Data - (True/False). When true, additional fields are added to the variable that store the name of the last Mark encountered by the VoiceXML platform as well as the time elapsed since the mark was processed.
- Location - (Read-only) Displays the location of the node graphic in the workspace.
Default Node Structure (Node Detail Editor Flow)
- Input item - Uses sub-items to indicate:
- What prompt the call flow uses to collect input from the caller (Prompt item).
- What means the call flow uses to collect the input (ASR or DTMF Grammar item).
- How the system functions if the caller does not respond (No Input item, which has its own associated Prompt item).
- Note that this setting overrides any global, or application-level, settings you might have assigned in the AppRoot node. If you prefer to use the global settings, you can delete this item. For more information about global settings, see AppRoot Node Event Handlers.
- How the system functions if the system cannot match the response by the caller with any expected response (No Match item, which has its own associated Prompt item).
- Note that this setting overrides any global, or application-level, settings you might have assigned in the AppRoot node. If you prefer to use the global settings, you can delete this item. For more information about global settings, see AppRoot Node Event Handlers.
- Next item - Indicates which node comes next in the call flow.
Tip: