Skip to content

Wrong Greeting / Time Condition Behaving Wrong

Symptom: caller hears the after-hours greeting during business hours (or vice versa). Time-of-day routing seems "off."

Most Likely Causes

  1. System clock wrong — Time Conditions use the host clock; wrong timezone or NTP broken.
  2. Time Group hours don't include all expected days — e.g. Monday-Friday does NOT include Saturday.
  3. Manual override in effect — someone hit the override feature code and forgot.
  4. Time Group has lunch-hour split that's wrong — split definitions need TWO rows.
  5. DST didn't update — system locked to standard time.
  6. Wrong destination set on match / non-match — typo in the Time Condition itself.

Diagnose

# Check system time:
date
timedatectl

# Check NTP:
chronyc tracking   # or "ntpq -p"

# Check Time Condition state:
asterisk -rx "database show TC"
# Output shows current state ("matched" / "not matched") and any override.

In the GUI: System Attributes → Time Conditions → click your TC. Look at the Override display — manual override sticks until cleared.

Fix

  • Wrong clock: System Admin → Sysadmin → Time Zone → set correct zone. Verify with date.
  • Wrong NTP: edit /etc/chrony.conf or /etc/ntp.conf to use pool.ntp.org. Restart service.
  • Manual override stuck: dial the Time Condition Override feature code with Reset parameter (default *271<id> toggles, follow with the reset code). Or open the TC in GUI and click Reset Override.
  • Time Group missing days: open Time Group → add a row. Saturday + Sunday usually need explicit rows.
  • Lunch-hour split: TWO rows: 08:00-12:00 and 13:00-17:00, both Mon-Fri. NOT one 08:00-17:00 row.
  • Wrong destination: open the TC, fix Destination matches / Destination non-matches, Submit, Apply Config.

When to Escalate

Behavior is correct for some calls and wrong for others on the same TC at the same time of day. Likely a competing Time Condition or Time Group earlier in the routing chain. Trace the inbound route's full destination tree.