Every combination here is valid Asterisk, and some of them route calls on days nobody intended. Build or paste your entries and see every day and hour they actually match.
Week days and times only; month day and month are left out here. Asterisk counts the finish minute, so a finish of 17:00 still matches until 17:00:59.
Each one loads into the tool with an explanation and, where possible, a fix.
Including holidays that move but never need editing.
Entries in one time group add up: a call matches if any entry matches. Add Dec 25 to the group that means "open" and the office is open all day on Dec 25, even when it falls on a Sunday. Holidays belong in their own group, on their own time condition.
A holiday time condition only works if calls reach it. Put it before the business hours time condition in the call flow. Placed after, callers on a weekday holiday are already sent to "open".
A time condition can be forced open or closed with a feature code, a BLF key or the admin page. A permanent override ignores the schedule until someone resets it, so a perfect time group changes nothing. A temporary one clears itself once the schedule reaches the state it forced.
Times are checked against the PBX's timezone, or the one set on the time condition, not your office's. A hosted PBX in another timezone runs every entry shifted by the difference.
Usually the time group matches something other than what its entries look like. Asterisk accepts every combination, so nothing warns you. The usual causes: the finish minute counts, a time range crosses midnight on only some week days, a date range crosses into another month, holidays sit in the business hours group, the holiday time condition comes after the business hours one, someone left a permanent override on, or the PBX runs in a different timezone. Paste your entries into the tool above and it flags the ones that live in the entries. The rest are under "Traps a single entry can't show".
Asterisk counts the finish minute. 08:00-17:00|mon-fri|*|* matches until 17:00:59, so a caller at 17:00:30 still reaches the open branch. To close at 17:00 exactly, finish at 16:59: 08:00-16:59|mon-fri|*|*.
If every week day is allowed, a wrapped range like 17:00-09:00|*|*|* covers the whole night. Limit the week days and it stops working, because Asterisk checks the time and the week day separately. 22:00-02:00|fri|*|* matches Friday from 22:00 to 23:59 and Friday from 00:00 to 02:00, but not Saturday morning. Split it in two: 22:00-23:59|fri|*|* and 00:00-02:00|sat|*|*.
17:00-08:00|fri-mon|*|* looks like one stretch, but Asterisk applies 17:00 to 08:00 to each day from Friday to Monday on its own. Saturday and Sunday don't match during the day, and Friday morning and Monday evening do. One stretch takes three entries: 17:00-23:59|fri|*|*, *|sat-sun|*|* and 00:00-07:59|mon|*|*.
Not as one entry. *|*|24-2|dec-jan saves the days and the months as two separate ranges, and Asterisk matches the day range inside every month in the month range, so it also catches Dec 1 to 2 and Jan 24 to 31. Use one entry per month: *|*|24-31|dec and *|*|1-2|jan. Keep holidays in their own time group, on a time condition that calls reach before the business hours one.
Asterisk has no "last day of the month", and *|*|31|* only matches in the seven months that have a 31st. It takes seven entries: *|*|31|*, the 30th in April, June, September and November (*|*|30|apr and so on), and *|*|28|feb plus *|*|29|feb. In a leap year Feb 28 matches too.
Pair one week day with a seven-day range of month days. The 4th Thursday in November always falls between the 22nd and the 28th, so Thanksgiving is *|thu|22-28|nov. The first Monday of every month is *|mon|1-7|*. The date moves every year and the entry never needs editing. For the last Monday of a 31-day month use the 25th to the 31st, so Memorial Day is *|mon|25-31|may. In a 30-day month use the 24th to the 30th.
No. There is no year field, so *|*|3|mar matches March 3 every year. Delete the entry once the date has passed. If that might get forgotten, also set the week day that date falls on. The entry then stays quiet until a year when that date lands on the same week day again, and the tool shows you which year that is.
If you set a start time and leave the finish time blank, FreePBX saves the start time as both the start and the finish. 09:00|mon-fri|*|* matches the single minute 09:00, not "from 09:00 on". Set a finish time.
Four fields: time, week day, month day and month. FreePBX saves a time group entry with pipes between them, like 08:00-17:00|mon-fri|*|*. GotoIfTime() takes the same four fields separated by commas, with an optional timezone after them. * matches anything. Ranges include both ends and wrap around, so fri-mon and 28-3 both work. The finish minute counts through :59, and there is no year.
Times are checked against the PBX's timezone, or the one set on the time condition, not your office's. A hosted PBX in another timezone runs every entry shifted by the difference.
GotoIfTime() on Asterisk 13, 20 and 22, and matched this page on every one. Ranges wrap around, the four fields are checked separately, and the finish minute counts through :59. The saved text was checked against FreePBX 14 and 17's own save code.Tick the holidays you close for, then add them to your entries or copy them. Holidays belong in their own time group.
Dates checked against the date-holidays dataset for every year from 2026 to 2075. Holidays that move with Easter can't be a lasting entry, so they are offered for their next date only: delete them afterward.