<html><head></head><body bgcolor="#FFFFFF"><div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000">Try playing with real users. They *always* type ahead by their second or <br>third call to the same IVR. Handling type-ahead well - accepting the <br>string of entered digits, skipping the playback of prompts so you don't <br>slow things down, etc. - is one of the key tests of a good IVR.</font></div></blockquote><div><br></div>I'm guilty of this. Hate sitting through a long message that I already know word for word. <br><br>Steve on iPhone</div><div><br>On 25 Oct 2011, at 02:01, Steve Underwood <<a href="mailto:steveu@coppice.org">steveu@coppice.org</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><span>On 10/25/2011 12:07 AM, Antonio Teixeira wrote:</span><br><blockquote type="cite"><span>Well guys it depends on your application , generally i solve this </span><br></blockquote><blockquote type="cite"><span>with regexp , a buffer and a way to clear the buffer of </span><br></blockquote><blockquote type="cite"><span>invalid/duplicated data I'm extending it to support with min delay </span><br></blockquote><blockquote type="cite"><span>between keys.</span><br></blockquote><blockquote type="cite"><span>This is not as hard as you think when using min/max :) and your data </span><br></blockquote><blockquote type="cite"><span>is predictable :)</span><br></blockquote><span>Is a properly engineered solution so unattainable that such guesswork is </span><br><span>the only solution?</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Also in ivr menus humans don't generally guess whats the next menu so </span><br></blockquote><blockquote type="cite"><span>if len(dtmf) > 1: drop ...</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I play with this in our test environment not in our production and it </span><br></blockquote><blockquote type="cite"><span>works :)</span><br></blockquote><span>Try playing with real users. They *always* type ahead by their second or </span><br><span>third call to the same IVR. Handling type-ahead well - accepting the </span><br><span>string of entered digits, skipping the playback of prompts so you don't </span><br><span>slow things down, etc. - is one of the key tests of a good IVR.</span><br><span></span><br><span>Steve</span><br><span></span><br><span></span><br><span></span><br><span>FreeSWITCH-users mailing list</span><br><span><a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a></span><br><span><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a></span><br><span>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users</span><br><span><a href="http://www.freeswitch.org">http://www.freeswitch.org</a></span><br></div></blockquote></body></html>