3CX Mismatch IP Causing Crash

[sclark10]

Hello all and thank you for your time.

We recently had a late phone upgrade that had to be done. We were still on v12 and had to go through the process to get it up to v15.5. Everything went well, except since the upgrade the 3CX system gets a mismatch IP and then the computer struggles to get it corrected and we are left with a CPU overload that is only fixed by hard reboot. I have done all sorts of diagnotic tests on the physical machine and there are no issues with it, even the NIC is showing healthy and fully operational. When I check logs, event viewer and 3cx logs, there is nothing stating why overload happens or why the management console is showing a mismatched IP. It is static set as well. Any assistance would be greatly appreciated!

 

[AWS2P]

So now your pbx is V15.5 sp6?
it was not affected by any network problem or crash before update

 

[sclark10]

Yes, that is correct.

 

[AWS2P]

if i was you , i'll try a v15.5 complete backup (FQDN+ Licence), keep it safely out of 3cx , then uninstall, reboot, reinstall from scratch, restore

you don't want to update to latest V16 Sp2 ?

when you speak about static IP , is it LAN , WAN, both ?

 

[sclark10]

Do you think maybe some corruption occurred during the installation? The unfortunate thing is that I won't be able to do that until after hours.

 

[sclark10]

when you speak about static IP , is it LAN , WAN, both ?

LAN, it is a public IP that the system is statically set to.

 

[AWS2P]

I had a PBx in the past that worried me randomly, without ever finding the cause. this machine had been updated from v11 to v14. I got tired of looking in vain, I got a backup and I reinstalled everything from scratch. it takes 15 minutes, since the machine works without worries. So from time to time, remaking everything eliminates problems

 

[sclark10]

Ok, I will take your advice and give that a shot tonight. Thank you for your time and advice!

 

[AWS2P]

your pbx is on dedicated computer?
running on Windows 10 Pro 64?

 

[sclark10]

Yes it is on a dedicated, not a server. It is running Win 7 64.

 

[AWS2P]

your PBx is on premise?
Behind Nat router ? or directly exposed on internet with static public IP?

ok , so now W7 is no more supported for 3CX, you need linux Debian 9 or Windows 10 pro 64

What 3cx licence do you use ? Free , commercial, std, pro, ent ?

 

[sclark10]

For v15.5? I know it is that way for v16. How could 15.5 be supported before and now all the sudden not?

 

[AWS2P]

It was working but no more 3CX supported (W7 is end of life even on microsoft side)
https://www.3cx.com/docs/supported-operating-systems-previous-versions/

if your idea is to update to latest V16 SP2, then 2 choices

1. Change to new W10 or debian computer (64 both) (you can scratch W7 and use iso linux from 3cx)
2. upgrade freely your W7 to W10 and reinstall 3Cx using your backup from V15.5

 

[sclark10]

I wonder why the change? That is so infuriating!

 

[AWS2P]

between you and me, this computer is not a fresh one, if it run with 3cx since V12, Os W7, in French we call this "vieux coucou" that means is not completly out of service but is EOL.

For now your 3cx use has perhaps increased and you need new computer with more and actual hardware requirement to run with confort and for next years .

Like i said you can switch freely your key licence from W7 to W10, when you install W10 just answer you don't have a key, when install is ended, give the W7 key to activate.
You just need to take care which install of w10 you choose, it had to be the same it was for W7
example you had 7 home version, so you need to install w10 home

Nota: Home versions are not supported even W10

 

[sclark10]

Hello,

I wanted to follow up with you, just so you know what happened. We reinstalled the 3CX system, but still experienced the issue. Come to find out, it was a driver for the Intel RST for the 2 drive raid we have in that system. Once the driver was updated, everything has been great! I want to thank you again for your time and your help!