RE: nothing on the spec to clear dtmf buffer ?

Yeah, on our platform there is an extension property that controls how far back in time you should look in the dtmf buffer.  If you set it to 0 you get no buffer, but you can also control should you look back just 2 seconds or more like 20 depending on application state.

>From a VXML specification point of view, I think the common case the specification is correctly addressing is that dtmf keys should bargein to the next bargeable prompt as the usual case is that the non-bargeable prompt is a legal message or an ad and a power user knows the first few keys they want to press to navigate the call tree.  In the case that you want to prevent them from doing this (like you changed your menus) you can make the new warning prompt non-bargeable as well.  

-----Original Message-----
From: www-voice-request@w3.org [mailto:www-voice-request@w3.org] On Behalf Of Michael Glover
Sent: Thursday, October 20, 2011 8:18 AM
To: www-voice@w3.org
Subject: Re: nothing on the spec to clear dtmf buffer ?

I agree. It seems like a simple thing that should be easy to do.

Perhaps the spirit of the specification expects that if you didn't want to interrupt the form with previous digits, you would play one of those non-bargeable "please listen to the menu, as our options have recently changed" prompts that we all love to hear. 

My personal opinion of the best way to do it would be with a <property> specified within the specification. Something like "cleardtmfbuffer".
Perhaps in VXML 3.0 something like this will be available.


Michael Glover
Software Engineer
Interact, Inc.


-----Original Message-----
From: Stephane Boyera <boyera@w3.org>
To: Michael Glover <GloverM@iivip.com>
Cc: www-voice@w3.org
Date: Thu, 20 Oct 2011 16:51:56 +0200
Subject: Re: nothing on the spec to clear dtmf buffer ?

> Hi Michael, and Shane
> 
> Thank you very much for your answers.
> 
> first of all, i'm not happy with a platform specific attribute, so 
> that's why i sent this email. (if W3C staff write non-standard code 
> where do we go ? :) )
> 
> Then, i don't want to turn barge-in to false for my second prompt. I 
> just want to let the user know that he is entering a new prompt. He 
> may decide or not to skip it, but he should be aware of it.
> 
> If i understand correctly what you are saying, just adding something 
> like
> 
> <form id="eat">
> <block>
> <prompt bargein="false" cond="true">
>            <audio src="silence.wav" /> </prompt>
>           <goto next="#form2" />
> </block>
> </form>
> 
> which would play a 1s silence is enough to clear the dtmf buffer ?
> 
> I will try.
> 
> For now, my solution was not that different
> 
> <form id="eat">
> <field name="barge" type="digits">
> <property name="interdigittimeout" value="1s"/> <prompt bargein="true" 
> cond="true" timeout="0s"> </prompt>
> 	<noinput>
>          	<goto next="#form2" />
> 	</noinput>
> 	<filled>
>          	<goto next="#form2" />
> 	</filled>
> </field>
> </form>
> 
> even if a bit more complex.
> 
> In all case, it seems a bit ugly to me to have to add specific piece 
> of codes to do something which seems quite natural.
> 
> Anyway, i've all the info i needed: a nicer solution, and the 
> confirmation that there is no other option.
> 
> thanks again !
> Steph
> -- 
> Stephane Boyera		stephane@w3.org
> W3C				+33 (0)6 73 84 87 27
> BP 93				fax: +33 (0) 4 92 38 78 22
> F-06902 Sophia Antipolis Cedex,		
> France
>

Received on Friday, 21 October 2011 02:26:14 UTC