[asterisk-bugs] [JIRA] (ASTERISK-22684) extenpatternmatchnew doesn't match some extensions

[Patrick Maille (JIRA)]

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

Patrick Maille edited comment on ASTERISK-22684 at 11/1/13 1:55 PM:
--------------------------------------------------------------------

Ok here is the piece of dialplan:

{noformat}
[dialin]
exten => _NXXNXXXXXX,1,NoOp(Incoming call from ANI: ${CALLERID(ani)} - CID: ${CALLERID(name)} <${CALLERID(num)}> to ${EXTEN})
exten => _NXXNXXXXXX,n,Dial(SIP/${EXTEN},6)                             ;; Dial endpoint with ringtime - default 6 seconds for testing
exten => _NXXNXXXXXX,n,Goto(dialin,${EXTEN}-${DIALSTATUS},1)            ;; Handle Dial Status
exten => _NXXNXXXXXX,n,Hangup(16)                                       ;; Safety net hangup

exten => _NXXNXXXXXX-BUSY,1,NoOp(${EXTEN:0:10} returns BUSY)
exten => _NXXNXXXXXX-BUSY,n,Busy(6)

exten => _NXXNXXXXXX-[N]OA[N]SWER,1,NoOp(${EXTEN:0:10} returns NOANSWER)
exten => _NXXNXXXXXX-[N]OA[N]SWER,n,Hangup(20)
{noformat}

When a call comes in for extension 3456789999, we start at dialin,3456789999,1.
We ring the endpoint for 6 seconds, if it's busy(dnd) we jump to {noformat}dialin,${EXTEN}-${DIALSTATUS},1{noformat} , which in this case would be dialin,3456789999-BUSY,1

But with externpatternmatchnew=yes, we get:
[Nov  1 14:44:09] WARNING[16393][C-00000007]: pbx.c:6390 __ast_pbx_run: Channel 'SIP/TESTINGTRUNK-0000000c' sent to invalid extension but no invalid handler: context,exten,priority=dialin,3456789999-BUSY,1

If I set externpatternmatchnew=no, then it jumps to the right extension (dialin,3456789999-BUSY,1). The same occurs with no-answer and probably other dialstatus conditions.
                
      was (Author: patrickm):
    Ok here is the piece of dialplan:

{noformat}
[dialin]
exten => _NXXNXXXXXX,1,NoOp(Incoming call from ANI: ${CALLERID(ani)} - CID: ${CALLERID(name)} <${CALLERID(num)}> to ${EXTEN})
exten => _NXXNXXXXXX,n,Dial(SIP/${EXTEN},6)                             ;; Dial endpoint with ringtime - default 6 seconds for testing
exten => _NXXNXXXXXX,n,Goto(dialin,${EXTEN}-${DIALSTATUS},1)            ;; Handle Dial Status
exten => _NXXNXXXXXX,n,Hangup(16)                                       ;; Safety net hangup

exten => _NXXNXXXXXX-BUSY,1,NoOp(${EXTEN:0:10} returns BUSY)
exten => _NXXNXXXXXX-BUSY,n,Busy(6)

exten => _NXXNXXXXXX-[N]OA[N]SWER,1,NoOp(${EXTEN:0:10} returns NOANSWER)
exten => _NXXNXXXXXX-[N]OA[N]SWER,n,Hangup(20)
{noformat}

When a call comes in for extension 3456789999, we start at dialin,3456789999,1.
We ring the endpoint for 6 seconds, if it's busy(dnd) we jump to dialin,${EXTEN}-${DIALSTATUS},1 , which in this case would be dialin,3456789999-BUSY,1

But with externpatternmatchnew=yes, we get:
[Nov  1 14:44:09] WARNING[16393][C-00000007]: pbx.c:6390 __ast_pbx_run: Channel 'SIP/TESTINGTRUNK-0000000c' sent to invalid extension but no invalid handler: context,exten,priority=dialin,3456789999-BUSY,1

If I set externpatternmatchnew=no, then it jumps to the right extension (dialin,3456789999-BUSY,1). The same occurs with no-answer and probably other dialstatus conditions.
                  
> extenpatternmatchnew doesn't match some extensions
> --------------------------------------------------
>
>                 Key: ASTERISK-22684
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22684
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/PBX
>    Affects Versions: 11.5.1
>            Reporter: Patrick Maille
>            Assignee: Patrick Maille
>            Severity: Minor
>
> When extenpatternmatchnew=yes, unable to match extensions that work with extenpatternmatchnew=no

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira