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

Call Forward unconditional and noanswer incorrect in UCP

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 12
    • Fix Version/s: None
    • Component/s: UCP (User Control Panel)
    • Labels:
      None
    • Environment:

      Freepbx 6.12.65-24
      UCP 12.0.0beta46
      Call Forward 12.0.5

    • ToDo:

      Description

      Call forward unconditional and call forward no answer are incorrectly shown in UCP, they are swapped around.
      If I set call forward from phone using *52 (no answer/unavailable) and then look in UCP it shows as unconditional call forward
      whilst
      *72 unconditional call forward shows up as unavailable in UCP
      *90 Call forward busy shows up correctly.

        Gliffy Diagrams

          Attachments

            Issue Links

            is duplicated by

            Bug - A problem which impairs or prevents the functions of the product. FREEPBX-8661 Free PBX User Portal Issue

            • Minor - Minor loss of function, or other problem where easy workaround is present.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. FREEPBX-8310 UCP displays *72 forward as "Unavailable"

            • Minor - Minor loss of function, or other problem where easy workaround is present.
            • Closed

              Activity

                People

                • Assignee:
                  tm1000 Andrew Nagy
                  Reporter:
                  byteguy byteguy
                • 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.