Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-18 Thread Kevin P. Fleming
Shidan wrote: But, when you imply "that's your problem because it wasn't documented", I would really like to know where this official documentation is apart from reading the source code. Most successful Asterisk based operations are novel and creative hacks, not structured formulas that follow a

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-18 Thread Shidan
> It was _never_ documented that you could skip a numeric parameter for > the substring functionality and expect it to work properly. If it did, > you got lucky. When it stopped, you got unlucky. Apart from the source code and its comments whats the official "documentation of Astreisk. I know the

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-17 Thread Pisac
I was never read documentation about that substring functionality. I was (once upon a time) just thinking about how can I extract first 3 digits from CALLERIDNUM, and what appears logical to me is that I should try CALLERIDNUM::3 Guess what, it's worked! That was the first idea that come in to my

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-17 Thread Kevin P. Fleming
Pisac wrote: But I'm dissapointed with all this minor & needless & problematic changes which needlessly spending my time. I will realy double rethink in the future about upgrading any tuned system to new Asterisk release. It was _never_ documented that you could skip a numeric parameter for t

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-14 Thread Pisac
Yes, you are right, it's working. Thanks. - Original Message - From: "Steve Ringwald" <[EMAIL PROTECTED]> > Pisac wrote: > > Sorry, I use correct syntax in dialplan, but here in e-mail I maked this > > mistake. > > In dialplan I'm using ${CALLERIDNUM::3} > > Just for grins, have you trie

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-14 Thread Pisac
I'm using Asterisk 1.2.1-BRIstuffed-0.3.0-PRE-1f Your answer was helpfull, it's working now like it used before. But I'm dissapointed with all this minor & needless & problematic changes which needlessly spending my time. I will realy double rethink in the future about upgrading any tuned system

RE: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-14 Thread Chris Bagnall
> So, > if > ${CALLERIDNUM}=0123456789 > Then > ${CALLERIDNUM:3} returns 3456789 > ${CALLERDINUM::3} returns 012 > ${CALLERIDNUM:3:3} returns 345 > But this do not work anymore in 1.2.1, and if I do not found > solution for this I will downgrade to 1.0.9 Have you tried ${CALLERID(number)::3} ? I

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-14 Thread Steve Ringwald
Pisac wrote: Sorry, I use correct syntax in dialplan, but here in e-mail I maked this mistake. In dialplan I'm using ${CALLERIDNUM::3} Just for grins, have you tried ${CALLERIDNUM:0:3} I have always found it better to explicitly specify what to do, rather than relying on a function's assump

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-14 Thread trixter aka Bret McDanel
On Sat, 2006-01-14 at 14:49 +0100, Pisac wrote: > I maked mistake in my previous e-mail, but in my dialplan I didn't make > this mistake. So, my intention in previous e-mail was to write: > > ${CALLERIDNUM:3} erase first 3 digits > ${CALLERIDNUM::3} returns first 3 digits > ${CALLERIDNUM:3:3} shou

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-14 Thread Pisac
I maked mistake in my previous e-mail, but in my dialplan I didn't make this mistake. So, my intention in previous e-mail was to write: ${CALLERIDNUM:3} erase first 3 digits ${CALLERIDNUM::3} returns first 3 digits ${CALLERIDNUM:3:3} should erase first 3 digits and return next 3 digits So, if ${C

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-14 Thread Pisac
Sorry, I use correct syntax in dialplan, but here in e-mail I maked this mistake. In dialplan I'm using ${CALLERIDNUM::3} - Original Message - From: "Trevor G. Hammonds" <[EMAIL PROTECTED]> > You are using incorrect syntax. Notice where the close bracket is placed, > using your exampl

RE: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-14 Thread Trevor G. Hammonds
You are using incorrect syntax. Notice where the close bracket is placed, using your examples: ${CALLERIDNUM:3} erase first 3 digits ${CALLERIDNUM::3} returns first 3 digits ${CALLERIDNUM:3:3} should erase first 3 digits and return next 3 digits Pisac wrote on Saturday, 14 January 2006 5:10 AM

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-14 Thread Pisac
No, ${CALLERIDNUM}:3 erase first 3 digits ${CALLERIDNUM}::3 returns first 3 digits ${CALLERIDNUM}:3:3 should erase first 3 digits and return next 3 digits So, if ${CALLERIDNUM}=0123456789 Then ${CALLERIDNUM}:3 returns 3456789 ${CALLERDINUM}::3 returns 012 ${CALLERIDNUM}:3:3 returns 345 But this d

Re: [Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-14 Thread Dinesh Nair
On 01/14/06 11:09 Pisac said the following: But, it's not working anymore in Asterisk 1.2.1 when I test this with noop(${CALLERIDNUM::3}) I get full callerid, not just first 3 numbers like it use to be on 1.0.9 i believe the syntax is ${CALLERIDNUM:3} and not as you're using it with double c

[Asterisk-Users] CALLERIDNUM::3 do not working on 1.2.1

2006-01-13 Thread Pisac
I upgraded from 1.0.9, to 1.2.1. I was using this line exten => s,1,gotoif($[${CALLERIDNUM::3} = 066]?mycity,1:other,1) it selecting calls if callerid begins with some number pattern (from some city) But, it's not working anymore in Asterisk 1.2.1 when I test this with noop(${CALLERIDNUM::3}) I g