Well, big telcos will anyway use big mediation systems (whether they really need them or not :-) ), but for most other implementations one consolidated table for CDRs might be enough for all practical purposes.




2010/5/22 Jan Berger <jan.berger@video24.no>

Firstly I would find out what’s already here because FS do have some CDR support.

 

A generic CDR daemon could be useful, though you should take into consideration that a distributed telecom system might need to write parts of a CDR on different computers.

 


From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Vitalii Colosov
Sent: 22. mai 2010 18:35

Subject: Re: [Freeswitch-dev] Would like to create and contribute a module "mod_cdr_logic"

 

Hi Jan,

 

Thanks for your inputs.

 

Basically what you described here makes me plan to create completely different thing that I was planning initially.

 

It should be "mod_cdr_mediation" - it must read the CDRs prepared by mod_cdr_csv, apply business rules, insert into the database and move successfully processed CDRs into archive directory.

 

If to go in this direction, I would also give the possibility to invoke a Lua/JS script before exporting CDRs, so user will create complex business logic to apply on the CDR values.

 

It will give a lot of flexibility, for example user can decide whether to skip some CDRs from inserting into the database, can enhance the values, etc...

 

Lua/FS script will receive selected CDR fields from the session variables, and enhanced / new values will be sent back to the mod_cdr_mediation for exporting.

 

Do you think this idea reflects what you described?

 

Thank you,

Vitalie

 

 

 


_______________________________________________
FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org