Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-8621

EPM time zone problem for Brazil

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 12
    • Fix Version/s: None
    • Component/s: Endpoint (Commercial)
    • Environment:

      SchmoozOS, FreePBX 12 with all modules and system packages updated

    • ToDo:
    • Distro Version:
      12
    • Distro:
      FreePBX Distro

      Description

      When using the commercial EPM I select timezone GMT-3 (for Brazil) and enable DST but then the file generated for yealink phones (and potentially other brands as well) show time zone for Argentina/Buenos Aires (which is also GMT-3).

      However, while both are GMT-3 the DST rules are very different for Argentina and Brazil so right now all my phones are off by one hour and there is no way I can fix it except by making an edit to the basefile.

      Also note that having an entry for "Brazil GMT-3" will work for me but not for all people in Brazil because while most of Brazil territory is withing the GMT-3 time zone, the DST rules are different for different states.

      I really think EPM tried to take a shortcut on the timezone settings but it won't cut it, I would much rather choose from a list of time zone names like "America/Sao Paulo" like you find in many linux os installs, that is the only way I see that can make it work properly for everyone.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                datorherren United States
                Reporter:
                mbello Marcelo
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.