Hi Woody :)
You cannot use the variable on another extension, however you could just merge both extensions' conditions.
then your only problem would be that you're not exporting the value, after set, you gotta export, look at this example (a little extract from dialplan/default.xml):
<extension name="Local_Extension">
<condition field="destination_number" expression="^(10[01][0-9])$">
<action application="set" data="dialed_extension=$1"/>
<action application="export" data="dialed_extension=$1"/>
</condition>
<condition field="destination_number" expression="^${caller_id_number}$">
<action application="set" data="voicemail_authorized=${sip_authorized}"$
<action application="answer"/>
<action application="sleep" data="1000"/>
<action application="voicemail" data="check default ${domain_name} ${dialed_extension}"/>
...
<anti-action application="bridge" data="user/${dialed_extension}@${domain_name}"/>
</condition>
</extension>
Woody Dickson <woodydickson@gmail.com> wrote:When parsing the dial plan, FreeSWITCH tests all of the conditions, then
> I am getting a strange problem in my dialplan.
>
> After doing "SET", I want to use it in the next condition field. But then
> the value is not being set properly.
builds a linked list of actions to execute. Once this is done, the actions are
executed, in order.
This is why you can't simply set a variable in one extension and test it in
the condition of a later extension.
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org