3CX Team,
As others have stated in these forums, build 4492 has broken the status functionality in the client. I'm going to go out on a limb here an assume that it's because it requires build 4492 of the server. If this is the case then you should either specify that in your announcement about build 4492 or simply don't make it available until the server is available.
I'm very disappointed that I've just deployed this to a couple of workstations and must now go back and locate a copy of 4393 just to get status working again.
Please advise.
As others have stated in these forums, build 4492 has broken the status functionality in the client. I'm going to go out on a limb here an assume that it's because it requires build 4492 of the server. If this is the case then you should either specify that in your announcement about build 4492 or simply don't make it available until the server is available.
I'm very disappointed that I've just deployed this to a couple of workstations and must now go back and locate a copy of 4393 just to get status working again.
Please advise.
