- Joined
- Jun 8, 2020
- Messages
- 46
- Reaction score
- 27
Hi,
Having just provisioned 100+ Yealink T46 phones on a Debian 3CX 16 I started to receive a lot of calls all saying the time zone in the display was 1 hour behind.
Thought it was a bit odd as my own Debian 3CX v18 and the same phone did not have that discrepancy.
The timezone on the server was set to: -3:00 Denmark - Greeland (Nuuk)
The phones were all set to use global time zone
Looking in the web interface of a provisioned phone I noticed that the phone had the correct timezone, but no location set. There's an additional dropdown to select various locations within GMT-3.
Setting the location to Greenland(NUUK) in the dropdown yielded the correct time in the display.
Looking at the configuration file for the phone it appeared I could see it was trying to set it as "Denmark - Greenland (Nuuk)", which I'm guessing is unknown to the phone itself.
Comparing the yealinkT4x.ph.xml files from between the v16 and the v18 showed that the TimeZoneName was correct in the v18, Greenland(NUUK), but incorrect in v16, Denmark - Greenland (Nuuk).
Created a custom template with the correct TimeZoneName matching what was available in the dropdown and reprovisioned all phones - all is good now, but it would be great to have the v16 template updated in case anybody else runs in to that issue.
Original

Custom

/mikkel
Having just provisioned 100+ Yealink T46 phones on a Debian 3CX 16 I started to receive a lot of calls all saying the time zone in the display was 1 hour behind.
Thought it was a bit odd as my own Debian 3CX v18 and the same phone did not have that discrepancy.
The timezone on the server was set to: -3:00 Denmark - Greeland (Nuuk)
The phones were all set to use global time zone
Looking in the web interface of a provisioned phone I noticed that the phone had the correct timezone, but no location set. There's an additional dropdown to select various locations within GMT-3.
Setting the location to Greenland(NUUK) in the dropdown yielded the correct time in the display.
Looking at the configuration file for the phone it appeared I could see it was trying to set it as "Denmark - Greenland (Nuuk)", which I'm guessing is unknown to the phone itself.
Comparing the yealinkT4x.ph.xml files from between the v16 and the v18 showed that the TimeZoneName was correct in the v18, Greenland(NUUK), but incorrect in v16, Denmark - Greenland (Nuuk).
Created a custom template with the correct TimeZoneName matching what was available in the dropdown and reprovisioned all phones - all is good now, but it would be great to have the v16 template updated in case anybody else runs in to that issue.
Original

Custom

/mikkel