Problems after upgrade pi3 and v16 to pi4 and v18

[computerforceNZ]

Hi all

I have recently done a few upgrades of systems running v16 on a pi3 to v18 running on a pi 4.

My process has been to backup the v16 pi3, install 3cx on the pi4 and then to restore the backup.

I have found that this works to a point, but I almost always need to factory reset and then reprovision the phone handsets (Grandstream 2612P). This is not too bad on a small site, but I am about to do a much larger site and would prefer not to have to re provision all the handsets.

Has anyone else had this problem and found a resolution?

Thanks in advance.

 

[cobaltit]

So I will preface this by saying that 3CX no longer supports the Pi anything beyond v18 Update 2 I believe for 3CX server. Still works fine for the SBC.

Assuming IP stays the same and you restore a backup, there should be no need to reset/re-provision. And if the IP did change but you were using DNS for the provisioning URL there should be no need to reset/re-provisioning. And ultimately if you changed both IP and DNS option 66 can usually save the day and is fine. The only time you should factory reset the phones is if the provisioning method is changing, in particularly STUN <--> SBC swaps can be a little weird.

 

[computerforceNZ]

Thanks for the input.

The IP stays the same. What happen is that the phones initially seem ok but afer a few minutes go to 'account not registered" and the re provision is the only way I have found to re enable them.