[asterisk-bugs] [Asterisk 0017089]: Background behaves strangely[t when priority 1 is not available in current extension.
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Mar 24 08:55:58 CDT 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=17089
======================================================================
Reported By: whardier
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17089
Category: Core/PBX
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Asterisk Version: 1.6.2.6
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: no change required
Fixed in Version:
======================================================================
Date Submitted: 2010-03-23 22:20 CDT
Last Modified: 2010-03-24 08:55 CDT
======================================================================
Summary: Background behaves strangely[t when priority 1 is
not available in current extension.
Description:
Apparently whatever extension lookup method is being used by BackGround
fails when the extension calling BackGround does not have priority 1 in the
current context. I discovered this when including an IVR menu into another
context using a 50000 offset to extension 's' and a named priority. See
additional information for a quick sample.
In the example below, if a caller is sent to Goto(tree-dish-AK-ANC,s,1)
the extension detection fails with:
[Mar 23 19:17:41] -- Sent into invalid extension 's' in context
'tree-dish-common' on SIP/0011-Sales-0000001c
[Mar 23 19:17:41] -- Executing [i at tree-dish-common:1]
Gosub("SIP/0011-Sales-0000001c", "s,common") in new stack
If I attempt to dial a 4 digit extension starting with 0 when a '0'
extension exists. Something is 'wonky' if I can get technical with you
all.
Previously [tree-dish-AK-ANC] included [tree-dish-common] and simply went
to the named priority at priority 50000 via a local Goto which may have
worked.. untested.
I can see how some users may want to jump into a named priority in another
context and use DTMF detection of some kind. If the extension does not
have priority 1 this will fail.
======================================================================
----------------------------------------------------------------------
(0119796) lmadsen (administrator) - 2010-03-24 08:55
https://issues.asterisk.org/view.php?id=17089#c119796
----------------------------------------------------------------------
This is not a bug in Asterisk, but rather a bug in your dialplan:
[tree-dish-AK-ANC]
exten => s,1,Set(locale=AK-ANC)
; exten => s,n,Goto(tree-dish-common,menu,1)
exten => s,n,Goto(tree-dish-common,s,makeitso)
exten => _.,1,Set(locale=AK-ANC)
exten => _.,n,Goto(tree-dish-common,${EXTEN},1)
In this case, if you do Goto(tree-dish-AK-ANC,s,1) your pattern match of
_. will match the 's' extension, which then does the
Goto(tree-dish-common,s,1) which of course doesn't exist because you don't
have s,1 in [tree-dish-common].
Don't use the _. pattern match, and then you won't have the problem. The
_. pattern match takes precedent over everything.
Issue History
Date Modified Username Field Change
======================================================================
2010-03-24 08:55 lmadsen Note Added: 0119796
2010-03-24 08:55 lmadsen Status new => closed
2010-03-24 08:55 lmadsen Resolution open => no change
required
======================================================================
More information about the asterisk-bugs
mailing list