[asterisk-bugs] [JIRA] Created: (ASTERISK-20441) AEL jump to wrong ext after switch-statement is completed (dialplan pattern)

[Johan Wilfer (JIRA)]

AEL jump to wrong ext after switch-statement is completed (dialplan pattern)
----------------------------------------------------------------------------

                 Key: ASTERISK-20441
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20441
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: PBX/pbx_ael
    Affects Versions: 1.8.15.1, 1.8.17.0
         Environment: Tested with Asterisk 1.8.15.1 and 1.8.17.0-rc1
            Reporter: Johan Wilfer
            Severity: Minor


After a switch-statement in ael, the switch uses a goto to the wrong ext. 

Consider this dialplan:
{noformat}
context test {
 _X. => {
          Noop(Before switch statement, exten: ${EXTEN});
          switch (${EXTEN}) {
            case 12345:
              Noop(In switch statement, case 12345);
              break;
          }

          Noop(After switch statement, exten: ${EXTEN});
        }
}
{noformat}

Results in the following:
{noformat}
    -- Executing [12345 at test:1] MSet("SIP/trunk-00000011", "~~EXTEN~~=12345") in new stack
    -- Executing [12345 at test:2] NoOp("SIP/trunk-00000011", "Before switch statement, exten: 12345") in new stack
    -- Executing [12345 at test:3] Goto("SIP/trunk-00000011", "sw_1677_12345,10") in new stack
    -- Goto (test,sw_1677_12345,10)
    -- Executing [sw_1677_12345 at test:10] NoOp("SIP/trunk-00000011", "In switch statement, case 12345") in new stack
    -- Executing [sw_1677_12345 at test:11] Goto("SIP/trunk-00000011", "_X.,4") in new stack
    -- Goto (test,_X.,4)
    -- Executing [_X. at test:4] NoOp("SIP/trunk-00000011", "Finish switch_test_1677") in new stack
    -- Executing [_X. at test:5] NoOp("SIP/trunk-00000011", "After switch statement, exten: 12345") in new stack
    -- Auto fallthrough, channel 'SIP/trunk-00000011' status is 'UNKNOWN'
{noformat}

Havn't seen any bad effects yet thought. But the goto should have jumped to 12345,4 insted of _X.,4

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