[asterisk-bugs] [Asterisk 0010540]: timeout value should accept floating point numbers

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10540 
====================================================================== 
Reported By:                spendergrass
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   10540
Category:                   Functions/func_timeout
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 89276 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-23-2007 13:27 CDT
Last Modified:              12-21-2007 14:08 CST
====================================================================== 
Summary:                    timeout value should accept floating point numbers
Description: 
Example, setting digit timeout value to 1.5 seconds should be accepted. 
Currently, it rounds down to nearest whole number.
====================================================================== 

---------------------------------------------------------------------- 
 blitzrage - 12-21-07 14:08  
---------------------------------------------------------------------- 
No crash this time around... but a couple of other issues:

    -- Executing [http://bugs.digium.com/view.php?id=123@phones:1]
NoOp("SIP/leifmadsen_desk-106cdc20", "")
in new stack
    -- Executing [http://bugs.digium.com/view.php?id=123@phones:2]
Set("SIP/leifmadsen_desk-106cdc20",
"TIMEOUT(digit)=1.5") in new stack
    -- Digit timeout set to 1500
    -- Executing [http://bugs.digium.com/view.php?id=123@phones:3]
Set("SIP/leifmadsen_desk-106cdc20",
"TIMEOUT(response)=5.2") in new stack
    -- Response timeout set to 5200
    -- Executing [http://bugs.digium.com/view.php?id=123@phones:4]
Set("SIP/leifmadsen_desk-106cdc20",
"TIMEOUT(absolute)=3.5") in new stack
Channel will hangup at 1969-12-31 19:00:03.500 EST.
    -- Executing [http://bugs.digium.com/view.php?id=123@phones:5]
Verbose("SIP/leifmadsen_desk-106cdc20",
"1,37.1") in new stack
 37.1*CLI> 
    -- Executing [http://bugs.digium.com/view.php?id=123@phones:6]
WaitExten("SIP/leifmadsen_desk-106cdc20",
"") in new stack
    -- Timeout on SIP/leifmadsen_desk-106cdc20, going to 't'
    -- Executing [t at phones:1] Verbose("SIP/leifmadsen_desk-106cdc20",
"1,40.6") in new stack
 40.6
    -- Executing [h at phones:1] Verbose("SIP/leifmadsen_desk-106cdc20",
"1,40.6") in new stack
 40.6

Notice the TIMEOUT(absolute) is not offset correctly. Seems to be
offsetting backwards of 1970-01-01?  At least just in the output there.

The response timeout is set to 5.2, but absolute is set to 3.5, so the
time output of STRFTIME seems to match up that the absolute is what is
causing the hangup, but it's going to 't' instead of 'T', which I believe
(unless I'm remembering wrong) is the desired behaviour. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-21-07 14:08  blitzrage      Note Added: 0075814                          
======================================================================