XML_CDR allows this now... And you don't have to use the posting... Also, it allows for single call exceptions Drop the CDRs to the File System Use favorite scripting language to scrape and process, if exception move to exception directory and fire alert, if good move to done directory, If no DB connection, time out and wait a minute before even processing them in the first place Even you use the post method, you still have to do the above steps to make sure a post didn't fail... Also you, this way you don't have to SIGHUP FS constantly to rotate the CSV CDRs... On 2/6/12 8:54 AM, "Carlo Dimaggio" <jaasmailing@gmail.com> wrote:
Il 06/02/12 15.29, Avi Marcus ha scritto:
You don't need a single file per call to do billing... I personally POST and have my import script do the billing management. what about network problems? For example, if the web server is unreachable the call must be stored on the filesystem. Suppose that arrives a new call, in this case the state of the billing system is inconsistent and must be resynchronized before sending quota or credit info. One file per call allows me to process just the single (or multiple) call without the need to parse the entire cdr file (after this process, I could move the file to another directory).
perl + cdr_csv could be interesting but no posting.
What do you think about?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org