Upgrade to v12.5 has changed my timezone

Discussion in '3CX Phone System - General' started by billthenerd, Jan 25, 2015.

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

    Joined:
    Jul 3, 2014
    Messages:
    19
    Likes Received:
    1
    I upgraded to 3CX Phone Server Pro v12.5 a couple of days ago, and I have noticed a problem for the first time.

    It appears the timezone for the 3CX Phone Server database has been changed.

    All of my previous call history records are now reporting the wrong date/time for my timezone!

    Previous to the upgrade, all the call date/time records in the postgresql database were being stored in my local timezone (UTC+12).

    Now they seem to be being stored in UTC (+0) time instead.

    This has broken the 3CX Call Reporter and some of my custom reports as well.

    Please help! How do I fix this?

    Should I try to update all the previous timestamps to match the new timezone?

    I think the only postgresql tables affected that matter are calldetails, callhistory2 and callhistory3.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. pj3cx

    pj3cx Active Member

    Joined:
    Aug 1, 2013
    Messages:
    645
    Likes Received:
    1
    Hi there,
    Could you kindly open a support ticket so we can investigate this issue further?
    That being said, custom reporting using direct access to the database is not supported. You should rather use the export functionnality of our web report, to excel format for example.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. billthenerd

    Joined:
    Jul 3, 2014
    Messages:
    19
    Likes Received:
    1
    Sure Pierre. How do I open a support ticket?

    I don't seem to have access to http://support.3cx.com/
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    2,978
    Likes Received:
    183
    Do you have a support contract? If not, that is required. Otherwise, the 3cx Partner that you bought 3cx from should be able to file the bug report for you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. billthenerd

    Joined:
    Jul 3, 2014
    Messages:
    19
    Likes Received:
    1
    OK thanks Craig, I'll approach them.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. billthenerd

    Joined:
    Jul 3, 2014
    Messages:
    19
    Likes Received:
    1
    Pierre, our reseller has raised a support ticket for this issue:

    Ticket ID JDL-284-14933

    Looking forward to your response.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. billthenerd

    Joined:
    Jul 3, 2014
    Messages:
    19
    Likes Received:
    1
    Thanks for your reply guys. I decided that rather than reload and lose some of our call history, I ran an SQL statement to update the old, problematic records in PostgreSQL, and that has fixed the problem for me.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.