[asterisk-dev] cmd set with multiple values

[Enzo Michelangeli]

I don't think you can use a single DIALSTRING variable, and expect Dial()
to understand it as three parameters. I would rather use something like:

exten => 907,1,Set(DESTINATION=Zap/G1/4989123456789)
exten => 907,n,Set(TIMEOUT=10)
exten => 907,n,Set(OPTIONS=gh)
...
exten => 907,n,Dial(${DESTINATION},${TIMEOUT},${OPTIONS})

Enzo

----- Original Message ----- 
From: "Christian Benke" <a0305292 at unet.univie.ac.at>
To: <asterisk-users at lists.digium.com>
Cc: <asterisk-dev at lists.digium.com>
Sent: Friday, February 03, 2006 7:49 PM
Subject: [asterisk-dev] cmd set with multiple values


> hello!
>
> has this made it into 1.2.3 already:
> http://bugs.digium.com/view.php?id=6128 ?
>
> i'm trying to set a variable that should be used as a dialstring in the
> dial-command, including parameters seperated with the respective
> delimiter, e.g. like:
>
> exten => 907,1,Set(DESTINATION1=Zap/G1/4989123456789|10|gh)
> exten => 907,n,Set(DIALSTRING=${DESTINATION1})
> exten => 907,n,Dial(${DIALSTRING})
>
> asterisk complains:
>
> Feb  3 12:39:40 WARNING[26200]: pbx.c:6010 pbx_builtin_setvar: Ignoring
> entry '10' with no = (and not last 'options' entry)
>
> i've tried several of the resolution-proposals mentioned in the
> bugnotices, but none of them seems to work yet.
> the best fit was exten =>
> 907,1,Set(DESTINATION1='Zap/G1/4989123456789,10,gh') but then the value
> included in the quotes seems to be set as a string that is not parsed
when
> dialing ${DIALSTRING}, resulting in
>
> Called G1/4989123456789,10,gh
>
> is there any workaround?
>
> thanks
> christian
>
> -- 
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>