[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 14:11:44 CDT 2010
A NOTE has been added to this issue.
======================================================================
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: feedback
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:
======================================================================
Date Submitted: 2010-03-23 22:20 CDT
Last Modified: 2010-03-24 14:11 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.
======================================================================
----------------------------------------------------------------------
(0119851) whardier (reporter) - 2010-03-24 14:11
https://issues.asterisk.org/view.php?id=17089#c119851
----------------------------------------------------------------------
There are no errors because that is ligitimate dialplan. Similar to how
[stdExten] works off of priority 50000.
Here's another scenario that might explain the whys involved with handling
dialplan this way (similarly to how stdExten works)
[test-inbound]
exten => 1,1,Goto(test-menu-anchorage,s,1) ; Go through the anchorage
context first and do something
exten => 2,1,Goto(test-menu-anchorage,s,1)
exten => 3,1,Goto(test-menu-wasilla,s,1) ; Go through wasilla context
first and do something
exten => 4,1,Goto(test-menu,s,start) ; Go directly because I want too for
some reason
[test-menu]
exten => s,50000(start),NoOp(test1) ; Offset this so that we can be
included
exten => s,n,Background(silence/10)
exten => s,n,Hangup()
exten => _00xx,1,NoOp(Entered ${EXTEN})
exten => 0,1,NoOp(Entered ${EXTEN})
exten => 1,1,NoOp(Entered ${EXTEN})
exten => 2,1,NoOp(Entered ${EXTEN})
exten => 3,1,NoOp(Entered ${EXTEN})
exten => 4,1,NoOp(Entered ${EXTEN})
exten => 5,1,NoOp(Entered ${EXTEN})
[test-menu-anchorage]
include => test-menu
exten => s,1,NoOp(Do something here)
exten => s,n,Goto(start)
exten => 3474,1,NoOp(Do stuff)
[test-menu-wasilla]
include => test-menu
exten => s,1,NoOp(Do something else here)
exten => s,n,Goto(start)
exten => 5787,1,NoOp(Do stuff)
Issue History
Date Modified Username Field Change
======================================================================
2010-03-24 14:11 whardier Note Added: 0119851
======================================================================
More information about the asterisk-bugs
mailing list