[asterisk-bugs] [Asterisk 0014011]: [patch] Incorrect jump to extension
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu May 7 18:44:21 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14011
======================================================================
Reported By: dveiga
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 14011
Category: Applications/General
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Asterisk Version: 1.6.1-beta3
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 160441
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2008-12-02 20:46 CST
Last Modified: 2009-05-07 18:44 CDT
======================================================================
Summary: [patch] Incorrect jump to extension
Description:
When calling Background() application, function pbx_builtin_background() is
called. Inside it, I believe there's a bug when comparing the channel
context with the one used as a parameter. Where it says "if (args.context
!= chan->context && res)" it should say "if ( strcmp(args.context,
chan->context) && res)".
I just explained it because in this simple case I think its easier than
sending a patch, but I can send the patch file if it helps.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0014940 Background application executed in post...
======================================================================
----------------------------------------------------------------------
(0104416) svnbot (reporter) - 2009-05-07 18:44
http://bugs.digium.com/view.php?id=14011#c104416
----------------------------------------------------------------------
Repository: asterisk
Revision: 193122
_U branches/1.6.1/
U branches/1.6.1/main/pbx.c
------------------------------------------------------------------------
r193122 | tilghman | 2009-05-07 18:44:20 -0500 (Thu, 07 May 2009) | 33
lines
Merged revisions 193120 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk
................
r193120 | tilghman | 2009-05-07 18:42:28 -0500 (Thu, 07 May 2009) | 26
lines
Merged revisions 193119 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r193119 | tilghman | 2009-05-07 18:41:11 -0500 (Thu, 07 May 2009) | 19
lines
Fix Background within a Macro for FreePBX.
If the single digit DTMF is an extension in the specified context,
then
go there and signal no DTMF. Otherwise, we should exit with that
DTMF.
If we're in Macro, we'll exit and seek that DTMF as the beginning of
an
extension in the Macro's calling context. If we're not in Macro, then
we'll simply seek that extension in the calling context. Previously,
someone complained about the behavior as it related to the interior of
a
Gosub routine, and the fix (http://bugs.digium.com/view.php?id=14011)
inadvertently broke FreePBX
(http://bugs.digium.com/view.php?id=14940). This change should fix both of
these situations, but with
the
possible incompatibility that if a single digit extension does not
exist
(but a longer extension COULD have matched), it would have previously
gone immediately to the "i" extension, but will now need to wait for a
timeout.
(closes issue http://bugs.digium.com/view.php?id=14940)
Reported by: p_lindheimer
Patches:
20090420__bug14940.diff.txt uploaded by tilghman (license 14)
Tested by: p_lindheimer
........
................
------------------------------------------------------------------------
http://svn.digium.com/view/asterisk?view=rev&revision=193122
Issue History
Date Modified Username Field Change
======================================================================
2009-05-07 18:44 svnbot Checkin
2009-05-07 18:44 svnbot Note Added: 0104416
======================================================================
More information about the asterisk-bugs
mailing list