Moreover, looks like instead of XML tree we should be able to use dialplan template here to make it more customizable.

Done - svn revision 76

Freeswitch docs tell that variables should be resolved normally in this case.

Yeah, I just tested it against freeswitch revision 13223 and it worked. So it was fixed somewhere between freeswitch revision 10359 snd 13223.

Thanks for the link to the freeswitch docs .. it sounds like that variable resolution might actually work. I will test it on a later version of freeswitch and see what happens.

Also, looks like dialplanbuilder.build_xml function has some incostintencies. First we create an XML tree starting with context tag, then check if current extension has condition tag and if it does we use string substitution with another string. So in the latter case there was no need to create XML tree here. Moreover, looks like instead of XML tree we should be able to use dialplan template here to make it more customizable. This would let the users to easily change all dialplans easily, e.g. could be used for setting some variables, silence detection, authorization checks.

Now it should be much easier to customize the configuration to your specific needs when that customization is not supported in the web interface / database.

The templates are still outdated compared to the current config, and will be brought up to date soon. But it should be fairly easy since it is just a matter of merging in new parameters to the xml template. (all templates are located in the freeswitchxml subdirectory).

WARNING: don't try to use default variables like $${foo} that are defined in vars.xml in the static freeswitch config. This will be passed verbatim to freeswitch, which will not resolve the variable. Not sure if this is a bug in freeswitch or by design. Only tested against an old version of freeswitch (10300) so your mileage may vary.