Ok but in our case its not the case anyway , people don't like to comeback to our ivr's ....<br><br>So regarding the initial topic getting DTMF/RTP Events from the main trunk :)<br><br><br><div class="gmail_quote">
2011/10/25 Steve Underwood <span dir="ltr"><<a href="mailto:steveu@coppice.org">steveu@coppice.org</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On 10/25/2011 12:07 AM, Antonio Teixeira wrote:<br>
> Well guys it depends on your application , generally i solve this<br>
> with regexp , a buffer and a way to clear the buffer of<br>
> invalid/duplicated data I'm extending it to support with min delay<br>
> between keys.<br>
> This is not as hard as you think when using min/max :) and your data<br>
> is predictable :)<br>
Is a properly engineered solution so unattainable that such guesswork is<br>
the only solution?<br>
><br>
> Also in ivr menus humans don't generally guess whats the next menu so<br>
> if len(dtmf) > 1: drop ...<br>
><br>
> I play with this in our test environment not in our production and it<br>
> works :)<br>
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.<br>
<br>
Steve<br>
<br>
<br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br>