Yealink t42 stuck on registering process after upgrade from 3cx v16 on a google cloud VPS to v18 on a 3CX hosted modality

[cloudccentereplalimo]

Hello dear 3CX community and experts.

I recently upgraded from v16 to 18. In this change, I also switched from Google hosted on a VPS to a 3CX hosted plan. After this change my desk phones stopped working and are showing "Warning no service" on the screen.

I tried restarting the phones but no luck. Any ideas? Thanks in advance

 

[Nathan@Voxtelesys]

Is the phone firmware up to date?

https://www.3cx.com/docs/phone-firmwares/
https://www.3cx.com/sip-phones/firmware-update-yealink/

 

[cloudccentereplalimo]

Thank you Nathan. According to this URL I have the latest release. https://www.3cx.com/docs/phone-firmwares/

This is what my phones are showing in the status page of their GUI.

Firmware Version

66.86.0.5

 

[Charles_3CX]

Hello dear 3CX community and experts.

I recently upgraded from v16 to 18. In this change, I also switched from Google hosted on a VPS to a 3CX hosted plan. After this change my desk phones stopped working and are showing "Warning no service" on the screen.

I tried restarting the phones but no luck. Any ideas? Thanks in advance

Are you using a 3CX SBC to provision the IP phone? Or provisioning as remote Stun?

 

[cloudccentereplalimo]

Are you using a 3CX SBC to provision the IP phone? Or provisioning as remote Stun?

Thank you Charles. I am using remote Stun. The odd situation is that 3 phones are still registered

 

[Charles_3CX]

I would suggest using a 3CX SBC, as with stun, there are too many network variables to consider, and the 3CX system is designed to be used with a 3CX SBC to provision IP phones remotely.

 

[cloudccentereplalimo]

I would suggest using a 3CX SBC, as with stun, there are too many network variables to consider, and the 3CX system is designed to be used with a 3CX SBC to provision IP phones remotely.

Thank you Charles. I will go ahead and do this:

1) Reset the phone that was already registered (when I had v16 on the Google VPS)
2) Recreate the extension
3) Do the provision tab with SBC instead to STUN

I will get back with the result, thank you.

 

[cloudccentereplalimo]

Charles, thanks for the advice. I was able to get the phones to register after creating the SBC inside each LAN.

This is what I did that allowed me to have my existing phone to re-register again.

1) Create an 3CX SBC (Session Border Controller) on a machine inside the same network as the phones.
https://www.3cx.es/docs/instalar-sbc/#h.w6kcyfq4vxf4
2) On the 3cX management console--> Click the desired extension on Users--> click Phone Provisioning--> switch the provisioning method to 3CX SBC and set the 3CX Session Border controller
3) On the respective Phone go to its GUI --> Go to the account tab==> Enable Outbound Proxy Server and type in the field the LAN IP address where you created the SBC (from step1)==> Click confirm.
4) In the same phone GUI--> Go to the settings tab--> Auto Provision ==> AutoProvision Now (It will show configuration updating... Wait until it finishes thisprocess).
5) Confirm that it shows REGISTERED on the status tab (Same Phone GUI).