1st January

[Jason Hayes]

Hi

Again as last year, it appears 3CX Holidays ignored today.

25th and 26th of December worked and calls to our Queues were directed to our closed messages, but today (as in previous years), it kept our Queues open.

The holiday today was configured correctly....



I didn't test today as expected it to work (stupid I know).

All calls to our Queues are showing abandoned calls today....

 

[accentlogic]

We have this issue reported by one client so far. Changing the schedule from Jan 1 Every Year to Jan 1 2020 cause the system to use Closed mode.

A spot check of several other systems using Every Year were all fine and calls routed to the Out of Office option.

 

[bbaker73]

I had a report of this as well, holiday was set for January 1 every year. It did not work all calls went to queue instead of Holiday. However 12/25 set for every year worked fine.

 

[YiannisH_3CX]

Can you please provide the versions of the systems that were affected as well as if the systems were Windows or Debian?
Also please mention your timezone and we will try to replicate the issue. We did not encounter the issue in all the systems we tested so we need to find the common denominator to see what caused the issue.

 

[bbaker73]

16.0.3.676, Windows, -6:00 US Central

 

[Jason Hayes]

Can you please provide the versions of the systems that were affected as well as if the systems were Windows or Debian?
Also please mention your timezone and we will try to replicate the issue. We did not encounter the issue in all the systems we tested so we need to find the common denominator to see what caused the issue.

This happened last year, I sent 3CX screen shots and logs via this forum and messages. We are using Debian, V16.0.676, Time Zone "0:00 United Kindom (London)". I can send you a Verbose log as we currently have it turned on trying to capture another issue with have with failed call backs going into a loop. As others have said if you add it as a "Single Day", it works, it just doesn't like is set as "Every Year". The 25th December, 26th December as "Every Year" works, it is just an issue for the 1st January.

 

[accentlogic]

Ours was v16.0.4.493 on Debian, -6:00 US Central time. Same as all of the other systems we spot checked that did not have the issue.

 

[Matthew Kaye]

Note also had this issue and all of our instances are hosted 3CX at lightsail using 3CX Version 16.0.4.493

 

[accentlogic]

I did notice that the pbx with the issue was the active instance in failover mode.