[asterisk-bugs] [JIRA] Commented: (ASTERISK-20313) GotoIf redirection to label not working in included extension

[Noah Engelberth (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196391#comment-196391 ] 

Noah Engelberth commented on ASTERISK-20313:
--------------------------------------------

At a minimum, it's pretty inconsistent behavior.  Assume you have a context [foo] that is where your call has come into (because the endpoint dials to it or whatever).  [foo] includes [bar], which has the extension you actually are dialing.  If there's a Goto in the extension in [bar] that uses a relative label, and [foo] does NOT have an active DUNDi switch, the Goto works.  However, if the [foo] context (where the call is executing) does have a DUNDi switch, the Goto a relative label within an extension in the included context [bar] doesn't work.

In addition, the same behavior occurs if you try to Goto(foo,${EXTEN},label) from context [blah].  If there is no DUNDi switch in [foo], the call falls through to the included [bar],${EXTEN},label.  If there is an active DUNDi switch (reachable or otherwise -- all that matters is that pbx_dundi.so is loaded and the DUNDi switch is active in the dialplan, as I have been doing this on a test box with no DUNDi peers defined and it still "fails"), then the call sent to [foo],${EXTEN},label fails with the error reported -- "Priority 'notloggedin' must be a number > 0, or a valid label".  

I found it pretty jarring to have an otherwise working dialplan break simply because I turned DUNDi on.

> GotoIf redirection to label not working in included extension
> -------------------------------------------------------------
>
>                 Key: ASTERISK-20313
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20313
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/General, Core/General
>    Affects Versions: SVN, 10.4.2, 11.0.0-beta1
>         Environment: CentOS 6.3 VM on CentOS 6.2 KVM cluster; CentOS 6.3 on Dell Optiplex 790
>            Reporter: Noah Engelberth
>            Severity: Minor
>         Attachments: dialplan.txt
>
>
> I run a hotdesking system based on the example from Asterisk: The Definitive Guide.  Calls come into the [hotdesk] context, which verifies the phone has a logged in user and sends the call to users,${EXTEN},1 if there is a user logged in.  The [users] context then includes several other contexts for internal/external call handling, as attached.  In both Asterisk 10 and Asterisk 11, the GotoIf does not work under the circumstances shown, giving me the following error and hanging up the call:
> [Aug 23 15:17:35] WARNING[3558][C-00000565]: pbx.c:11799 pbx_parseable_goto: Priority 'notloggedin' must be a number > 0, or valid label
> I can work around the issue with any of the following:
> -	Change the GotoIf to point to internal,${EXTEN},notloggedin
> -	Change the GotoIf to point to 9
> -	Comment out the DUNDi switch in [users]
> -	Unload the pbx_dundi.so module
> In the latter two cases, the call redirects to the notloggedin priority label within [internal],${EXTEN} without me changing the GotoIf - as long as the DUNDi switch is not active in [users].  With the DUNDi switch active, I get the warning message above and the call hangs up.
> I have tried with several other words for the label -- no label works.  I've had the target priority at different points in the extension, ranging from 9 to 15 -- if I call it numerically or as a full context,extension,priority it works, but just calling the priority as a label does not as long as the DUNDi switch is active in the original context the call is operating out of ([users]).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira