Notice: New Apple Push Service Requires HTTP/2. Is Your Windows Compatible?

[michelescapini]

Hi,

I just upgraded to the latest version of 3CX to 16.0.5.611.
After the update I received confirmation by e-mail that 3CX "noticed that I'm running 3CX on an unsupported operating system", which is WS 2012 R2 and found out this post.
Will restoring a backup from version 16.0.4.493 will give us a little extra time to plan the upgrade from WS 2012 R2 to 2019 momentarily until November 2020?
Because for now, it seems like the best solution, considering some users working from home due to the virus are using iOS as their main device and upgrading from Server 2012 to 2019 will take some time and physical travel.
Thanks a lot for your help!

Why not move to Debian?
it's free and in the U5 they have solved the bug with exchange contact sync, so Debian it's the best choice

 

[Seskoi]

Hi,

Thanks all for your help!
I'm responsible of the "IT department" at my job (we are 18 employees) on the side, in addition to my account manager role, because I'm considered tech-savvy, but nothing like a real system admin who studied in that field. I built my own computer, made websites, manage Sharepoint, etc. and I do what I can do with research, but sometimes things go beyond my capabilities such in this case I think
I could not see how in 2 days I, alone, could either migrate 3CX to a Debian VM (only used Linux once, I can't remember why, maybe cryptomining) or do a clean install of WS 2019 without risking losing precious data.
I rolled back to a backup of version 16.0.4. While my dashboard still tells my version is 16.0.5.6, iOS users receive push notifications.
This will give me time to either create a virtual Debian machine and set it correctly or to do a clean install of WS 2019 and make sure all of our software keeps running without data loss.

Thanks and stay safe !!!

 

[michelescapini]

@Seskoi i'm a sys admin and it's my job. I'm not a linux guru, but the 3CX linux iso is ready to use.
Moreover the backup&restore of 3cx is platform indipendent (not all sw do this!)
you can do this:
- deploy the new vm with Debian with provisional ip
- take backup of 3cx in windows
- turn off the windows vm
- change ip of debian
- restore backup

If anything go wrong you can always turn off the debian and turn on the windows until you restore the backup!
If you wan't linux and you have 2k19 license you can do a snapshot and upgrade the o.s. (if something go wrong you can revert the snapshot) OR the same step above but with Windows!

i done this steps in our installation for test a lot of times and always everything is gone right

 

[Seskoi]

@michelescapini
Thanks for your reply! This sounds like a safe, effective and cheap solution. I'll look into it.
My only concern is that currently 3CX is on our main server, not a virtual machine. How could I manage to "turn off the windows environment" and change IP to Debian in that case?
Well, you've already helped me greatly, I'll start by creating a Debian VM and install 3CX on it, I'll be back if I meet any problems.
Thanks for the great support!

 

[michelescapini]

@Seskoi you say that 3cx is on a physical server and this server has other functions? then you must use the name dns (eg voip.yourlocaldomain.local) and replace it in all extension to use dns name instead of the ip when they are inside your lan.
once you have done this you can migrate everything to another server with another ip and then change the dns record with new ip, but these operations I have never done (for me a vm a function) therefore it is better that someone who has already changed the ip of 3cx answers without having to rethink the phones and clients.
This are the problem with no VM and more services on same server