Indeed, there is no way to load a module multiple times.
Modules register various api and app commands. Loading a module twice would register the same command twice, then how does fs know which module you mean?
I would agree with Hassan - mod_xml_cdr is far more versatile, as the web server can read the account variable and use that to determine what to do with the cdr.
Steve on iPhone
I don't think you can load the same module twice.
I would suggest you take a look at mod_xml_cdr. It dumps a whole lot of information, which can be very useful for debugging as well. You're already using an external program to parse the CSV files. Just need it to parse the XML output, and you've got access to a whole lot more!
Regards
HASSAN
On Fri, Aug 13, 2010 at 14:27, François Delawarde
<fdelawarde@wirelessmundi.com> wrote:
Thanks for the answers,
I initially wanted to use the accountcode variable as an account code
for billing and not for template selection, but I guess I can use it for
template and create another variable (ex: realaccountcode) for the
actual account code.
Only thing would be that I'd be limited to two templates. Say I want to
log to CSV and a couple of database tables with different fields, well
I'll have to do it "manually".
> what I would do is to log all the fields you need to Master.csv, and
> then do selective imports of the fields you require depending on the
> usage.
> mysqlimport (LOAD DATA INFILE) allows that if you put a dummy variable
> (@dummy) instead of a column name.
Nice idea thanks, I could also have my own CDR script listening for
hangup events, or to log everything to say an sqlite db and use a cron
script to create other logs out of it, but the LOAD DATA INFILE method
seems quite cool.
Last question: Is there any way to load this module more than one time
with different base directories to make it simpler?
Thanks again,
François.