[Freeswitch-users] $${base_dir} effect

Vbvbrj vbvbrj at gmail.com
Wed Aug 1 10:53:39 MSD 2012


Hello.

I have a start up script which CDs to basedir of FS before launching 
daemon with "bin/freeswitch -nc".

In freeswitch.xml I have  <X-PRE-PROCESS cmd="set" data="base_dir=."/> 
to set other paths relative to current directory. As in default config 
files from repository most parameters which uses $${base_dir}/some-path 
a commented out, its hard to test. I've encountered problem with 
mod_callcenter. In callcenter.conf.xml there is:
<param name="record-template" 
value="$${base_dir}/${destination_number}.${strftime(%Y-%m-%d-%H-%M-%S)}.${caller_id_number}.${uuid}.wav"/>. 
In final freeswitch.xml.fsxml the line is:
<param name="record-template" 
value="/srv/freeswitch/recordings/${destination_number}.${strftime(%Y-%m-%d-%H-%M-%S)}.${caller_id_number}.${uuid}.wav"/>
But final recorded path from logs become 
$${sounds_dir}/$${base_dir}/recordings/ ie 
/opt/freeswitch/sounds/en/us/callie/./recordings/ or 
/opt/freeswitch/sounds/en/us/callie/recordings/ in final creation.

Where does this $${sounds_dir} come if I don't specify it?

Thank you.



Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users mailing list