| Summary: | ASTERISK-28191: features.conf option blindxfer doesn't seem to do Pattern Matching. | ||
| Reporter: | Michael (ringo) | Labels: | pjsip |
| Date Opened: | 2018-11-29 14:15:48.000-0600 | Date Closed: | |
| Priority: | Minor | Regression? | |
| Status: | Open/New | Components: | Features |
| Versions: | 16.0.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | debian 9 amd64 asterisk v16 LTS using pjsip mysql ODBC | Attachments: | |
| Description: | the blindxfer option configured via features.conf only seems to work with exact configured extensions ie. '1234' => 1. NoOp()" , but not pattern matched exten like '_X!' => 1.NoOp()"
| ||
| Comments: | By: Asterisk Team (asteriskteam) 2018-11-29 14:15:50.438-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Benjamin Keith Ford (bford) 2018-11-30 08:30:08.719-0600 Yep, definitely something weird going on here. {code} exten => _X89!,1,NoOp() {code} works, but {code} exten => _X87!,1,NoOp() {code} in the same context doesn't. Opening this one up. | ||