Solved Yealink T54W unregistered as router phone

[YouKnowWho]

T54W firmware 96.86.0.74
This is the first phone configured for a remote user(testing with a new extension). It's configured as a router phone via the webclient. After rebooting the phone, I was never prompted on the Yealink phone to enter the extension number and a 8-digit one-time PIN. I have tried 2 different T54W with the updated firmware.

 

[Dmitry Yurkin]

Hello, what version of 3CX do you use?

 

[YouKnowWho]

On-prem Debian 18.0 Update 6(Build 908)

 

[YouKnowWho]

Since I don't get the prompt on the handset to enter the extension and the one-time code, could I input the information via the phone's web interface?

 

[bitn2]

Check your firewall. Is the phone allowed to get to the internet?

 

[AramS_3CX]

@YouKnowWho

Can you please check the following:
1. Check if the IP address of the remote side is not blacklisted
2. From Events Logs check if the RPS request for your Yealink MAC address was successfully delivered to the Yealink RPS server. You will see something like this:

3. Try to reset the Yealink T54W phone to the factory settings.

 

[YouKnowWho]

1. IP was blacklisted(due to invalid credentials, since I was trying different settings via the web interface), but I had set it to Allow.
2. Both T54W had been reset to factory settings multiple times.
3. I can ping out to the internet from the phone.
4. I do not see the RPS request on the event viewer.

 

[AramS_3CX]

@YouKnowWho

I sent you a PM.
Please have a look

 

[YouKnowWho]

Thanks Aram.
How do we get Teamviewer going? Is there a different email address i could use to email you the information?

 

[AramS_3CX]

Thanks Aram.
How do we get Teamviewer going? Is there a different email address i could use to email you the information?

Please reply to the PM that I sent.
Only you and I can see that information.

 

[AramS_3CX]

It turns out that the reported issue of YouKnowWho was caused due to expired custom GeoTrust certificates used on PBX.
This is why the provisioning of the Yealink T54W was failing.

This type of issue will never occur on PBXs that are installed using 3CX FQDN where we automatically renew certificates for all our customers.

 

[YouKnowWho]

Thank you Aram. After getting the certificate updated, the issue went away.