Issue registering Yealink W52P phone

[DavidHodgson]

I have just migrated a customer's telephone system from on-premises (v16 running on Windows 10) to Azure (v18 running on Debian).

We have a Yealink W52P Base Station and one cordless phone; both were working OK when locally provisioned to v16 running on-prem. After the migration we cannot get the extension to register on the base station.

We have factory reset the base station and phone. Set up the base station under FXS/DECT in 3CX Admin Console. Logged into the base station and entered the provisioning link provided in the FXS/DECT section, selected to Auto Provision. This is all OK, the password of the base station changes to the one set in 3CX and I can log in, we can see the extension under 'Account 1' with all the correct settings for that extension (i.e. register name, password, label, and display name) but the status is Register Fail.

We are provisioning using Direct SIP, firmware of the base station has been updated to the latest provided by Yealink for 3cx.

Nothing I have tried seems to work and I cannot register the extension. Could anyone offer any advice?

Thanks

 

[JohnS_3CX]

Alternatively, consider installing a 3CX SBC at the customer site. It's more secure, and does not have the requirements mentioned above.

PS: Also visit this site, click on "Software" and make sure your device is running the correct firmware version https://www.yealink.com/products_48.html

 

[Saqqara]

Under options for the extension may sure 'Disallow use of extension outside the lan (remote extensions using Direct SIP) is unticked

 

[DavidHodgson]

Alternatively, consider installing a 3CX SBC at the customer site. It's more secure, and does not have the requirements mentioned above.

PS: Also visit this site, click on "Software" and make sure your device is running the correct firmware version https://www.yealink.com/products_48.html

Thanks,

Already checked all of that stuff, we are not installing a SBC as it's only a few phones and customer does not want the hardware running.

Bit that does not make sense is separate SIP ports for all phones, we have many customers running in this same scenario without SBC and they are all default to 5060 and they all register fine. In fact the other Yealink's at this site have registered fine using Direct SIP.

 

[Alphabetic]

Have you opened port 5060 to the world?

 

[DavidHodgson]

Under options for the extension may sure 'Disallow use of extension outside the lan (remote extensions using Direct SIP) is unticked

View attachment 29079

Thanks, that's already been disabled.

 

[DavidHodgson]

Have you opened port 5060 to the world?

Default 3CX Deployment Wizard stuff in Azure. Strong passwords in place on all extensions and all the security defaults in place in 3CX

 

[Alphabetic]

What about blacklisted IPs?

 

[DavidHodgson]

What about blacklisted IPs?

Nothing blacklisted and I have whitelisted the IP of the customers site

 

[Alphabetic]

Can you do another firewall test

 

[JohnS_3CX]

Bit that does not make sense is separate SIP ports for all phones, we have many customers running in this same scenario without SBC and they are all default to 5060 and they all register fine. In fact the other Yealink's at this site have registered fine using Direct SIP.

- You are troubleshooting at this stage so please try doing so regardless. Add unique ports for the W52 SIP and RTP, then forward them at the customer's site then reboot the device. The fact that the others happen to work is not sufficient to guarantee that this one will work.

- Ensure the device has it's DHCP address reserved to avoid losing the forwards.

- Ensure SIP ALG is also disabled at the customer site.

- Ensure the firmware is 100% matching the one on the page I shared above.