Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-17 Thread John Todd
At 5:46 PM +0200 2008/10/16, Olivier wrote: Is Incomplete() application an acceptable work around for ISN ? It is impossible to determine the full sequence of digits for an ISN number ahead of time (well, I shouldn't say impossible because one could create a really nasty hack...) because the

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-17 Thread Olivier
2008/10/17 John Todd [EMAIL PROTECTED] At 5:46 PM +0200 2008/10/16, Olivier wrote: Is Incomplete() application an acceptable work around for ISN ? It is impossible to determine the full sequence of digits for an ISN number ahead of time (well, I shouldn't say impossible because one

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-17 Thread Tilghman Lesher
On Friday 17 October 2008 10:15:22 Olivier wrote: 2008/10/17 John Todd [EMAIL PROTECTED] At 5:46 PM +0200 2008/10/16, Olivier wrote: Is Incomplete() application an acceptable work around for ISN ? It is impossible to determine the full sequence of digits for an ISN number ahead of time

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-16 Thread Olivier
Is Incomplete() application an acceptable work around for ISN ? ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit:

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-16 Thread Tilghman Lesher
On Thursday 16 October 2008 10:46:51 Olivier wrote: Is Incomplete() application an acceptable work around for ISN ? If you could explain what ISN is, that might help. -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-16 Thread Karl Fife
On Thu, 16 Oct 2008 11:47:15 -0500, Tilghman Lesher [EMAIL PROTECTED] said: If you could explain what ISN is, that might help. an ISN, stands for ITAD Subscriber Number, which in turn stands for 'Internet Telephony Administrative Domain Subscriber Number'. Essentially it is a very clever way

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-16 Thread Steve Murphy
On Thu, 2008-10-16 at 13:59 -0500, Karl Fife wrote: On Thu, 16 Oct 2008 11:47:15 -0500, Tilghman Lesher [EMAIL PROTECTED] said: If you could explain what ISN is, that might help. an ISN, stands for ITAD Subscriber Number, which in turn stands for 'Internet Telephony Administrative

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-16 Thread Tilghman Lesher
On Thursday 16 October 2008 13:59:46 Karl Fife wrote: On Thu, 16 Oct 2008 11:47:15 -0500, Tilghman Lesher [EMAIL PROTECTED] said: If you could explain what ISN is, that might help. an ISN, stands for ITAD Subscriber Number, which in turn stands for 'Internet Telephony Administrative Domain

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-15 Thread Jared Smith
On Tue, 2008-10-14 at 19:59 -0500, Karl Fife wrote: QUESTION: Is there a way to do just that? As in: match: one more of the preceding character or expression (a variation on '.') zero more of the preceding character or expression (a variation on bang) No, there's currently nothing in the

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-15 Thread Steve Murphy
On Wed, 2008-10-15 at 09:06 -0400, Jared Smith wrote: On Tue, 2008-10-14 at 19:59 -0500, Karl Fife wrote: QUESTION: Is there a way to do just that? As in: match: one more of the preceding character or expression (a variation on '.') zero more of the preceding character or expression (a

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-15 Thread Karl Fife
On Wed, 15 Oct 2008 14:22:09 -0600, Steve Murphy [EMAIL PROTECTED] said: the real killer is trailing context... for instance... XX[58]*ZZ If you give it the pattern 3358, it has to decide that the [58]* part is empty and the 58 is matched by ZZ. And this makes the whole algorithm pretty

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-14 Thread Benny Amorsen
Steve Murphy [EMAIL PROTECTED] writes: Other than the above, we could invent a slightly different syntax for pcre type expressions; and you'd have to invent some sort of disambiguation for when multiple extensions might be matched, to choose the 'best' one. I'd just use strict ordering from

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-14 Thread Karl Fife
I have to eat crow here guys. I was completely wrong about the use of dialplan wildcards and non numerics such as *,# and +. My test was invalid and I drew the wrong conclusion. So to summarize: A single dialplan extension that matches '3129842314' or '*989' or '+13129842314' BUT NOT 'i' nor

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-14 Thread Benny Amorsen
Karl Fife [EMAIL PROTECTED] writes: is in fact simply something like: exten = _[0-9*#+]X.,1,NoOp(*** match ***) As long as you're happy to match *9foo and not match **123, then yes, that will work. /Benny ___ -- Bandwidth and Colocation Provided

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-14 Thread Karl Fife
On Wed, 15 Oct 2008 01:54:40 +0200, Benny Amorsen [EMAIL PROTECTED] said: Karl Fife [EMAIL PROTECTED] writes: is in fact simply something like: exten = _[0-9*#+]X.,1,NoOp(*** match ***) As long as you're happy to match *9foo and not match **123, then yes, that will work. Thanks

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-13 Thread Steve Murphy
On Sat, 2008-10-11 at 10:09 +0200, Benny Amorsen wrote: Tilghman Lesher [EMAIL PROTECTED] writes: exten = [0-9*#+].,... If that does not work, that is a bug and needs to be reported as such. Sadly that matches *james and 9foo... It would be nice if you could use normal regexes (e.g.

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-13 Thread Karl Fife
Steve Murphy [EMAIL PROTECTED] wrote: People have voiced this before; but the cut-down version of RE's that the matching algorithms allow are fairly fast, both in the new and the old pattern matching algorithms. Steve Your explanation is clear and it seems like a good design choice to

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-13 Thread Eric ManxPower Wieling
exten = +13129842314,1,Noop(Happy match!) or exten = _+1NXXNXX,1,Noop(Happier match!) Karl Fife wrote: Steve Murphy [EMAIL PROTECTED] wrote: People have voiced this before; but the cut-down version of RE's that the matching algorithms allow are fairly fast, both in the new and the old

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-11 Thread Benny Amorsen
Tilghman Lesher [EMAIL PROTECTED] writes: exten = [0-9*#+].,... If that does not work, that is a bug and needs to be reported as such. Sadly that matches *james and 9foo... It would be nice if you could use normal regexes (e.g. with the pcre library) in extensions.conf. /Benny

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-08 Thread Rob Hillis
Tilghman Lesher wrote: Can someone suggest the best way to deal with this without resoring to a highly repetitive/iterative dialplan? Leif and I discussed something like this at Astricon 2008, and we came up with this patch: http://bugs.digium.com/view.php?id=13632 Nice! For those of

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-08 Thread Tilghman Lesher
On Tuesday 07 October 2008 21:58:31 Karl Fife wrote: So that leaves only one question: exten = ? What extension the following: '3129842314' '*989' '+13129842314' BUT does not match: 'i' 'james' is this possible? I think you already described it in your original post: exten =

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-08 Thread Tilghman Lesher
On Wednesday 08 October 2008 02:20:38 Rob Hillis wrote: Tilghman Lesher wrote: Can someone suggest the best way to deal with this without resoring to a highly repetitive/iterative dialplan? Leif and I discussed something like this at Astricon 2008, and we came up with this patch:

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-07 Thread Tilghman Lesher
On Monday 06 October 2008 14:58:09 Karl Fife wrote: In several places online, and in the Asterisk F.O.T. book, there is a warning against using '_.' saying: [it] should probably never be used. However, the need often arises act on numeric extensions that begin with *'s and #'s, and '+', and

Re: [asterisk-users] Matching *, + and # in the dialplan

2008-10-07 Thread Karl Fife
Leif and I discussed something like this at Astricon 2008, and we came up with this patch: http://bugs.digium.com/view.php?id=13632 -- Tilghman That's a great idea. Good work. Also, nice work with the new CDR stuff in 1.6! So that leaves only one question: exten = ? What

[asterisk-users] Matching *, + and # in the dialplan

2008-10-06 Thread Karl Fife
In several places online, and in the Asterisk F.O.T. book, there is a warning against using '_.' saying: [it] should probably never be used. However, the need often arises act on numeric extensions that begin with *'s and #'s, and '+', and of course _X. does not match I have tried exten =