VoIP.infoThe independent guide to business communications.
VoIP.info Troubleshooting

FreePBX calendar event does not match or routes the wrong way

Trace one expected transition through source retrieval, local event time, group policy, consumer semantics, generated state and the actual call branch.

Reviewed 2026-10-11FreePBX 17 / Debian 12 editorial baseline; Sangoma Calendar, Event Groups, local, iCal, CalDAV and Outlook OAuth documentation plus FreePBX release/17.0 Calendar source and Time Conditions metadata reviewed October 11, 2026; several interface examples are version-labelled for PBX 14 and installed module behavior remains authoritative; no PBX, calendar account, event, credential, sync, route, generated configuration, scheduler, page or live call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one event, instant and consumer outcome

Choose one authorized event and one expected Time Condition, Follow Me or scheduler action. Record source event identifier, title, start and end with timezone, recurrence or exception, PBX time, selected calendar or group, expected branch, actual branch and one call or action timestamp. Preserve both destinations and avoid editing the event while collecting evidence.

Classify the first symptom: the source event is absent, remote retrieval is stale, local time is wrong, the group does not match, the consumer applies inverse semantics, generated state is old, or the call reached a different consumer or destination.

Prove retrieval into the intended local calendar

For a remote driver, inspect the configured endpoint, selected collection, authorization state, synchronization interval, last successful retrieval and any current error without exposing credentials. Confirm the exact event appears in the intended local calendar. A reachable provider or successful OAuth authorization does not prove the selected calendar synchronized or the event parsed.

Compare a known-good control event from the same source. If both are absent, remain at retrieval; if only one is absent, inspect its format, recurrence and filters before changing the connector.

Resolve timezone, recurrence and active interval

Normalize the source start and end, source timezone, event timezone, PBX timezone and consumer timezone to explicit instants. Check all-day interpretation, overnight events, recurrence rules, exclusions, moved instances and daylight-saving boundaries. A visually correct date in the source UI may map to a different active interval on the PBX.

Test immediately outside and inside the intended window. Do not move the production event or PBX clock as a diagnostic shortcut; correct the demonstrated owner of the conversion.

Evaluate the selected group and match policy

If the consumer selects a Calendar Event Group, enumerate its calendar, event and category members. Determine whether the expected event satisfies the exact rule and whether another active event makes the group match unexpectedly. Calendar synchronization and group evaluation are separate checkpoints.

Use one should-match and one should-not-match control. Correct only the member, category or name rule that diverges; do not add the entire calendar merely to make one test pass unless that is the approved policy.

Follow the consumer into generated and live state

Record whether Time Conditions uses Calendar mode and which match and non-match destinations it owns, whether Follow Me uses inverse matching, or whether Paging Pro created the expected scheduled action. Apply supported configuration changes and confirm the generated or scheduled state belongs to the same object.

For a call, prove that the dialed path actually entered that Time Condition and record the branch selected at the test instant. A correct calendar indicator does not establish that another inbound route, manual override, call flow or earlier destination did not own the result.

Correct one owner and retest the boundaries

Correct only the first demonstrated divergence: remote authorization, selected collection, synchronization, event data, timezone, recurrence, group membership, category rule, inverse setting, consumer destination, generated configuration or scheduler state. Preserve prior values, credential handling, fallback and rollback.

Retest before, during and after the event with one should-match and one should-not-match case. Confirm the intended call or scheduled action and the alternate branch. This workflow is derived from first-party documentation and was not reproduced on a customer or laboratory PBX.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Guide · FreePBX 17 / Debian 12 editorial baseline; Sangoma Calendar, Calendar Event Groups, local, iCal, CalDAV and Outlook OAuth documentation plus FreePBX release/17.0 Calendar source and Time Conditions metadata reviewed October 11, 2026; several Sangoma interface examples are version-labelled for PBX 14 and are semantic rather than an exact FreePBX 17 screen map; installed module and driver versions, provider behavior, credentials, synchronization, event parsing, timezone, recurrence, group membership, consumer state, generated configuration, scheduler and live routing require local evidence, and no PBX, calendar account, event, credential, sync, route, page or live call was inspected or tested

FreePBX Calendar: sources, groups and routing evidence

Keep calendar retrieval, event time, group matching and the consuming Time Condition, Follow Me or scheduler independently observable.

Read guide →
Guide · Asterisk 22 GotoIfTime, ExecIfTime, IFTIME, TESTTIME and STRFTIME documentation plus current public Sangoma Time Conditions and Time Groups guidance and FreePBX release/17.0 Time Conditions metadata version 17.0.1.19 reviewed October 15, 2026; Sangoma interface guidance is explicitly labelled for PBX GUI version 13 and is used for object and override semantics rather than as an exact FreePBX 17 screen map; installed modules, generated dialplan, host and explicit timezones, clock state, schedule, overrides, targets and calls remain deployment specific; no PBX, module, clock, timezone, dialplan, condition, override, destination or live call was inspected or tested

FreePBX time conditions and time groups

Route open hours, holidays and authorized overrides by keeping the time group, condition, destination chain, scheduled state and override state independently observable.

Read guide →
Troubleshooting guide · Asterisk 22 GotoIfTime, ExecIfTime, IFTIME, TESTTIME and STRFTIME documentation plus current public Sangoma Time Conditions and Time Groups guidance and FreePBX release/17.0 Time Conditions metadata version 17.0.1.19 reviewed October 15, 2026; Sangoma interface guidance is explicitly labelled for PBX GUI version 13 and is used for object and override semantics rather than as an exact FreePBX 17 screen map; installed modules, generated dialplan, host and explicit timezones, clock state, schedule, overrides, targets and calls remain deployment specific; no PBX, module, clock, timezone, dialplan, condition, override, destination or live call was inspected or tested

FreePBX time condition routes to the wrong destination

Separate call-path selection, PBX time, time-group matching, manual override and holiday logic before changing an open or closed destination.

Read guide →
Guide · FreePBX 17 / Debian 12 editorial target; Sangoma's public Follow Me and extension field references are explicitly labelled for PBX GUI version 13 or 13+, so the installed FreePBX 17 module versions, labels, generated dialplan and loaded behavior remain authoritative; first-party pages reviewed October 9, 2026; no PBX, extension, route, trunk, number, prompt, mailbox or call was inspected or tested

FreePBX Follow Me: sequence, external legs and acceptance

Design an extension-owned Find Me/Follow Me sequence without confusing saved settings, enabled state, external outbound legs, human confirmation or the final no-answer destination.

Read guide →
Guide · FreePBX 17 paging-module source plus Sangoma's version-13-labelled Paging and Intercom guide and current Sangoma phone header documentation reviewed September 29, 2026; no PBX, page group, endpoint, header, firmware, audio path or live page was tested

FreePBX paging and intercom deployment

Choose an explicit audience, verify endpoint auto-answer and distinguish broadcast delivery from two-way intercom.

Read guide →
Guide · FreePBX 17 on Debian 12; Bulk Handler 17.0.7.1 release/17.0 metadata and Sangoma Bulk Handler workflow reviewed October 11, 2026; repository state does not prove the installed module or runtime, and no import or Apply Config operation was tested

FreePBX changes: submit, apply and verify

Keep GUI settings, generated configuration and runtime behavior aligned during routine administration.

Read guide →