Yes, tried those suggestions, both a " and \, get passed with the string.

-- Executing [9@default:3] Set("SIP/10.10.50.1-00000003", 
"CALLERID(name)="Abelbeck\, Lonnie"") in new stack
-- Executing [9@default:4] Macro("SIP/10.10.50.1-00000003", "test,"Abelbeck\, 
Lonnie"") in new stack
-- Executing [s@macro-test:1] NoOp("SIP/10.10.50.1-00000003", 
"ARG1="Abelbeck\") in new stack
-- Executing [s@macro-test:2] NoOp("SIP/10.10.50.1-00000003", "ARG2= Lonnie"") 
in new stack
-- Executing [s@macro-test:3] NoOp("SIP/10.10.50.1-00000003", "ARG3=") in new 
stack


Lonnie

On Feb 9, 2012, at 4:22 PM, David Kerr wrote:

> 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 <[email protected]> 
> wrote:
> 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})
> exten => s,n,NOOP(ARG2=${ARG2})
> exten => s,n,NOOP(ARG3=${ARG3})
> 
> 
> exten => 9,1,Set(CALLERID(name)=Abelbeck Lonnie)
> exten => 9,n,Macro(test,${CALLERID(name)})
> exten => 9,n,Set(CALLERID(name)=Abelbeck, Lonnie)
> exten => 9,n,Macro(test,${CALLERID(name)})
> 
> 
> -- Executing [9@default:1] Set("SIP/10.10.50.1-00000002", 
> "CALLERID(name)=Abelbeck Lonnie") in new stack
> -- Executing [9@default:2] Macro("SIP/10.10.50.1-00000002", "test,Abelbeck 
> Lonnie") in new stack
> -- Executing [s@macro-test:1] NoOp("SIP/10.10.50.1-00000002", "ARG1=Abelbeck 
> Lonnie") in new stack
> -- Executing [s@macro-test:2] NoOp("SIP/10.10.50.1-00000002", "ARG2=") in new 
> stack
> -- Executing [s@macro-test:3] NoOp("SIP/10.10.50.1-00000002", "ARG3=") in new 
> stack
> 
> -- Executing [9@default:3] Set("SIP/10.10.50.1-00000002", 
> "CALLERID(name)=Abelbeck, Lonnie") in new stack
> -- Executing [9@default:4] Macro("SIP/10.10.50.1-00000002", "test,Abelbeck, 
> Lonnie") in new stack
> -- Executing [s@macro-test:1] NoOp("SIP/10.10.50.1-00000002", 
> "ARG1=Abelbeck") in new stack
> -- Executing [s@macro-test:2] NoOp("SIP/10.10.50.1-00000002", "ARG2= Lonnie") 
> in new stack
> -- Executing [s@macro-test:3] NoOp("SIP/10.10.50.1-00000002", "ARG3=") in new 
> stack
> ==
> Notice, "Macro(test,${CALLERID(name)})" passes different number of arguments 
> depending on if the callerid data contains a comma !
> 
> Is there a workaround? other than moving ${CALLERID(name)} into the macro.
> 
> Comma's are not uncommon in data.
> 
> Lonnie
> 
> PS: This works properly in Asterisk 1.4 because of the | delimiter.
> 
> 
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Astlinux-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to 
> [email protected].
> 
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing 
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/_______________________________________________
> Astlinux-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to 
> [email protected].


------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
[email protected].

Reply via email to