Amazing, We are talking about CURRENT CVS CODE chan_phone the way it DOES work, not zap, not anything else, not the way it SHOULD work.
CHAN_PHONE scans the ENTIRE dial plan on EVERY digit dialed in dialtone mode and what you describe does not work for chan_phone. Why is it so hard to accept the facts?
Brian West wrote:
No, newer code does exactly how I described it. Specific matches in the current context override wildcards in any included context. I have tested this and that's how Mark himself says it works. This is how it should work if I understand it correctly and I usually do, ast_matchmore_extension is
Sorry to ruin your theory.
what makes that possible. I don't have any zap hooked up to double check this. Jeremy did that in chan_skinny so it may very well be the channel driver at fault.
bkw
-----Original Message----- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Karl Brose Sent: Sunday, September 05, 2004 4:33 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Wildcards and variable number of digits
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.
_______________________________________________ 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
