[asterisk-bugs] [Asterisk 0019168]: possible deadlock in WaitExten()

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19168 
====================================================================== 
Reported By:                luckman212
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19168
Category:                   Core/PBX
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-3444 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.8 
SVN Revision (number only!): 314550 
Request Review:              
====================================================================== 
Date Submitted:             2011-04-21 19:49 CDT
Last Modified:              2011-05-10 16:04 CDT
====================================================================== 
Summary:                    possible deadlock in WaitExten()
Description: 
When "WaitExten()" is called from inside the dialplan with no params, e.g.

exten => 123,n,WaitExten(,)

it ignores the default response timeout ($TIMEOUT(response)) and instead
waits indefinitely. Dialplan will continue if user enters DTMF but
otherwise dialplan execution is halted.

see:
http://www.freepbx.org/forum/freepbx/beta-program-issues/t-timeout-is-not-honored-by-ivr

and also: http://pbxinaflash.com/forum/showthread.php?p=63863

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

---------------------------------------------------------------------- 
 (0134747) luckman212 (reporter) - 2011-05-10 16:04
 https://issues.asterisk.org/view.php?id=19168#c134747 
---------------------------------------------------------------------- 
AFAIK this is basically a mis-use of the syntax by FreePBX, so as it's
already been reported to the FreePBX project, and not really an Asterisk
bug, this should probably just be closed out. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-10 16:04 luckman212     Note Added: 0134747                          
======================================================================