Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

DST settings for phone provisioning

Discussion in '3CX Phone System - General' started by MatrixIT-EJBoeve, Oct 28, 2013.

Thread Status:
Not open for further replies.
  1. MatrixIT-EJBoeve

    Joined:
    Oct 28, 2013
    Messages:
    1
    Likes Received:
    0
    Hello,

    Customer is using 3CX with Yealink IP phones but had issues with switching to winter time. In 3CX we found out the date was wrong for the Netherlands (It was set to okt 25, instead of okt 27). However, the date is not a fixed date every year. At this moment we need to update the DST date manually each year.

    Is it possible to change this in 3CX? Instead of a fixed date, I would prefer a user-selectable option for either a fixed date (for those who require that) or a auto-setting 'last sunday of month x'. In the Netherlands it's Always last sunday of okt, and back to summer time on the last sunday of March.
     
  2. jasit

    jasit New Member

    Joined:
    Feb 12, 2013
    Messages:
    172
    Likes Received:
    1
    We have the same problem in Canada it is also a fixed date, but the first week in November.

    you can modify the yealink template so that it uses the end of the month schedule instead of the specified date that 3cx provides.

    We also have the problem that we have phones that are in a different timezone connected to our server and they are using the server time instead of their own local time. It would be nice to have a if statement based on extension group so that I could use different time zones.
     
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,111
    Likes Received:
    329
    Do the Yealink phones not each have their own internal settings for DST, and time difference from UTC? The devices I've used allow for internal time settings to accommodate a location anywhere in the world, and input of a time server, independent of the PBX. Some might not have the flexibility (older models) for specifying which Sunday in a moth to change, and be limited to a specific date. Of course, when the set it provisioned from 3CX, and not manually, the template must be where the setting is changed.
     
  4. layton

    Joined:
    Jan 18, 2011
    Messages:
    47
    Likes Received:
    3
    Yealink provides an AutoDST.xml file with their provisioning kit. This xml file has the correct DST rules for each time zone (including relative effective dates - e.g. 1st Sunday of Nov) instead of fixed dates. Simply make sure this file exists in your provisioning directory, and then in your Yealink template, make sure you have an entries for:

    local_time.summer_time = 2

    and

    auto_dst.url =http://%%pbx_ip%%:%%pbx_http_port%%/provisioning/%%PROVSUBDIR%%/AutoDST.xml

    In my templates, the first line is under the Time Settings section, and the second line is under the Local Contact/DST Time/Dialnow Rule/Replace Rule section. For the second line, obviously you'll only have the %%PROVSUBDIR%%/ level in the path if you're running v12.

    The AutoDST.xml file should be correct for each time zone - but you can always edit it if you need to tweak it.

    Yealink's default DST (summer_time) setting is 2 (Automatic). But that requires the AutoDST.xml file which isn't included in 3CX's Provisioning folder.

    I know this works with the Yealink T4x series phones - not sure about the other series.

    As for jasit's question about phones in other locations. If these are remote extensions that are still being provisioned, you'll have to manually set the time zone in the phone interface. Right now we can only set the time zone for provisioned phones globally. Hopefully in the future 3CX will allow us to override time zone settings on a per extension basis to allow for remote provisioned extensions.
     

    Attached Files:

    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.