Corrupted update for Yealink T23G 44.84.0.180

[REkiert]

Hi there,

I have came across the problem with the telephones with this update installed. Problem is specific to phones with enabled VLAN for PC port. Telephone is displaying "No Service" and you can't open the web console, ping it, also run ping from it e.g. gateway all packets are lost. But computer attached to it is in the right vlan and still working. Only solution I found is reset the phone to defaults, then downgrade to 44.84.0.140 and enable vlan for pc port. It's not ideal when you have almost 50 telephones.

Thank you

 

[JohnS_3CX]

Hello,

Please see here: https://www.3cx.com/community/threads/yealink-t40-series-firmware-issue.135396/

We would recommend you also report this to Yealink Support directly so they can investigate.

 

[Colorado VoIP]

Hi there,

I have came across the problem with the telephones with this update installed. Problem is specific to phones with enabled VLAN for PC port. Telephone is displaying "No Service" and you can't open the web console, ping it, also run ping from it e.g. gateway all packets are lost. But computer attached to it is in the right vlan and still working. Only solution I found is reset the phone to defaults, then downgrade to 44.84.0.140 and enable vlan for pc port. It's not ideal when you have almost 50 telephones.

Thank you

this problem affects most of the yealink line now. it started with the 54W a few months ago, and now that they've released firmware upgrades for most of the rest of the lineup, they all do it. (have a pending ticket open right now with them).

if you allow tagged traffic on your network switch ports, you can enable WAN VLAN 1 and your PC PORT VLAN will work fine. If you block tagged traffic like most do, we all have to wait for yealink to fix this, and 3cx to push it out via the systems (which hopefully all happens soon).

right now we have a client with 80+ phones that all say firmware update and i've cautioned the small quantity of staff (dept admins) at that place to not touch the update button so they don't re-brick their phones.

 

[gbrown100]

I was about to post this too and then found this thread - I ran a packet capture and after picking up an IP address, I see a DHCP Inform and the ACK from the firewall and that's the last traffic that comes from the phone itself, it cannot be pinged. The device in the PC port get's an IP address and functions just fine. I verified this behaviour both using a custom template and by manually adding the VLAN details in in the web interface and rebooting.

Now, if you enable tagged vlan on both the WAN and PC Ports then the phone will operate normally so the issue is when the phone is untagged on the wan and tagged on the PC port only.