[asterisk-bugs] [JIRA] Issue Comment Edited: (ASTERISK-20313) GotoIf redirection to label not working in included extension - document expected behavior on wiki and update sample config

[Noah Engelberth (JIRA)]

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

Noah Engelberth edited comment on ASTERISK-20313 at 9/14/12 11:18 AM:
----------------------------------------------------------------------

The reason I reported it as a bug is that, with the switch active, GotoIf works as desired *if* the jump is a numeric priority only, but *not if* the jump is a labeled priority.

So, my match has already correctly cascaded into an included context, is executing happily there.  Within the extension that it's operating in using the included context, I have a Goto to jump past dialing the user and go straight to voicemail.  If said Goto is in the format Goto(9), it jumps to priority 9 within the included context & extension it's already operating in.  If said Goto is in the format Goto(label), it complains about the label not existing.  If said Goto is in the format Goto(context,extension,label), it works -- although, of course, the call has now been completely moved into the included context, which I'm trying to avoid for the sake of maintainability.

The ONLY time it complains about the label not existing is when there is an active switch in the call's originating context.  With an inactive switch due to unloading DUNDi, or no switch at all, the Goto(label) does correctly jump to priority 9 in the included context & extension the call is operating in.

      was (Author: mlnoah):
    The reason I reported it as a bug is that, with the switch active, GotoIf works as desired -if- the jump is a numeric priority only, but -not if- the jump is a labeled priority.

So, my match has already correctly cascaded into an included context, is executing happily there.  Within the extension that it's operating in using the included context, I have a Goto to jump past dialing the user and go straight to voicemail.  If said Goto is in the format Goto(9), it jumps to priority 9 within the included context & extension it's already operating in.  If said Goto is in the format Goto(label), it complains about the label not existing.  If said Goto is in the format Goto(context,extension,label), it works -- although, of course, the call has now been completely moved into the included context, which I'm trying to avoid for the sake of maintainability.

The ONLY time it complains about the label not existing is when there is an active switch in the call's originating context.  With an inactive switch due to unloading DUNDi, or no switch at all, the Goto(label) does correctly jump to priority 9 in the included context & extension the call is operating in.
  
> GotoIf redirection to label not working in included extension - document expected behavior on wiki and update sample config
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20313
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20313
>             Project: Asterisk
>          Issue Type: Improvement
>      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
>            Assignee: Matt Jordan
>            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