Can't configure IP phones - IP blacklisted

[koa_s]

Hi all, having an issue with our IP being blacklisted when plugging a physical phone in.
I am logged in to the web console, navigate to a user and configure an IP phone (Yealink T54W as a router phone), select the model and input the MAC.

Next I plug the phone in to the network, at which point I am logged out of the web console and logging back in gives 'an IP has been blacklisted'.

I can access the web console from my phone on mobile network to make changes but the phone itself cannot autoprovision (I assume due to the blacklisting error).

I have been trying all afternoon to get the phone to register, by logging in to the web interface of the phone, inputting the details from the webconsole (autoprovision url, auth ID, pass) but it always skips downloading the config on boot and shows me a homescreen with 'no service'.

Is there any way to get around the blacklisting issue so we can get this router phone set up?

 

[DimitrisL_3CX]

Hello @koa_s,

Reset the IP phone and make sure that the latest 3CX Phone Firmware is installed on the IP phone
For the SMB solutions, the blacklist is not available and you can contact 3CX Support via ticket or wait for 24 hours for the blacklist to be auto-removed.
Once it is removed, you may provision the IP phone again as per our guide How to Configure Yealink T5 Series

 

[koa_s]

I had made sure the firmware listed was installed before doing so.

Does that mean I won't know if the phone will work for another 24 hours, at which point it could blacklist again?

 

[Alphabetic]

I had made sure the firmware listed was installed before doing so.

Does that mean I won't know if the phone will work for another 24 hours, at which point it could blacklist again?

Correct. You could always take it to your local maccies with a POE injector to use their wifi

 

[SteveITS]

FWIW the last time I set up a Yealink router phone it doesn't work on wireless...one needs to set it up via a wired connection first, then connect to wireless. (side note: 3CX officially doesn't support wireless)

@koa_s Once the public IP is blocked then you have to use another network, or wait it out. Are you using the "connect directly" option when adding the phone?

You could always install the SBC software, but then the phone will connect through the SBC. And of course that still won't work while the public IP is blocked.

 

[herman2232]

This is not a phone issue, more like the system reacting to your network/IP change. When the Yealink T54W plugs in, it’s probably grabbing a new DHCP address or triggering a security rule, and that’s what’s getting your admin IP blacklisted. That would also explain why you get kicked out of the web console right after. Check the blacklist/security log first and remove the current IP if it’s there. After that, reboot everything so both the phone and router get fresh IPs. If it still happens, try giving the phone a fixed IP (or DHCP reservation) before you provision it. That usually stops the system from flagging it again during setup.

 

[bitn2]

This is not a phone issue, more like the system reacting to your network/IP change. When the Yealink T54W plugs in, it’s probably grabbing a new DHCP address or triggering a security rule, and that’s what’s getting your admin IP blacklisted. That would also explain why you get kicked out of the web console right after. Check the blacklist/security log first and remove the current IP if it’s there. After that, reboot everything so both the phone and router get fresh IPs. If it still happens, try giving the phone a fixed IP (or DHCP reservation) before you provision it. That usually stops the system from flagging it again during setup.

This has absolutely nothing to do with the phone's internal IP address. The phone simply needs to be running the correct firmware and be provisioned as a router phone; then this won't happen. It makes absolutely no difference what internal IP address you have or how often you change it.

 

[herman2232]

Yeah that actually makes more sense. I was thinking the blacklist could’ve been triggered by the device joining the network, but if the firmware/provisioning is wrong then that explains it better. Especially since it happens the moment the Yealink T54W tries to provision. I’d probably factory reset the phone first, update it to the recommended firmware, then reprovision it specifically as a router phone again. Sounds more like the PBX security is reacting to failed registration/provision attempts than anything DHCP/IP related.