asterisk users - Jan 2005 - Re: I think your problem has to do with how you set the variable.

No Jeremy, excuse me, the error was in my email. The correct command is
/bin/echo "Channel: Local/$1@chiamamezzi-dialout";\
/bin/echo "Variable: 
callid=123456|number=$1|url=pippo|menuid=FOP|redirectnum=0554202880";\
/bin/echo "Context: chiamamezzi-Wave";\
/bin/echo "Exten: s";\
/bin/echo "Priority: 1";\
/bin/echo "Callerid: Asterisk Automatic Wardial";\
/bin/echo "Timeout: 10000";\
/bin/echo "Async: True";\
/bin/echo "ActionId: 10";\       
where the dialplan is:
[chiamamezzi-dialout]
exten => _X.,1,Dial(ZAP/g1d/${EXTEN},30)
exten => _X.,2,NoOp( _X.  DIALSTATUS is ${DIALSTATUS} number is ${number} )
exten => _X.,3,GotoIf($[$[${DIALSTATUS} = NOANSWER ] | $[${DIALSTATUS} = 
CANCEL]] ?_X.,5)

It is not only a problem for the variable number : I cant'se any 
variables att all.
Moreover if you look in the originate command, the context name is 
chiamamezzi-Wave  that I can show you:
 [chiamamezzi-Wave]
exten => s,1,Wait,1
exten => s,2,Answer
exten => s,3,DigitTimeout,5
exten => s,4,AbsoluteTimeout,140
exten => s,5,system(/prd/asterisk/sendxmlresponse.sh "-1 yes ${callid} 
${number} ${url}" )
exten => s,6,system(/prd/asterisk/log.sh  "Variabili: [menuid=${menuid}]
[number=${number}] [redirectnum=${redirectnum}] [url=${url}] 
[callid=${callid}]")
exten => s,7,BackGround(${wavemsg})

If the dial command succeds * goes on the chiamamezzi-Wave context and 
magically the variables get visible.
It seems an unsensible behaviour but probably I lack something,
Yes I use pri zapata channels and I am able to see and handle the BUSY 
event.
Luca

Jeremy Lichfield wrote:
> I think your problem has to do with how you set the variable. It looks 
> like you have a under score in your variable _number not number. So 
> you would call it with ${_number}. Are you able to get BUSY in the 
> DIALSTATUS using the originate command. If so are you using a PRI?
>
> Jeremy
>
>
> .
>

No , forget the undescore I wrote an error in the email. All the 
variables prints out correctly in chiamamezzi-Wave context only after 
the Originate command succesfully run the dial application on  
chiamamezzi-dialout , _X.,1
This is a row flow of what happens:
  User  Vars  visible(of course      user  vars not visible             
                                                                vars are 
now visible
I defined  them here)                                                    
                                                              
Originate             ->  Local/xxxx@chiamamezzi-dialout"              
(  Dial Success)                ->              chiamamezzi-Wave
Originate             ->  Local/xxxx@chiamamezzi-dialout"              
(  Dial failure)      I have DIALSTATUS but not the variables

As far as the Dialstatus I remember I had problems with capi bri 
channels where I was not able to get the BUSY signal and I devise a very 
bad workaround to handle busy lines. But I that time I didn't use the 
DIALSTATUS because I was unaware of it and also I used the originate 
command to go directly to the callee channel . Also I used the originate 
command in sync way and hence the originate failed in case of BUSY line 
( unfortunately alsoin case of NOANSWER and other event which therefore 
I was unable to discriminate ).
Luca

Jeremy Lichfield wrote:
> I'm sorry - still new at this. The information I got looked like this:
>
> /bin/echo  "Variable: 
> callid=123456|_number=$1|url=pippo|menuid=FOP|redirectnum=0554202880"
>
> And the number variable had a underscore..... So the variable prints  
> out correctly in chiamamezzi-Wave context, however not after the  
> Originate command? Is that your question?
>
> Also Do you know if you can get DIALSTATUS with out using PRI zapata  
> channels?
>
> Jeremy
>
> On Jan 25, 2005, at 11:05 AM, Luca Casavola wrote:
>
>> No Jeremy, excuse me, the error was in my email. The correct command is
>> /bin/echo "Channel: Local/$1@chiamamezzi-dialout";\
>> /bin/echo "Variable:  
>>
callid=123456|number=$1|url=pippo|menuid=FOP|redirectnum=0554202880";\
>> /bin/echo "Context: chiamamezzi-Wave";\
>> /bin/echo "Exten: s";\
>> /bin/echo "Priority: 1";\
>> /bin/echo "Callerid: Asterisk Automatic Wardial";\
>> /bin/echo "Timeout: 10000";\
>> /bin/echo "Async: True";\
>> /bin/echo "ActionId: 10";\       where the dialplan is:
>> [chiamamezzi-dialout]
>> exten => _X.,1,Dial(ZAP/g1d/${EXTEN},30)
>> exten => _X.,2,NoOp( _X.  DIALSTATUS is ${DIALSTATUS} number is  
>> ${number} )
>> exten => _X.,3,GotoIf($[$[${DIALSTATUS} = NOANSWER ] | 
>> $[${DIALSTATUS}  = CANCEL]] ?_X.,5)
>>
>> It is not only a problem for the variable number : I cant'se any  
>> variables att all.
>> Moreover if you look in the originate command, the context name is  
>> chiamamezzi-Wave  that I can show you:
>> [chiamamezzi-Wave]
>> exten => s,1,Wait,1
>> exten => s,2,Answer
>> exten => s,3,DigitTimeout,5
>> exten => s,4,AbsoluteTimeout,140
>> exten => s,5,system(/prd/asterisk/sendxmlresponse.sh "-1 yes 
>> ${callid}  ${number} ${url}" )
>> exten => s,6,system(/prd/asterisk/log.sh  "Variabili:  
>> [menuid=${menuid}] [number=${number}] [redirectnum=${redirectnum}]  
>> [url=${url}] [callid=${callid}]")
>> exten => s,7,BackGround(${wavemsg})
>>
>> If the dial command succeds * goes on the chiamamezzi-Wave context 
>> and  magically the variables get visible.
>> It seems an unsensible behaviour but probably I lack something,
>> Yes I use pri zapata channels and I am able to see and handle the 
>> BUSY  event.
>> Luca
>>
>> Jeremy Lichfield wrote:
>>
>>> I think your problem has to do with how you set the variable. It  
>>> looks like you have a under score in your variable _number not  
>>> number. So you would call it with ${_number}. Are you able to get  
>>> BUSY in the DIALSTATUS using the originate command. If so are you  
>>> using a PRI?
>>>
>>> Jeremy
>>>
>>>
>>> .
>>>
>>
>>
>
>
>