[Home]

Summary:ASTERISK-18343: extenpatternmatchnew fails to correctly respect dialplan order (regex match before exact in an included context)
Reporter:snuffy (snuffy)Labels:
Date Opened:2011-08-24 19:39:14Date Closed:
Priority:MinorRegression?
Status:Open/NewComponents:PBX/General
Versions:SVN 13.18.4 Frequency of
Occurrence
Constant
Related
Issues:
is related toASTERISK-19137 patten matching wrong when issue "dialplan reload"
Environment:Attachments:
Description:extenpatternmatchnew fails to correctly respect dialplan order (regex match before exact in an included context)

Example:

SIP user is a conA member.

'extenpatternmatchnew' is FALSE

If they dial 1234, they get the exact match executed. (RIGHT)
If they dial 1236, they get the regex match executed. (RIGHT)

If they dial 4321, the get they extact match executed (RIGHT)
If they dial 4325, they get the regex match excuted (RIGHT)


'extenpatternmatchnew' is TRUE

If they dial 1234, they get the exact match executed. (RIGHT)
If they dial 1236, they get the regex match executed. (RIGHT)

If they dial 4321, the get they regex match executed (WRONG)
If they dial 4325, they get the regex match excuted (RIGHT)



{noformat}
[conA]
include => conB
exten => 1234,1,verbose(got to 1234)
exten => 1234,n,hangup

exten => _123X,1,verbose(got to 123X exten)
exten => _123X,n,hangup

[conB]

exten => 4321,1,verbose(got to 4321)
exten => 4321,n,hangup

exten => _432X,1,verbose(got to 432X exten)
exten => _432X,n,hangup
{noformat}
Comments: