[asterisk-bugs] [JIRA] (ASTERISK-23805) Dialplan pattern matching error

[Andres Mazzocchi (JIRA)]

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

Andres Mazzocchi commented on ASTERISK-23805:
---------------------------------------------

Oh, I realize now. The Z is there because I don't want people to be able to dial 00 (international prefix). In my mind somehow that first X was completely omitted so I was matching 20 to Z. instead of XZ.

Sorry for the inconvenience, I'll close the issue.

> Dialplan pattern matching error
> -------------------------------
>
>                 Key: ASTERISK-23805
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23805
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Dial
>    Affects Versions: 11.4.0, 11.9.0
>         Environment: CentOS 6.5
>            Reporter: Andres Mazzocchi
>            Severity: Minor
>
> There's a little flaw in the pattern matching algorythm. This pattern is pretty straighforward:
> {code}
> exten => _9XZ.,1,Answer()
> {code}
> It means one should be able to dial 9(0-9)(1-9). numbers, unlimited length.
> However, if the dialed number begins with 920., Asterisk returns the following error:
> {code}
> ---
> Call from '2801' to extension '920256666' rejected because extension not found in context 'xxxxxxxx'.
> ---
> {code}
> A simple workaround is to add an additional entry tailored for these specific numbers:
> {code}
> exten => _920.,1,Answer()
> {code}
> Furthermore, the pattern recognizes correctly numbers 921 to 929. The only one that is not recognized is 920.
> I've discovered this while using Asterisk 11.4.0, then I upgraded to 11.9.0 and the error is still present. I don't know about the versions in between.



--
This message was sent by Atlassian JIRA
(v6.2#6252)