asterisk users - Jan 2009 - Scope of variable

I have this extension:

exten => 1322,1,Answer()
exten => 1322,n,Set(CfMC_AMDValue="NotChecked")
exten => 1322,n,GotoIf($["${CfMC_DoAMD}" != "Yes"]?NOAMD)
exten => 1322,n,AMD()
exten => 1322,n,Set(CfMC_AMDValue = ${AMDSTATUS})
exten => 1322,n(NOAMD),Wait(1)
exten => 1322,n,UserEvent(E1322-1,${CfMC_ActionID}=${CHANNEL} &
${CfMC_AgentToUse} & ${CfMC_AMDValue})
exten => 1322,n,Playback(tt-weasels)
exten => 1322,n,Hangup()


When this executes I see these two line on the Asterisk CLI screen:

Set("Local/1321 at cfmc_cdi_info-df3d,1",
"CfMC_AMDValue="NotChecked"")
Set("IAX2/sfserver3-16384", "CfMC_AMDValue = MACHINE")

I am not sure why in the same extension it is setting two different
variables named CfMC_AMDValue. This then causes the following problem.

UserEvent("IAX2/sfserver3-16384",
"E1322-1|callE1321=IAX2/sfserver3-16384 &
IAX2/sfserver3/915419712512 & tqe & 1001 & NotChecked")

I do not want to set global variables as if I use this extension twice at
the same time there would be a conflict. What is the correct way to handle
this.

This is while running Asterisk 1.4.23
-- 
Jim Dickenson
mailto:dickenson at cfmc.com

CfMC
http://www.cfmc.com/

On Wed, Jan 28, 2009 at 2:48 PM, Jim Dickenson <dickenson at cfmc.com>
wrote:
> I have this extension:
> exten => 1322,n,Playback(tt-weasels)
Clearly the problem is that "weasels have eaten [your] phone system".
:-p

But really, you posted your 1322 condition, and then asked about
something happening with 1321. So you need to take a better look at
your extensions.conf and find out what is happening somewhere else.
Adding on variables you're not defining in your sample doesn't make it
any easier.

All I can say is that the 1322 condition is likely not the problem, or
at least not the problem you're asking about here. Try commenting it
out entirely, reload your dialplan, and do process of elimination
until you find the section of your dialplan you're actually having a
problem with.

You might also like to enable heavier debugging and confirm that when
you set those variables they end up with the values you think they
get, or your if's are going to eval differently, blah, blah, blah.