It appear 3cx phone provisioning gets confused when
They can be made to show for provisioning by either
The above behavior was repeated on several occasions. Which suggests perhaps 3cx doesn't respond when only a phone recently shown to have incompatible firmware is available. No longer an issue for me as the work around is simple if known. Hopefully it will help someone else minimise the time spent provisioning phones or pehaps help 3cx improve the robustness of the provisioning interface.
The following made not difference for me
- Clean install of 3cx v18 Debian on premises, local lan
- Yealink phone with old firmware is connected
- Reset to factory default
- Yealink firmware is updated to a supported version (tested with T53 firmware updated to T54W(T57W,T53W,T53,T53C)-96.86.0.18 then updated to T54W(T57W,T53W,T53,T53C,T54,T57)-96.86.0.23
- phones will not show for provisioning.
They can be made to show for provisioning by either
- Connecting a Yealink T28P phone to the local network (but I assume the improtant feature is a different phone model with compatible firmware) or
- Restarting the 3cx services.
The above behavior was repeated on several occasions. Which suggests perhaps 3cx doesn't respond when only a phone recently shown to have incompatible firmware is available. No longer an issue for me as the work around is simple if known. Hopefully it will help someone else minimise the time spent provisioning phones or pehaps help 3cx improve the robustness of the provisioning interface.
The following made not difference for me
- check the 3CX blacklisted IP
- turn off the "Trusted Certificate" in your Phone setting and then proceed with your configuration process (returning it to the default setting after provisioning)
