No Brian,
The old driver scans the ENTIRE dial plan on EVERY digit dialed so no matter where, if you have a
"." wildcard in the plan, it will match always on the first digit dialed.
It is the driver that does this.
If you use a SIP phone, or any technology that presents a complete dial string, then you are correct
with your examples.
Brian West wrote:
Actually it does the proper usage of the "." char in your dial plan should solve this problem. It's not the channel driver that's doing this its asterisk. You need to sandbox a wildcard into its own context then include it. Otherwise it wins NO MATER WHAT. This way an extension defined within the current context wins over the included wildcard context. S= bkw
-----Original Message----- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Eric Jacksch Sent: Sunday, September 05, 2004 2:50 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Wildcards and variable number of digits
Not sure I understand..does that help my problem of not being able to enter sufficient digits, or is that a consideration once I get a driver that allows me to # terminate the dialing string?
On 2004-09-05 15:00, "Brian West" <[EMAIL PROTECTED]> wrote:
documentedJust to clarify the usage of the . wildcard in your dialplan.
Here is the proper usage of this feature which seems to not be
asANYWHERE very well.
[default] include => other exten => _712XXX,1,NoOp,Blah
[other] exten => _7.,1,NoOp,somethingelse
The extensions in the current context win over an include.. only if
something doesn't specifically match in [default] but does as a wildcard
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
