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

Can't submit inbound route page

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 15
    • Fix Version/s: None
    • Component/s: Core - Trunks/Routing
    • Labels:
      None
    • Sprint:
      Sprint 64
    • ToDo:

      Description

      core 15.0.12.90

      First report: https://community.freepbx.org/t/a-route-for-this-did-cid-already-exists/79259

      With current stable version of core, editing an inbound route and attempting to submit the page fails with this error:

      A route for this DID/CID already exists! => xxxxxxxxxx/

      Rolling back to 15.0.12.89 will work around this issue:

      fwconsole ma downloadinstall core --tag 15.0.12.89

        Gliffy Diagrams

          Attachments

            Issue Links

            is duplicated by

            Bug - A problem which impairs or prevents the functions of the product. FREEPBX-23022 Inbound Route Edit Broken if CID field is empty/blank

            • 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-23122 Modifying an inbound route gives error inbound route already exists

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

              Activity

                People

                • Assignee:
                  mbrooks Matt Brooks
                  Reporter:
                  lgaetz Lorne Gaetz
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    NextupJiraPlusStatus

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