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

EPM is not updating Yealink T46S firmware to latest version

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 16.0.40.1
    • Fix Version/s: None
    • Component/s: Endpoint (Commercial)
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      16.30.0
    • Distro Version:
      12.7.8-2302-1.sng7
    • Distro:
      FreePBX Distro

      Description

      I know this worked in the past, but I seem to be having trouble now.
      FreePBX 16.0.40.2 (it would not let me specify this above because it says that it doesn't exist)
      EPM 16.0.80.7 (with current commercial license)
      Under EPM, Firmware, I have Firmware Slot 1 as 1.22. That says it includes 66.86.0.15 as the latest supported Firmware for Yealink SIP-T46S. Under Template/General, I have tried both leaving it at "Recommended" and saying to use "Slot 1".
      No matter what I do, it is not updating the firmware of the Yealinks that I have in EPM. This includes phones running 66.86.0.5 (a fairly recent version compared to the supported 66.86.0.15) and phones running 66.84.0.15.
      All phones are connecting fine, but are just not updating their firmware.
      I am seeing this across multiple FreePBX installations of mine – all with current EPM licenses.
      Am I missing something obvious? Or is there a bug here? Thanks.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                rfmjohn JohnG
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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