-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Birgit,
well of course the condition is THE condition, but I espected the whole
dialplan is executed sequentially, so that this fictive dialplan works:
<condition field="xyz" expression".*" break="never">
<action application="set" data="MYVAR=abc"/>
</condition>
<condition field="MYVAR" expression="abc">
<action application="bridge" data="....."/>
<anti-action application .... />
</condition>
but unfortunately all conditions are parsed befor executing the actions,
so MYVAR is nearly worthless in dialplan (except within applications).
regards
Helmut
Birgit Arkesteijn schrieb:
> Hi Helmut,
>
> As far as I know, the <condition> at the top of the dialplan is indeed
> THE condition.
>
> We've used two mechanism for 'dynamic' dialplan:
> - xml_curl: freeswitch posts parameters to a URL and the URL returns a
> dynamic dialplan. This works well with a webserver connected to a database
> - javascript (spidermonkey)
>
> Hope the above helps,
> Birgit
>
>
> On 11/11/08 12:51, Helmut Kuper wrote:
> Hi,
>
>
> I want a dialplan setting a channel variable with a certain value. After
> that I want to do some action depending of that variable/value. But it
> looks like that FS parses the regular expressions of dialplan conditions
> only at the beginning of dialplan_hunt, so that conditions based on
> channel variables are only possible with the variable values at the time
> of starting dialplan_hunt.
>
>
> Is that true or is there a way to do what I like to do ?
>
>
> regards
> helmut
>
>
>>
iEYEARECAAYFAkkZh6MACgkQ4tZeNddg3dxGVwCgllX9/Xz/Dv9Tlisy5OKXXt8N
AYQAnirOm1w2veyLqaVRYQmcD1IogYa9
=/pjY