You are closer to GMT. Those in the Americas have had this problem for 11 days. This is on ALL servers with SP3 installed in America continents and Hawaii and most likely anybody more than 3 hours from GMT.No issues over here.
All my customers are running 3CX V15.5 SP3
I suggest to backup, uninstall, re-install, restore to solve your issue.
As simple as that. Just 5 minutes work for you.
We call this... service from the house. No charge, right?
User to User - Answers are provided by the community. 3CX does NOT provide technical support via this forum. Commercial grade support should NOT be expected
don't waste your time here
Let's hope they will listen these recommendations.I think 3CX forget sometimes that we have to give answers to frustrating customers as to why something is not working and when it will be fix.
Another new feature could be toggle button where admins in different time zones could easily switch between local and UTCI hate to say it too but I agree, I don't really care about the new features. Yes they are nice to have, but something like this is a core component of the software and it should always work and if its not working should be fixed ASAP. Its very disappointing that it is taking so long.
Would be nice to be able to have admin login via either AD, AAA or Radius servers so we can track who is logging to our customer's servers.
Have you checked the call logs before 4PM? These are the call logs on the main page.Wow... I'm in Southern California, and my call logs are fine on "Professional Annual 15.5.8801.3" running the Linux distribution. No logging can be a big headache for call centers, legal and otherwise.
Have you checked the call logs before 4PM? These are the call logs on the main page.
Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.