Summary: | ASTERISK-04943: Request for Change of Priority | ||
Reporter: | inix (inix) | Labels: | |
Date Opened: | 2005-08-31 11:51:35 | Date Closed: | 2011-06-07 14:03:08 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | When writing an extension rule, it might be more effective if _9XXX or _90082. can overrule _9. In this case, we can write exception rules much easier with a "standard" rules. This is especially useful when we're dealing with International Numbers when _900. is the only rule which makes sense. For example, I would like my users to make International Calls, I'll write the following. exten = _900.,1,Dial(Zap/g1/${MACRO_EXTEN:1},,gtwW) <-- For normal International Calls exten = _90082.,1,Dial(IAX2/servername/${MACRO_EXTEN:1},,gtwW) <-- For Special Routing. This change will bring the * more in line with conventional PABX like Mitel, Siemens and Erricson. PS: It could be that I'm wrong. I'm not exactly a * guru, but if i've not done it wrongly, maybe you guys should consider it.. | ||
Comments: | By: Kevin P. Fleming (kpfleming) 2005-08-31 12:13:36 It already works the way that you are requesting, and even if it didn't, you can easily set it up the way you want using 'include =>' statements. There is no need for the dialplan parser/executer to be changed. If there is a specific scenario that you want to accomplish but cannot figure out how, post a _detailed_ request for help to the asterisk-users mailing list. If it turns out that Asterisk cannot do what you want, then (and only then) you can open a bug here with the detailed example and what you have tried to do. |