3CX not giving warning about IP change after reboot. Phones not registering.

Status
Not open for further replies.

Stulander

Customer
Joined
Aug 28, 2020
Messages
22
Reaction score
3
As per this thread: https://www.3cx.com/community/threa...th-a-different-ip-address.115067/#post-533069

I've changed the static IP of my 3CX install by editing etc/network/interfaces.

3CX did not give a warning about an IP address change after reboot. In Settings > Networking settings in the 3CX console, the network interface card has the correct IP address selected.

Of about 40 phones, only 5 were registered this morning. Last night when I made this change, all phones were correctly registered. They have unregistered overnight. Most do not appear in the 3CX console. After rebooting phones, they do appear. I noted the IP address of one of the non working phones, so I could register it to the correct user in the dashboard. This then gives me the password for the phones web page. After logging in, I noticed the registrar address was the OLD IP address of the 3CX server. Presumably this is because I did not get a prompt from 3CX about the IP change, and some parameters in 3CX are incorrect and set to the old IP.

I have no idea why about 5 phones are registering correctly, mine included, other than the registrar/outbound proxy/conference server settings on the phone web page are correctly shown to be the new IP.

UPDATE:

It appears rebooting the phones makes them appear in the console, so I'm asking everyone to reboot their phones. After I try and assign the phone to the first extension in the list, 3CX tells me the extension behlongs to a different extension. This allows me to assign the phone to the correct extension, and access the password for the phone's web UI, and update the registrar IP manually so the most important depts (I.e. sales, marketing) have working phones.

UPDATE 2:

I realise now I can simply go to Users > Select user > Phone provisioning to get the phone web page password. Am stressing and not thinking things through entirely.

Any help appreciated with explanations for this behaviour and a better/quicker way to resolve it.

Thanks
 
Last edited:
  • Like
Reactions: nub
As per this thread: https://www.3cx.com/community/threa...th-a-different-ip-address.115067/#post-533069

I've changed the static IP of my 3CX install by editing etc/network/interfaces.

3CX did not give a warning about an IP address change after reboot. In Settings > Networking settings in the 3CX console, the network interface card has the correct IP address selected.

Of about 40 phones, only 5 were registered this morning. Last night when I made this change, all phones were correctly registered. They have unregistered overnight. Most do not appear in the 3CX console. After rebooting phones, they do appear. I noted the IP address of one of the non working phones, so I could register it to the correct user in the dashboard. This then gives me the password for the phones web page. After logging in, I noticed the registrar address was the OLD IP address of the 3CX server. Presumably this is because I did not get a prompt from 3CX about the IP change, and some parameters in 3CX are incorrect and set to the old IP.

I have no idea why about 5 phones are registering correctly, mine included, other than the registrar/outbound proxy/conference server settings on the phone web page are correctly shown to be the new IP.

UPDATE:

It appears rebooting the phones makes them appear in the console, so I'm asking everyone to reboot their phones. After I try and assign the phone to the first extension in the list, 3CX tells me the extension behlongs to a different extension. This allows me to assign the phone to the correct extension, and access the password for the phone's web UI, and update the registrar IP manually so the most important depts (I.e. sales, marketing) have working phones.

UPDATE 2:

I realise now I can simply go to Users > Select user > Phone provisioning to get the phone web page password. Am stressing and not thinking things through entirely.

Any help appreciated with explanations for this behaviour and a better/quicker way to resolve it.

Thanks

Fac reset one of the phones and just test dhcp:

dhcp option 66 http://192.168.2.100/provisioning/????
 
Fac reset one of the phones and just test dhcp:

dhcp option 66 http://192.168.2.100/provisioning/????
I didn't use DHCP option 66. I'm using Snom phones, using PnP method. https://www.3cx.com/sip-phones/snom-710-720-760/

However you have made me notice that the provisioning link for all the phones is still set to the old IP address of .2.100

Can I set DHCP option 66 with these phones and why is the provisioning IP 2.100?

I factory reset my phone and the provisioning URL becomes the FQDN of our WAN IP. WAN registration is OFF for all phones, however if enable WAN registration my phone succesfully registers, although the shared parking BLF doesn't work... why is it using the FQDN for provisioning now?

I have no idea what is happening :D
 
I've changed the PROVISIONING_LINK_LOCAL and PROVISIONING_LINK_LOCAL_SEC parameters from the FQDN to the local IP... hopefully that fixes it after a factory reset of the phones...
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,083
Members
164,900
Latest member
Silent_Guru