Anthony Minessale 741b8329b9 Modifying the behaviour of the dialplan engine ... the 'data' field in action tags may now refer to variables and api functions to be expanded at runtime. Syntax: $varname ${varname} &func_name(func args) Exception: variables that are numeric are still expanded at dialplan compile time based on the regex eg $1 $2 etc Example: <extension name="1000"> <condition field="destination_number" expression="^(1000)$"> <action appplication="my_route_app" data="$1"/> <action appplication="bridge" data="$destination"/> </condition> </extension> Here the $1 is ecaluated before the call begins setting it to 1000 based on the regex ^(1000)$ $destination is evaluated on the fly in execution once the my_route_app has run and has had a chance to set the variable 'destination' to the correct value. git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@2994 d0543943-73ff-0310-b7d9-9358b9ac24b2		2006-10-07 19:54:04 +00:00
..
mod_dialplan_directory	Cleanups from update to new build system for windows.	2006-08-18 07:22:18 +00:00
mod_dialplan_xml	Modifying the behaviour of the dialplan engine	2006-10-07 19:54:04 +00:00