Solved Today Call Log Disappeared after today update.

[THCO]

THCO,

Thanks for that, confirmed working on another PC, different network also.

Little things that we forget to check.

I assumed it was similar to the recording issue in the previous build.

I could never get the recording bug fixed until I upgraded to sp3.

 

[kedesignz]

I could never get the recording bug fixed until I upgraded to sp3.

Same, it was a bug.

 

[sip.bg]

sip.bg,

Thanks for the info; it was from a public release link.

Is 155.6354.2 a SP2 final release, non-beta; this is what we had previously.

Yes, this is SP2 final release.

 

[kedesignz]

jimbo59,

Maybe you want to update your initial post, to include the fix, so others won't have to scroll through the thread.

 

[kedesignz]

jimbo59,

My apologies; however, thanks for making it easily accessible to others.

 

[AH2]

I wanted to wait until today to see if it would show yesterdays logs, and yes, it shows yesterday logs as of today logs. Some probably messed up on the table filtering ...

Probably will get fixed next update.

 

[AH2]

I logged in from a different computer and now call logs are working. So maybe try clearing browser cache to see if that fixes it.

Still the same issue with 2 different servers. Cache cleared.

 

[THCO]

Still the same issue with 2 different servers. Cache cleared.

Im still having issues to. Even from other computers. What is strange is I logged into the console from a macbook pro using chrome though a vpn last night and the log was correct. Today Im on a different macbook pro and I am local to the the server and I cannot get the call logs to show for today. I am not sure what is going on but I will investigate a little further.

 

[kedesignz]

AH2 & THCO,

Same issue(s) as of yesterday; so can we say clearing the cache is a temporary fix until resolved by 3CX Dev?

 

[jimbo59]

Clearing the cache didn't work today.

 

[THCO]

AH2 & THCO,

Same issue(s) as of yesterday; so can we say clearing the cache is a temporary fix until resolved by 3CX Dev?

Clearing cache did not work for either.

 

[AH2]

And they seem to have an error at the console at /#/app/call_log

 

[AH2]

No update on this ?
Come one guys, at least a reply of acknowledgement and some sort of hope for a solution, but no.

Perhaps I should note that I am a paying customer and still have a valid license with support.
Thanks.

 

[big.LITTLE]

We have been told by our supplier that SP3 is 'actually' beta version.

But we have upgraded our main 3CX and had this issue, but strangely after running for a day, our call log appears.

 

[jimbo59]

No, SP3 is released and it has problems with the call log date. On the West Coast at 1600 the log is populated for the day, but before then it is full of the previous day's call logs.

 

[Sopock]

Are these public releases not tested for QA?

There is even in Windows notable bug awaiting hotfix

I run it on a Debian desktop and Wireshark runs here just fine here also. I can even run many Windows programs with Wine. I'm a Windows engineer since v1.0, but I now hate it. My Windows Insider builds do nothing but green screen my PC now, so it now runs Debian with Gnome.
I only wish we had a linux client for 3CX.

 

[jimbo59]

bump

 

[YiannisH_3CX]

Can you please let me know the know the following so we can further investigate the issue:

• The timezone of the PBX server.
• Operating system the PBX is running on
• How are you accessing the server (directly from the server, RDP, Management console from a remote location etc.)

 

[jimbo59]

Can you please let me know the know the following so we can further investigate the issue:

• The timezone of the PBX server.
• Operating system the PBX is running on
• How are you accessing the server (directly from the server, RDP, Management console from a remote location etc.)

1. Pacific Time
2. Debian 9
3. All of the above

I can give you the permission to access the server.

As I've stated numerous time, the logs appear at 1600 for the current day, but until that time all we see are yesterday's logs.

This is happening on 2 servers both on Debian both on West Coast.

I'm a programmer and my guess is it's a filter on the call log that is not correct. The calls and times and dates are there and correct, but they don't display in the log until after 1600.

 

[THCO]

1. Central Time
2. Microsoft Windows Server 2016
3. All of the above.