[asterisk-bugs] [Asterisk 0017626]: [patch] Dialplan execution stops after awhile on an attended transfer by the calling party (with use of Dial 'g' option)
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jul 13 01:55:10 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17626
======================================================================
Reported By: ramonpeek
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17626
Category: PBX/General
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: 1.4.33
JIRA: SWP-1844
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-07-12 06:42 CDT
Last Modified: 2010-07-13 01:55 CDT
======================================================================
Summary: [patch] Dialplan execution stops after awhile on an
attended transfer by the calling party (with use of Dial 'g' option)
Description:
Dialplan execution stops after awhile on an attended transfer by the
calling party (with use of Dial() command 'g' option)
This applies to systems with large dialplans (which we use), small
dialplans do not seem to encounter much problems, due to the delay in SIP
messaging.
If traced, you can see the after Asterisk receives a SIP BYE message, the
dialplan execution is immediately stopped even though there are other
priorities to evaluate in the dialplan.
SEE STEPS TO REPRODUCE (in advanced view mode)
======================================================================
----------------------------------------------------------------------
(0124526) ramonpeek (reporter) - 2010-07-13 01:55
https://issues.asterisk.org/view.php?id=17626#c124526
----------------------------------------------------------------------
It appears my machine just got a lot quicker (If I knew how, I would have
sold my knowledge to Intel ;-) )
Anyway, it explains why I wasn't able to reproduce the problem.
Simply increasing the While loop to count until 2000 does the trick or
like I did, include a command that takes a little longer to execute. Like
this ODBC call:
exten = s,n,Set(RESULT=${ODBC_CST(SELECT callerid FROM device WHERE id=
'\1'\)})
Issue History
Date Modified Username Field Change
======================================================================
2010-07-13 01:55 ramonpeek Note Added: 0124526
======================================================================
More information about the asterisk-bugs
mailing list