V14SP2 - CDR - CSV Bug

Discussion in '3CX Phone System - General' started by Futureweb, Dec 3, 2015.

Thread Status:
Not open for further replies.
  1. Futureweb

    Futureweb New Member

    Joined:
    Jun 29, 2015
    Messages:
    163
    Likes Received:
    14
    Hello,

    CDR Data is sent as Comma Seperated Values (using "Client /Active Socket" configuration) ... so far so good - until you got Call Costs of 0.x ... as they get sent as 0,x (0,5, ...)
    So it's breaking the CSV - a Cost of 0,02 Cent is broken up into 2 Fields when parsing the Data as Comma Seperated Values ...
    Hope this get fixed really soon as it's breaking the whole CDR ... :-/

    Example:
    03.12.2015 15:59:14 Call 8506,0000000000000D28_536,0.00:01:36,2015.12.03 14:57:35,2015.12.03 14:57:37,2015.12.03 14:59:14,TerminatedByDst,Ext.1000,053123354,1000,10000,053123354,,,,,0,02,0,03,ÖSTERREICH FESTNETZ,Chain: Ext.1000;053123354;,Extension,Line,,Andreas,053123354,

    As you can see - bill-rate and bill-cost is braking the CSV ... it should be 0.02,0.03 instead of 0,02,0,03

    Thx, bye from Austria
    Andreas Schnederle-Wagner
     
  2. Futureweb

    Futureweb New Member

    Joined:
    Jun 29, 2015
    Messages:
    163
    Likes Received:
    14
    As I heared this may be because we use 3CX on German Language Server ... I guess it would be best to ignore the Windows configured Decimal Sign and just always use . for seperating Decimal Values?!? As , will break the CDR Output ...

    When configuring Call Costs within 3CX you already ignore the Windows configuration and always use .
    Just ignore it here too ... ;-)

    Andreas
     
  3. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,367
    Likes Received:
    83
    I have spent the past few days trying to replicate this on Windows OS installations for different languages and different default decimal symbols but the result is always the same.

    Could you check the files that are generated in C:\ProgramData\3CX\Instance1\Data\Logs\CDRLogs, open them with a text editor, not excel, and see if the values there for the billing costs are with a '.' or a ','?

    If you do not see any files there try changing the CDR export method to "1 file for all calls" or "1 file for each call".
     
  4. Futureweb

    Futureweb New Member

    Joined:
    Jun 29, 2015
    Messages:
    163
    Likes Received:
    14
    Hi Nick,

    on my Machine it's the same if I use File Based CDR or Client / Active Socket configuration.

    File Based:
    Socket Based:
    As you can see the bill-rate and bill-cost is braking the CSV Output here! :-/

    System: Windows Server 2012 R2 Standard
    Locale: Österreich
    Language: Deutsch (Österreich)
    Number Decimal Sign: ,
    Currency Decimal Sign: ,

    Hope those Information help you find the Problem.

    Andreas
     
  5. Futureweb

    Futureweb New Member

    Joined:
    Jun 29, 2015
    Messages:
    163
    Likes Received:
    14
    NickD_3CX presented me with a Solution for this Problem:

    Hope this will help if someone also stumbles across this problem! ;-)

    Even if I still hope they will change this behaviour - as it will ALWAYS break CDR CSV Output ...

    bye from snowy Austria
    Andreas
     
  6. Futureweb

    Futureweb New Member

    Joined:
    Jun 29, 2015
    Messages:
    163
    Likes Received:
    14
    Changelog 3CX Phone System v15.5 BETA, Build 15.5.715.6, May 2017
    - Fixed CDR outputs will log call costs with commas

    Does this mean this issue is finally fixed in V15.5? ;-)
    Can't wait to comment out the Regex which fixed that behaviour in my active CDR Socket Server ... :D

    Andreas Schnederle-Wagner
     
Thread Status:
Not open for further replies.