| Summary: | ASTERISK-12087: Ex-girlfriend-logic requires also most-specific extension matching | ||
| Reporter: | Marcelo M. Sosa Lugones (marsosa) | Labels: | |
| Date Opened: | 2008-05-27 07:55:09 | Date Closed: | 2011-06-07 14:07:56 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/NewFeature |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I wanted something like this: exten => _X./5551234,1,Congestion exten => _[12345]X.,1,blabla exten => _[67890]X.,1,blabla And the only way i can make that work is: exten => _[12345]X./5551234,1,Congestion exten => _[67890]X./5551234,1,Congestion exten => _[12345]X.,1,blabla exten => _[67890]X.,1,blabla Of course, my dialplan is much longer than that, not just 2 cases, that's why i'm seeing this as a bug. I think it should try to match by callerid first and then match by dialed number. Am i wrong? | ||
| Comments: | By: Jared Smith (jsmith) 2008-05-27 08:49:35 I think you're misunderstanding a fundamental of how the pattern matching is designed to work in Asterisk. Asterisk *first* looks at the dialed extension, and tries to find an exact match. If there's no match, it looks for the best pattern in the current context. Only *after* the best match is found it check to see if the Caller*ID number matches. In other words, a Caller*ID number match _does not_ make a pattern have a higher precedence than a more specific pattern without a Caller*ID number match. By: Marcelo M. Sosa Lugones (marsosa) 2008-05-27 09:15:12 Thanks, so this should be closed. Sorry. By: Eliel Sardanons (eliel) 2008-05-27 09:37:41 Closed per reporter. | ||