[asterisk-bugs] [Asterisk 0018146]: ast_app_dtget inconsistency

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18146 
====================================================================== 
Reported By:                dimas
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18146
Category:                   Core/General
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.13 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-16 09:13 CDT
Last Modified:              2010-10-17 17:31 CDT
====================================================================== 
Summary:                    ast_app_dtget inconsistency
Description: 
I noticed strange thing in the code decided to share. 1.6.2.13, main/app.c,
ast_app_dtget function at the very beginning it tries to configure the
timeout unless it is specified:

        if (!timeout && chan->pbx) {
                timeout = chan->pbx->dtimeoutms / 1000.0;
        } else if (!timeout) {
                timeout = 5;
        }

Both branches indicate  the final value for timeout is in seconds. However
I believe ast_waitfordigit accepts timeout in milliseconds.
And as I see when ast_app_dtget is called by builtin_atxfer, the timeout
passed is also in ms. So I guess the code above may be wrong.

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

---------------------------------------------------------------------- 
 (0128137) dimas (reporter) - 2010-10-17 17:31
 https://issues.asterisk.org/view.php?id=18146#c128137 
---------------------------------------------------------------------- 
When you say "you are right, the timeout should not be in sec rather than
ms" do you actually mean the opposite? :)

Just to be clear - the issue I reported does not cause anything in my
setup. Because yes, it is not triggered. So I'm not reporting something
which actually causes problem but rather just something which _looks_
wrong.

Your patch looks fine to me. But I see no point in testing because again -
I do not have an issue on the first place. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-17 17:31 dimas          Note Added: 0128137                          
======================================================================