Office hours no longer working

Status
Not open for further replies.

AtlasIT

Free User
Joined
May 12, 2022
Messages
3
Reaction score
0
Hi All,

I am having issues with 3CX ignoring office hours. I updated to 18.0 Build 5 (418) this evening and I can no longer get the office hours to work correctly. The times set worked correctly before the update. I have tried forcing the system into IN, OUT, and Default hours, and I get a response confirming, but any calls come in regardless of the time of day. The time is set correctly on the system. I have also tried setting specific office hours for our trunk, but they do not work. Anyone have any advice or solution?
 
Have you checked the logs. 3CX is pretty good about logging what it is doing and why. You may need to turn the logging up to verbose and then re-create.
 
Hi,
Can you give more informations about your setup please ?
https://www.3cx.com/community/threads/post-in-relevant-category.115838/

Can you describe the scenario of your call ?
  • 3CX Version, Standard Annual 18.0 Update 5 Build 418
  • Server OS, Debian 10
  • Is the 3CX Server Hosted and where? On-premises
  • IP Phone Make/Model/Firmware version, Grandstreams of various flavors
  • Provisioning Method: Local
  • Trunk Provider or VoIP Gateway Make/Model, SIP.US Trunk
  • Has the Firewall Checker passed: YES
  • Are custom Phone Templates being used: YES
Just to reiterate, office hours were working prior to the update yesterday. We updated because of the cert reissues coming on the 30th. As far as a call scenario goes, it is any call before or after business hours just comes through as if we are open. Normally after 17:00 EST, the incoming calls would be passed to our end of day IVR. Now they just come through. I have tried changing the extension, tried a different IVR, tried changing the dial codes for office hours, and tried calling from different phone numbers. We only have one DID and even setting specific hours for that DID does not work.
 
Last edited:
I have tracked down the issue. At some point during the update the "Route to" options under the SIP trunk defaulted to the extension with the lowest number. After changing it back to the correct destinations for in office and out of office, the issue went away.
 
Thanks for the feed back, I'm glad your issue is solved.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet