Combination View Flat View Tree View
Threads [ Previous | Next ]
Introduce bargeintype speech or hotword if bargein is utilised. Currently Audium does not cater for this and its part of the VoiceXML 2.0 Standard.

Should be added with next product release

Hi Karl,

We have entered the ability to define bargeintype as a feature request with an internal id of CSCsh51791. Please refer to this number when checking the status.

Note however, that the bargeintype attribute support is very platform specific. Using "hotword" setting, where only full matches of an active grammar or grammars trigger a barge-in might not be the best solution with the complex grammars. Quoting the Voice XML 2.0 specification, available at http://www.w3.org/TR/voicexml20/#dml4.1.5:

[quote:1cb2120124]
In the case of "speech" bargeintype, the exact meaning of "speech input" is necessarily implementation-dependent, due to the complexity of speech recognition technology. It is expected that the prompt will be stopped as soon as the platform is able to reliably determine that the input is speech. Stopping the prompt as early as possible is desireable because it avoids the "stutter" effect in which a user stops in mid-utterance and re-starts if he does not believe that the system has heard him.
[/quote:1cb2120124]

Note that "speech" bargeintype is defined in teh VoiceXML 2.0 Specification as either speech or DTMF input.

Regards,
Michael

Karl,

One note of clarification. The above comments refer to the [b:ac773d5ce4]bargeintype [/b:ac773d5ce4]as an attribute to [b:ac773d5ce4]bargein [/b:ac773d5ce4] tag.

Currently Call Services allows you to use [b:ac773d5ce4]bargeintype[/b:ac773d5ce4], as a VoiceXML property, defined either with a global scope in the root document or on the page level defined in each voice element.

VoiceXML 2.0 Specification, http://www.w3.org/TR/voicexml20/#dml4.1.5, defines that if the bargeintype is not defined as an attribute, then the value of the property will be used.

Regards,
Michael