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

Missing res_digium_phone_public rpm for digium phone module

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 13, 15, 16
    • Fix Version/s: 13, 16
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Sprint 63, Sprint 64, Sprint 65
    • ToDo:

      Description

      Missing dpma public rpm for digium phone module to below asterisk versions.

      Asterisk 13 Certified
      Asterisk 15
      Asterisk 16 Certified

      Since we get the above asterisk version listed while running asterisk-version-switch command.

      
      [root@freepbx ~]# asterisk-version-switch        Current version:  Asterisk 18.6.0        (LTS) = Long Term Support | (EOL) = End of Life | (S) = Standard        Press 1 for  Asterisk 13 (EOL)
              Press 2 for  Asterisk 13 Certified (EOL)
              Press 3 for  Asterisk 15 (EOL)
              Press 4 for  Asterisk 16 (S)
              Press 5 for  Asterisk 16 Certified (LTS)
              Press 6 for  Asterisk 17 (EOL)
              Press 7 for  Asterisk 18 (LTS)        Press q to exit and not change your Asterisk VersionPick the Asterisk Version you would like to change to:
      

        Gliffy Diagrams

          Attachments

          1. screenshot-1.png
            17 kB
            Rahul Verma
          2. screenshot-2.png
            9 kB
            Rahul Verma

            Activity

              People

              • Assignee:
                rverma Rahul Verma
                Reporter:
                msanthosh Santhosh M
              • 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.