[Asterisk-bugs] [Asterisk 0010084]: Read application buffers input DTMF tones

[noreply at bugs.diguim.com]

email_notification_title_for_action_bugnote_submitted 
====================================================================== 
http://bugs.digium.com/view.php?id=10084 
====================================================================== 
Reported By:                rushowr
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10084
Category:                   Applications/app_read
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.5 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        No 
====================================================================== 
Date Submitted:             06-28-2007 15:10 CDT
Last Modified:              06-29-2007 07:32 CDT
====================================================================== 
Summary:                    Read application buffers input DTMF tones
Description: 
The Read application is used to take the user's input and place it into a
variable but sometimes if it does not properly receive the DTMF tone(s), it
buffers the input and places it into the NEXT Read call's input buffer and
prepends it to the variable there.

One major thing we've noticed is that it's always the last digit of the
input.
For example, we get the uer's language selection and for some reason the
server does not get the entered digit "1" as show below:

-------------
--Executing[s at select_lang:3] BackGround("SIP/[provider name
removed]-08218e30", "prepaid-lang_select")
<SIP/[provider name removed]-08218e30> Playing 'prepaid-lang_select'
(language 'en')
--Executing[s at select_lang:4] Read("SIP/[provider name removed]-08218e30",
"lang_input||1")
Accepting a maximum of 1 digits.
User entered nothing.
-------------

Our dialpan tests for empty input and loops back to get it again. This
time, the first 1 is "received"  and the new "1" is buffered:

-------------
--Executing[s at select_lang:5] GotoIf("SIP/[provider name
removed]-08218e30", "1?6:13")
Goto (select_lang,s,6)
--Executing[s at select_lang:6] GotoIf("SIP/[provider name
removed]-08218e30", "1?7:10")
Goto (select_lang,s,7)
--Executing[s at select_lang:7] Set("SIP/[provider name removed]-08218e30",
"loop=2")
--Executing[s at select_lang:8] Goto("SIP/[provider name removed]-08218e30",
"getinput")
Goto (select_lang,s,3)
--Executing[s at select_lang:3] BackGround("SIP/[provider name
removed]-08218e30", "prepaid-lang_select")
<SIP/[provider name removed]-08218e30> Playing 'prepaid-lang_select'
(language 'en')
--Executing[s at select_lang:4] Read("SIP/[provider name removed]-08218e30",
"lang_input||1")
Accepting a maximum of 1 digits.
User entered '1'
-------------

This time, since there's a language selected, we set the language (no need
to show this), and then move on to get the pin number. This is where we can
really see the error, since the pin entered was 222333444555, but Read sees
122233344455:

-------------
--Executing[sw-5-callback at authentication:8] BackGround("SIP/[provider name
removed]-08218e30", "prepaid-enter-pin")
<SIP/[provider name removed]-08218e30> Playing 'prepaid-enter-pin'
(language 'en')
--Executing[sw-5-callback at authentication:9] Read("SIP/[provider name
removed]-08218e30", "pin||14")
Accepting a maximum of 14 digits.
User entered '1222333444555'
-------------

The next executions are omitted because they pertain to the database
queries used to determine if the pin is correct, which it is not. We then
loop back to try again. Unfortunately, the input is ALWAYS wrong because
the last digit of the previous input keeps getting prepended as shown
above. 


====================================================================== 

---------------------------------------------------------------------- 
 rushowr - 06-29-07 07:32  
---------------------------------------------------------------------- 
Hey file! I thought you might be the one to get this report. This bug and
report http://bugs.digium.com/view.php?id=9905 might be linked :)

I'll enable DTMF logging (sorry, I had forgotten that it could be done)
and report  to you the results.

Here's the sip configuration, minus passwords. This is the same sip.conf
from bug http://bugs.digium.com/view.php?id=9905. We've made some small changes.

[general]

rfc2833compensate=yes
context=deadly
bindport=5060	
bindaddr=0.0.0.0
pedantic=yes			
maxexpiry=3600			
defaultexpiry=3600	
disallow=all			
allow=ilbc
allow=alaw
allow=ulaw
allow=gsm
language=en
relaxdtmf=yes			
rtptimeout=60
rtpholdtimeout=300		
dtmfmode = rfc2833
rfc2833compensate=yes


[provider name removed]
type=peer
username=25811
fromuser=25811
secret=**password removed**
disallow=all
allow=gsm
allow=ilbc
host=**host name removed** 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-29-07 07:32  rushowr        Note Added: 0065899                          
======================================================================