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

Outgoing route using timegroup regardless config

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not an issue
    • Affects Version/s: 14
    • Fix Version/s: None
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
       11.25.1
    • Distro Version:
      12.7.3-1707-3.sng7
    • Distro:
      FreePBX Distro

      Description

      I have a time group, used elsewhere.
      My single outgoing route marked "permanent" and was working fine till yesterday. My users told me "no outgoing calls".
      My outgoing route suddenly stoped working:

      1. my outgoing route marked "permanent"
      2. open Applications -> Time conditions
      3. click Linked Item "Time Group" 
      4. GOT AN EMPTY TIMEGROUP IN USE BY MY OUTGOING ROUTE (see attached screenshot)

      route actual behavior: permanent route setting are ignored like I would selected my 08:00-18:00 time group

      that single time group used in time condition in INBOUND routing and working fine, it is 08:00-18:00 for incoming call routing
      workaround: make new time group 00:00-23:59 and assign it to my OUTGOING ROUTE

       

      P.S.: cannot select "Outbound routes" in Components when submitting this issue

        Gliffy Diagrams

          Attachments

          1. timegroup.PNG
            33 kB
            Dmitriy Barankov

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                expelliamus Dmitriy Barankov
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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