Cisco Cisco Customer Voice Portal Downloads Guia Do Programador
V
OICE
E
LEMENT
:
F
ORM
_W
ITH
_C
ONFIRM
E
LEMENT
S
PECIFICATIONS FOR
C
ISCO
U
NIFIED
C
USTOMER
V
OICE
P
ORTAL
R
ELEASE
4.0(1)
36
Form_With_Confirm
The Form_With_Confirm voice element is used to capture and confirm input from the caller, based on application designer-specified
grammars. The valid caller inputs can be specified either directly in the voice element settings (which will create an inline grammar)
or with external grammar files. Information returned by the grammar are saved in element data that can then be analyzed by
developer-defined components. A Form_With_Confirm voice element can be configured to listen for voice input only, DTMF input
only, or both voice and DTMF input. In short, the Form_With_Confirm element is the most flexible of all Unified CVP elements that
have confirmation menus as it allows almost any custom information to be captured and confirmed without requiring a separate voice
element. If a Unified CVP voice element does not capture and confirm certain information as desired, one can always use a
Form_With_Confirm element first, before embarking on constructing a custom voice element.
grammars. The valid caller inputs can be specified either directly in the voice element settings (which will create an inline grammar)
or with external grammar files. Information returned by the grammar are saved in element data that can then be analyzed by
developer-defined components. A Form_With_Confirm voice element can be configured to listen for voice input only, DTMF input
only, or both voice and DTMF input. In short, the Form_With_Confirm element is the most flexible of all Unified CVP elements that
have confirmation menus as it allows almost any custom information to be captured and confirmed without requiring a separate voice
element. If a Unified CVP voice element does not capture and confirm certain information as desired, one can always use a
Form_With_Confirm element first, before embarking on constructing a custom voice element.
The Form_With_Confirm element provides support for custom control over the VoiceXML code generation. For example, the
developer can decide what name to use for the VoiceXML field, whether or not to include a field-level slot attribute and how to name
the slot attribute. The element also supports separate options for activating help prompts and the ability to set modality for Form.
developer can decide what name to use for the VoiceXML field, whether or not to include a field-level slot attribute and how to name
the slot attribute. The element also supports separate options for activating help prompts and the ability to set modality for Form.
Multiple DTMF and speech external grammars can be referenced within a single Form_With_Confirm element, and the developer has
the ability to specify grammar weights for speech grammars and set MIME types for both speech and DTMF grammars. Additionally,
the Form_With_Confirm element can be used to capture multiple slots, and the developer can specify for which slot(s) they want the
recognition values stored as element data. Advanced n-best processing can be enabled, and standard n-best results are stored in
element data and the activity log.
the ability to specify grammar weights for speech grammars and set MIME types for both speech and DTMF grammars. Additionally,
the Form_With_Confirm element can be used to capture multiple slots, and the developer can specify for which slot(s) they want the
recognition values stored as element data. Advanced n-best processing can be enabled, and standard n-best results are stored in
element data and the activity log.
Settings
Name (Label)
Type
Req’d
Single
setting
value
Substitution
allowed
Default
Notes
inputmode
(Input Mode)
(Input Mode)
string
enum
enum
Yes true false
both
The type of entry allowed for input. Possible values are: voice
| dtmf | both.
| dtmf | both.
noinput_timeout
(Noinput Timeout)
(Noinput Timeout)
string
Yes true true
5s
The maximum time length allowed for silence or no keypress
before a noinput event is thrown. Possible values are standard
time designations including both a non-negative number and a
time unit, for example, 3s (for seconds) or 300ms (for
milliseconds). Default = 5s.
before a noinput event is thrown. Possible values are standard
time designations including both a non-negative number and a
time unit, for example, 3s (for seconds) or 300ms (for
milliseconds). Default = 5s.
form_max_noinput_count
(Form Max NoInput)
(Form Max NoInput)
int • 0
Yes true true
3
The maximum number of noinput events allowed during form
input capture. 0 = infinite noinputs allowed.
input capture. 0 = infinite noinputs allowed.