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

Calendar evaluation does not work as expected for "empty" calendars.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: No Feedback
    • Affects Version/s: 15
    • Fix Version/s: None
    • Component/s: Calendar, Time Conditions
    • Labels:
      None
    • Asterisk Version:
       16.26.1
    • Distro Version:
      12.7.8-2203-2.sng7
    • Distro:
      FreePBX Distro

      Description

      PBX version: 15.0.23.11 PBX Distro:12.7.8-2203-2.sng7 Asterisk version: 16.26.1
       
      Calendar evaluation does not work as expected for "empty" calendars.
       
      We use a CALDAV calendar (SOGo) for time control, which contains sub-calendars for individual people. The persons enter their times of responsibility in the corresponding CALDAV calendar (desktop) and are then only reached during these times. This has been working successfully for a long time.
       
      Now we have created another calendar (the same CALDAV server) for time control on the same FREEPBX, in a comparable configuration. The test revealed that people were also reached who had no corresponding calendar entry.
       
      We have checked the quite complex configuration (queue, agents as virtual extensions with calendar-controlled FollowMe to bell groups) several times and could not find any errors in it. Some participants were always reached even without a calendar entry, as if their calendar was not being evaluated correctly. For other participants it worked as expected.
       
      It then turned out that the error always occurs when the corresponding calendar (more precisely the sub-calendar) does not yet contain a calendar entry, i.e. it is completely empty. As soon as the first entry is present, everything works as it should. If the entry (or all entries) is deleted again, the problem occurs again immediately. It took us some time to realize this...
       
      Is this an intended or an unintended behavior (a bug or not a bug)? The presence of calendar entries shouldn't matter in the "Calendar Match Inverse" setting, should it?
       
      As a workaround, we created a "dummy entry" in each calendar (laborious in large environments). Can the behavior be changed (corrected) in principle? Alternatively, corresponding tooltips could be displayed "that calendars only work if they are not empty".
       
      Many Thanks.
       

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                yummiweb yummiweb
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Feedback Requested:

                  NextupJiraPlusStatus

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