Bob Goddard wrote:
On Monday 17 Oct 2005 04:11, Kevin P. Fleming wrote:
Samy Antoun wrote:
[context1]
exten => s,1,Answer
exten => s,2,SetVar(MYVAR=1)
exten => s,3,Goto(context2,s,1)
[context2]
exten => s,1,NoOp(${MYVAR})
The NoOp in context2 will return 1?
Variables are set on the channel
On Monday 17 Oct 2005 04:11, Kevin P. Fleming wrote:
> Samy Antoun wrote:
> > [context1]
> > exten => s,1,Answer
> > exten => s,2,SetVar(MYVAR=1)
> > exten => s,3,Goto(context2,s,1)
> > [context2]
> > exten => s,1,NoOp(${MYVAR})
> >
> > The NoOp in context2 will return 1?
>
> Variables are set on t
Samy Antoun wrote:
--- "Eric \"ManxPower\" Wieling" <[EMAIL PROTECTED]> wrote:
That is the default. Once you set a variable it should exist for the
life of the channel. Now, if you are wanting to access that variable
when one channel spawns another channel (like chan_local does), then
prefix
Samy Antoun wrote:
[context1]
exten => s,1,Answer
exten => s,2,SetVar(MYVAR=1)
exten => s,3,Goto(context2,s,1)
[context2]
exten => s,1,NoOp(${MYVAR})
The NoOp in context2 will return 1?
Variables are set on the channel itself, they aren't related to contexts
at all.
--- "Eric \"ManxPower\" Wieling" <[EMAIL PROTECTED]> wrote:
> That is the default. Once you set a variable it should exist for the
> life of the channel. Now, if you are wanting to access that variable
> when one channel spawns another channel (like chan_local does), then
> prefix the name of th
Samy Antoun wrote:
Hi,
Is there anyway to pass a variable from one context to another (NOT
macro and NOT global)
That is the default. Once you set a variable it should exist for the
life of the channel. Now, if you are wanting to access that variable
when one channel spawns another channel
Hi Samy,
Well, I've ran into the same issue a while back, and ended up solving it
by using an AGI script to
Actually performa a manager based originate with variables. This was I
actually dialed a specific extension
In a specific context, with pre-loading the variables I needed for the
target c
