This document was generated from CDN thread
Created by: null on 15-07-2003 03:38:12 PM
When barge in is set to false for a particular audio group, a DTMF recognition resource is still being requested from the browser. This is causing a licensing issue on our side. What is the best way to turn this off, if possible?
This is with Audium 3.2.2
Subject: RE: False barge in
Replied by: null on 16-07-2003 03:09:45 PM
Hi Joel,
There are several situations where you can turn off bargein. If it is for an audio group that appears within a field, then there is probably nothing you can do about using up the license since that field is listening for DTMF. If you are not listening for DTMF, then it will not use a license.
The second situation is when the audio group either appears in the page by itself (which is the case when you use an Audio voice element), or is the last audio group in a page (such as an "end" audio group in many Audium elements). In these two sitituations, some voice browsers do not provide a way to properly barge into this audio since they are not prompts for a data capture field. So bargein would not even be an option in these two cases. What we did, then, is to create a false field that contains an impossible-to-match DTMF grammar with the noinput timeout set to the minimum. By doing this, we allow bargin to apply to all audio groups, not just the ones that prompt a field.
Now, that DTMF grammar appears in the VoiceXML whether or not the audio group has been selected to be barged in, which seems to be the problem for you; it takes up a dtmf resource event when you don't need it.
Unfortunately, there is no quick solution. What you can do is create your own voice elements that do not use that trick. You can create your own audio-only voice element and then do not configure the Audium elements with "done" audio groups and instead use the new audio element. This would probably cover most cases that use this situation with minimal effort. You may find, however, that you'd have to make additional voice elements.
We are currently looking into how we handle bargein for audio groups and whether we still need to perform this trick or if there are alternatives. I will add this note to our feature tracking system At the least we can eliminate the trick when bargein is turned off.
By the way, while we are on the subject of bargein, there is a known issue with OSB you can see in the knowledge base that prevents speech bragein from ocurring in these same audio groups mentioned. This is because OSB does not allow speech bargein to a field that defines only a DTMF grammar. If we had added a speech grammar to this trick, there would be an undesireable pause while the ASR engine tried to match the utterance, and we did not want that. So, if you make a new audio voice element without this trick, you will be unable to bargein to the audio group at all.
Hope this helps.
