Ok but this is available today and works fine, so it can be used as a zero day replacement. Any syntax change is welcome but will take time until it gets in a public release and does not save you the hassle to change the dialplans anyway - unless you implement it as a default behaviour at the SIP driver level. And I got a feeling that most people will simply not bother learning regexps.... You could just as reasonably write a script to do the check, or run a check in the dialplan itself, or change Asterisk. l.
2010/2/15 Steve Murphy <[email protected]> > > > On Mon, Feb 15, 2010 at 8:25 AM, Lenz Emilitri <[email protected]>wrote: > >> Yes but in any case you can enter all of the strings that reasonably match >> - even if you have variable-length numbers, you will be able to determine >> that a valid number be between 5 and 15 characters - or likely 2 to 20, all >> numbers. A number of 156 characters is very likely to be a problem. >> > > This is probably a stupid idea, because it could only be implemented in > trunk, and won't help with current implementations, > and I suggested it a long time ago already when I did the fast pattern > matching code, but I don't THINK it would be all that > hard to offer SOME regex syntax in patterns to help reduce the impact of > these kinds of problems. > > -- Loway - home of QueueMetrics - http://queuemetrics.com
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
