Re: [Astlinux-users] Macro arguments in Asterisk

2012-02-10 Thread John Novack
More or less off topic, but there are some ATA units ( Intomedia, from memory ) that won't ring if the CLID name has a comma in it! John Novack Chris Abnett wrote: > I never did understand why asterisk went from the pipe to the comma.. > Just for that reason > > When I ran into this I had t

Re: [Astlinux-users] Macro arguments in Asterisk

2012-02-10 Thread Chris Abnett
Interesting on replace.. Ive always had an AGI script to cleanse data.. Never ran macros more than a couple deep.. Always would rather come back before I get in too deep or use AEL which is more suited for lots of loopty loop hopping around... I didn’t realize replaced works like you describe..

Re: [Astlinux-users] Macro arguments in Asterisk

2012-02-10 Thread Lonnie Abelbeck
Hi Chris, Yes, GoSub() is favored over Macro() in Asterisk 1.8, but Macro() still works fine. The problem is Macro()'s can't be nested over 5 or so deep without maxing out the stack. GoSub() has no such limitations. As you say Asterisk 1.8 has a new REPLACE function, but I think that would be

Re: [Astlinux-users] Macro arguments in Asterisk

2012-02-10 Thread Chris Abnett
I never did understand why asterisk went from the pipe to the comma.. Just for that reason When I ran into this I had to cleanse my caller ID names before letting scripts get hold of them... Esp since my caller ID names are often keyed into hotel PMS systems by people.. They use whatever deli

Re: [Astlinux-users] Macro arguments in Asterisk

2012-02-10 Thread Lonnie Abelbeck
Update, I'm thinking this may be useful info, enclosed is an update. As David suggests this appears to be a bug using Macro (and parsing), so let's try GoSub()... -- [macro-test] exten => s,1,NOOP(ARG1=${ARG1}) exten => s,n,NOOP(ARG2=${ARG2}) exten => s,n,NOOP(ARG3=${ARG3}) [sub-test] exten =>

Re: [Astlinux-users] Macro arguments in Asterisk

2012-02-09 Thread David Kerr
Then I think that is a bug in Asterisk. Quoted fields should not parse out comas. I seem to recall a similar issue with CDR fields a while back (and your parsing of them for the CDR display). David On Thu, Feb 9, 2012 at 5:28 PM, Lonnie Abelbeck wrote: > Yes, tried those suggestions, both a " a

Re: [Astlinux-users] Macro arguments in Asterisk

2012-02-09 Thread Lonnie Abelbeck
Yes, tried those suggestions, both a " and \, get passed with the string. -- Executing [9@default:3] Set("SIP/10.10.50.1-0003", "CALLERID(name)="Abelbeck\, Lonnie"") in new stack -- Executing [9@default:4] Macro("SIP/10.10.50.1-0003", "test,"Abelbeck\, Lonnie"") in new stack -- Executing

Re: [Astlinux-users] Macro arguments in Asterisk

2012-02-09 Thread David Kerr
Try putting "Abelbeck, Lonnie" inside quotations. There is a risk that the quotations might get passed in with the arg. Alternatively can you escape characters that have meaning with a backslash, for example \, David On Thu, Feb 9, 2012 at 5:17 PM, Lonnie Abelbeck wrote: > Hi, > > I know, I'm

[Astlinux-users] Macro arguments in Asterisk

2012-02-09 Thread Lonnie Abelbeck
Hi, I know, I'm setting a bad example by asking an Asterisk question here... Before asking Asterisk Users, I was wondering if anyone else ran across this new Asterisk "feature" in 1.8. Here is a test example... -- Asterisk 1.8.9.1 [macro-test] exten => s,1,NOOP(ARG1=${ARG1}) ex