all phones unregistered

[carlmuck]

On reboot a few extensions are registered correctly, but then then are "unregistered"

16.0.8.9 - Locally hosted on debian.

All worked well for months, now no phones will register. Can call in and all calls are sent to VM.

Where to look?

 

[carlmuck]

More info. Early this AM an unattended update was completed. Now no phones can register.

HELP. How to roll back to the previous "stable" version.

HELP!

 

[carlmuck]

One phone is showing up as "new" (it isn't) but the log files show that 3cx can't create the ROM files for it, nor can it write the Directory.xml file.

This is nuts this thing worked yesterday not the "update" has it f*ck to a fair-thee-well.

 

[carlmuck]

getting more and more annoyed. Now trying to just reinstall the whole pile of crap.

Was working yesterday, now can't even install on to the miniPC. Getting grub errors.

Installed into a Vmware VM but can't get the networking to work CONE test fails, but it worked with the miniPC

tearing my hair out.

 

[NickD_3CX]

Hi there,

If you are in dire need of a swift hands-on solution, I think the best course of action would be to contact a 3CX Partner asap. They will be able to offer personalized help for your and will most likely be the quickest route to a solution if you haven't figured it out already.

What I can say as help is, check the IP Blacklist. This can be found in the Dashboard --> IP Blacklist.
While still in the Dashboard, you can check if all services are running, and also if the Local IP has changed. If it has, there should be an indication in the upper-right corner. In the event that the 3CX IP has changed, it would be best to set it back to the old one, to save you the hassle of having to re-configure your IP Phones.

Now if you are going to continue down the road of moving to a new server, make sure you at least have a backup from your previous server. Then you can use this to restore onto a new server.

About the Firewall Checker failing, that is something you will have to see on the network.

 

[carlmuck]

I will be working on getting a partner, but at the moment I can have users use the 3cx app and get calls on their mobiles.

Yes, after the upgrade all the phones were blacklisted. I cleared that, but the phones could not register. On rebooting the server the phones would register (all green in the extensions page) and then about 30 seconds later the all go red.

The PBX thought everything was ok, all green on the dash board, except "extensions" showed green but "0/11" was also displayed...

The Event Log was not showing any messages. Rooting around in the Instance1 logs I found "registration expires" messages. So the 3cx is seeing the phones, just not talking to them.

I deleted one phone from an extension and it now shows up under "Phones" but i can't assign it to an extension. Again, nothing in Event Log, but the Instance1 logs show that the provisioning process can't create Directory-list.xml or the ROM for the phone.

At that point I just decided to reinstall, hoping that the upgrade broke something that I can change with a re-install. That process got all borked when the 3CX iso couldn't install grub on the XOTOM miniPC (that was running before I tried to do the "official" install).

Second choice was to install into an available VMWare cluster, which installed OK, but now has networking issues, which didn't exist with the QOTOM. I'm assuming it is the complication of having the VMWare SDN addition to the routing infrastructure. I'm re-using the addressing used on the old server for the VMWare hosted 3cx so am surprised that it now is failing.

We can limp along while I get the QOTOM reinstalled (have installed stretch, and an now manually installing 3cx).