Solved Accidentally Rejected a Phone

[Colin911]

Hello. I accidentally rejected a phone in the system manager and now can't get it back on the list. I have unplugged it and even factory reset it but can't get it up again like some others have posted about. Is there a list of rejected phones (not phone calls) where I can re-enable it?

Using V15

 

[eddv123]

Usually plugging it back into the network switch or a reset should be enough to get it back up. Have you checked the IP blacklist to check it hasn't been stuck in there ? are other phones working ?

What phone model and firmware is it ?

 

[Colin911]

Nothing in the blacklist. Will try giving it a new DHCP address.

 

[Colin911]

new IP did not work. Had to go to the phone to give it the Provisioning server of the 3cx PBX. taht seemed to do the trick

 

[eddv123]

You should not need to do that if it is on your local LAN subnet, unless of course it is phone which is EOL or not "preferred" supported: https://www.3cx.com/sip-phones/

What is the phone brand and model ?

 

[Colin911]

GXP1760W

 

[Lee Cramman]

Should work without issues.

I have, in the past, found myself unable to get PNP to work because I forgot I had accidentally registered the phone with an error in it's config and then forgotten to delete it again before trying PNP.

 

[eddv123]

Config would do that yes.

There was also an "old" issue where to get Pnp working you needed to run the firewall checker first, weird but this has been solved to my knowledge.

 

[YiannisH_3CX]

Hello @Colin911

Glad to see you were able to provision the phone. To see if this was a phone issue or if the PBX is not listening to the multicast group you can follow this guide: https://www.3cx.com/docs/plug-and-play-ip-phone/

There was also an "old" issue where to get Pnp working you needed to run the firewall checker first, weird but this has been solved to my knowledge.

The solution actually was to restart the SIP service. Running the firewall checker resulted in the SIP server being restarted.

 

[eddv123]

The solution actually was to restart the SIP service. Running the firewall checker resulted in the SIP server being restarted.

@YiannisH_3CX thanks for the clarity, glad its solved now but I guess worth noting in the off-chance partners are using an older 3CX version.