[asterisk-bugs] [Asterisk 0019168]: http://www.freepbx.org/forum/freepbx/beta-program-issues/t-timeout-is-not-honored-by-ivr
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Apr 21 22:06:29 CDT 2011
The following issue requires your FEEDBACK.
======================================================================
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: feedback
Asterisk Version: SVN
JIRA:
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-04-21 22:06 CDT
======================================================================
Summary:
http://www.freepbx.org/forum/freepbx/beta-program-issues/t-timeout-is-not-honored-by-ivr
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
======================================================================
----------------------------------------------------------------------
(0134026) pabelanger (administrator) - 2011-04-21 22:06
https://issues.asterisk.org/view.php?id=19168#c134026
----------------------------------------------------------------------
Debugging deadlocks:
Please select DEBUG_THREADS and DONT_OPTIMIZE in the Compiler Flags
section of menuselect. Recompile and install Asterisk (i.e. make install)
This will then give you the console command:
core show locks
When the symptoms of the deadlock present themselves again, please provide
output of the deadlock via:
# asterisk -rx "core show locks" | tee /tmp/core-show-locks.txt
# gdb -se "asterisk" <pid of asterisk> | tee /tmp/backtrace.txt
gdb> bt
gdb> bt full
gdb> thread apply all bt
Then attach the core-show-locks.txt and backtrace.txt files to this issue.
Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2011-04-21 22:06 pabelanger Note Added: 0134026
2011-04-21 22:06 pabelanger Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list