DST change

[Alphabetic]

as mentioned above though.. Yealink support have said they've addressed this in the latest firmware.
96.87.0.16

When I use this FW Im still on the wrong time though..

Yealink said

For phones already have this issue, Please try to provision with new DST file:

auto_dst.url= (URL of your AutoDST.xml)

When I look at this parameter on the template it is hashed out.

 

[zeeb]

Correct. You would need to create a custom phone template, copy the file into the provisioning directory, and then delete each phone and re-add it using the custom template.
That’s fine for a few devices — but completely impractical for hundreds of phones.

I’ve attached the new AutoDST.xml from Yealink.

 

[sir116]

A customer's solution:

 

[kathanasias]

3CX support team, it's just a template change! Why don't you fix it? The problem exists since last year!
local_time.dst_time_type = 0 <- it should take the value (1) from 3cx parameteres but it does not.

Then, local_time.start_time should work fine if we set 3/5/7/2 and 10/5/7/2 accordingly to start_hour and end_hour!

I use the default template because when I create new template, I have to update it manually each time.

Also, please add a parameter to disable the screensaver.

Thank you!

 

[NicholasP_3CX]

https://www.3cx.com/blog/releases/v20u5-yealink-firmware-updates/

 

[Alphabetic]

This is such a pain..

is there a way to mass send RPS again?

This is going to be very time consuming

 

[JoshWS]

https://www.3cx.com/blog/releases/v20u5-yealink-firmware-updates/

Hi Nicholas,

Thank you for providing the new firmware update for these phones.

However what i cannot understand is how we are expected as resellers to now factory reset all of our deployed Yealink handsets upgrade to the new firmware and reprovision back to the user. This is not a feasible option. Will this exact same thing happen next year unless the already deployed handsets are factory reset and put onto the new firmware?

 

[NicholasP_3CX]

Hi Nicholas,

Thank you for providing the new firmware update for these phones.

However what i cannot understand is how we are expected as resellers to now factory reset all of our deployed Yealink handsets upgrade to the new firmware and reprovision back to the user. This is not a feasible option. Will this exact same thing happen next year unless the already deployed handsets are factory reset and put onto the new firmware?

You might need to direct that question to Yealink.



Given that the week is almost over the time will be corrected in a few days, and that should give plenty of time to do the necessary actions.

We need to trust the process.

 

[johnmooret2k]

Is it not possible to change the Yealink template on 3CX to allow for local_time.start_time 3/5/7/2 and 10/5/7/2 accordingly to start_hour and end_hour! Then we could reprovision all the phones and it takes the new template?

I don't mean make a custom template, this could be introduced to the official template in v20 update 6?

 

[NicholasP_3CX]

The templates are provided to us from the vendors. If they decide to make the change, it could happen.

 

[jimjim]

I've updated some phones to test the new firmware, after the factory reset,
the phone is blocked and a manual password need to be set on T54W,
after boot, must to connect to the phone web console to set manually the VLAN ID...

the only good thing is that the time is now correct...

So don't update now and don't factory reset if you're updated, this is complete nightmare !!!

 

[Alphabetic]

I've updated some phones to test the new firmware, after the factory reset,
the phone is blocked and a manual password need to be set on T54W,
after boot, must to connect to the phone web console to set manually the VLAN ID...

the only good thing is that the time is now correct...

So don't update now and don't factory reset if you're updated, this is complete nightmare !!!

Tip for you.

Set up DHCP option 66 with your provisioning link and get your users to reset.

Easiest way i've found to do this.

 

[jimjim]

Tip for you.

Set up DHCP option 66 with your provisioning link and get your users to reset.

Easiest way i've found to do this.

yes I know, I din't remember that I've disabled this option on my test VLAN for PxE booting I will test a hard reset on a prod VLAN with some phones to check.