Show TOC

Background documentationVoice Entities Locate this document in the navigation structure

 

Elements

Voice Kit elements are the building blocks of a voice application. The following table lists the voice elements and their use:

Element

Description

Speak Element

Allows audio prompts to be played to the caller.

The audio prompts are either pre-recorded audio files or text to speech converted using the Text To Speech component of the gateway.

Listen Element

Allows the interactions of the caller to be captured.

This includes the definition of a speech recognition grammar set (built-in or user-specified), handling of the speech recognition result, and a set of utterances related to the interaction.

Route Element

Allows the flow of the dialog to branch based on the value of an expression

Record Element

Makes an audio recording of the caller's voice that can be stored and played back later. These recordings can be made available to other applications using a URL

Transfer Element

Passes control (transfers the call) to another telephone number or a URL

Process Element

Performs runtime actions such as assigning variables or managing tables

VoiceXML Element

Allows you to insert VoiceXML code in the application.

This provides a way of bypassing any limitations for the functions of NetWeaver Voice or of making use of non-standard capabilities of a voice gateway.

Log Element

Stores information in one of the several available logs. The logs available are the Business Information Warehouse (BI) database, the system log, and the platform log

Note Note

The Elements of a voice model have a Reset button on the Settings window. The Reset button allows you to cancel the changes you have made to the fields.

End of the note.
Component

Entity

Description

Voice Component

A component is a reusable voice entity that can be published in a voice application. You can have a component within a component in a voice application.
Connectors

Connectors are the entities that you use to define the start and end points of your model. The following table lists the set of voice connectors and their use:

Entity

Description

Start Point

Defines the start of a voice component or an application execution.

There is always one and only one start point in a voice application. Since a voice component cannot be published independently it need not have a start point.

End Point

Defines the end of a voice component or an application execution.

There can be no, one, or more end points, depending on the flow in a voice application.

When there is no end point in a voice application it could be part of any of its components.
Event Signals

Event Signals are the entities that you use to indicate a transfer of control to and from other events. The following table lists the set of voice event signals and their use:

Entity

Description

Signal In

Acts as a target to catch a particular event and transfer flow to the element connected to its out port

Signal Out

Causes an event to be triggered. The event can then be caught somewhere else in the application, either by a Signal In or in a defined event handler in any parent scope