System Notices

What system notices are

System Notices are short, plain-English alerts that appear at the top of the Communication Timeline when CallCore notices something about your 3CX phone system that may need attention — for example, recording storage filling up, or CallCore being unable to reach your 3CX server.

They exist to close a silence gap: CallCore can often see a developing problem (such as recording storage about to fill and stop new recordings) before it affects you. Notices surface that early, in the place you already look.

A few things to know up front:

• Everyone sees them. A notice raised for your organisation is shown to every user who can see the Communication Timeline — they are not aimed at one person.
• They look after themselves. Notices escalate as a situation worsens and clear on their own as it improves — you don't normally have to do anything to remove them.
• They're a courtesy. CallCore warns when it can see a problem, but can't promise to catch everything and doesn't fix the underlying issue (see A best-effort courtesy).

Turning notices on

Notices are produced only while 3CX monitoring is switched on for your workspace.

1. Go to https://<your-subdomain>.callcore.io/app/settings/features.
2. Find the 3CX monitoring feature and toggle it on.
3. Accept the caveat when prompted — monitoring is a best-effort courtesy, not a guarantee.

Once it's on, CallCore begins checking your 3CX system status and connectivity, and any notices start appearing in the Communication Timeline automatically.

Prerequisites. Your 3CX connection must be enabled, and CallCore must be able to read 3CX's status endpoint. If it can't, enabling will report an error (for example, the 3CX agent isn't enabled, or the status endpoint can't be reached).

What you'll see in the timeline

When one or more notices are active, a single banner is pinned to the top of the Communication Timeline. It always shows the most serious active notice; if there's more than one, a “+N more” count appears next to it.

Select the banner to open the Notices dialog, which lists every active notice — most serious first — each with its full explanation. Notices that can be dismissed show a ✕ here (see Dismissing notices).

The banner and dialog update live: as a situation worsens, improves, or clears, the timeline reflects it without a refresh.

Above: the collapsed banner shows the most serious active notice and a count of any others. Its colour and icon signal the severity — see Severity levels.

Severity levels

Every notice carries a severity from 0–10. CallCore's engine sets the number; the timeline turns it into one of four visual styles:

Two severities are deliberately not shown: 0 means the notice has cleared (it disappears), and 1 is an internal breadcrumb that never surfaces to users.

The sections below list each notice and the severities it climbs through, so you can see which style you'll get and when.

Dismissing notices

Some notices can be dismissed; the more serious ones can't.

• Dismissable notices show a small ✕ on their card in the Notices dialog. Select it to dismiss the notice.
• Dismissing is per-user — it hides the notice for you only. Other people in your organisation still see it.
• A dismissed notice comes back if the situation gets worse. If you dismiss a warning and it later climbs to a higher severity, it reappears so you don't miss the escalation.
• More serious notices can't be dismissed. When a problem is active or imminent (for example, recording has already stopped), the notice has no ✕ and stays until the situation actually improves.

Above: the Notices dialog. The “recording stopped” error has no ✕ (can't be dismissed); the storage-low warning does.

You never need to dismiss a notice — they clear themselves when the underlying situation resolves. Dismissing is just for tidying away a low-severity heads-up you've already seen.

How notices clear themselves

Notices are self-managing — in almost all cases you don't clear them, the situation does.

• Storage notices step down as things improve. Each check re-reads the current figure, so a notice moves down the severity ladder as storage frees up (for example, “critically low” at 90% becomes the milder “low” at 82%), and disappears entirely once it drops below the lowest threshold.
• Connection notices clear in one go. A connection notice only climbs while CallCore can't reach your 3CX. The moment the connection is restored, it clears completely.

If you've dismissed a notice and it then worsens, it reappears at the new, higher severity — see Dismissing notices.

Recording storage notices

The most important ladder. CallCore watches how full your 3CX recording storage is and warns before it fills — because once it's full, 3CX stops recording calls and transcription stops with it.

The notice updates in place as the figure changes, and clears once recording storage drops back below 75%.

3CX server disk notices

Separate from recording storage, CallCore also watches the 3CX server's own disk. A full server disk is more serious than full recording storage — it can affect the whole phone system, not just recordings.

This is the only notice that reaches Critical — at that point call handling, recording and the 3CX application itself are all at risk until disk space is freed.

Remote storage archiving notice

If your 3CX is set up to archive recordings to remote storage but that archiving isn't fully configured, CallCore raises a single Warning (severity 5). Recordings that aren't offloaded can fill recording storage and lead to recording stopping.

Known false alarm. Some setups offload recordings with their own script, which makes 3CX permanently report archiving as only “partially configured” even though it's working fine. If that's you, ask CallCore to clear this notice (see A notice that shouldn't be there?) — it will stay cleared. You're still protected by the recording-storage ladder, which watches the actual outcome rather than the configuration label.

Connection-loss notices

If CallCore can't reach your 3CX server at all — it's down, restarting, or unreachable — new calls may stop syncing. CallCore waits a little before saying anything, so a quick 3CX restart doesn't cry wolf, then escalates the longer the outage lasts.

CallCore resumes automatically once the connection is restored, and the notice clears in one step. The first visible nudge is deliberately held back to 15 minutes so a brief 3CX restart doesn't raise a false alarm.

A best-effort courtesy

3CX monitoring is provided as a best-effort courtesy, not a guarantee. CallCore warns you when it can see a problem, but:

• it can't promise to catch every issue, and
• it doesn't fix the underlying problem.

Freeing or expanding storage, or bringing a 3CX server back online, is done on your side (or by whoever manages your 3CX). You accept this when you turn monitoring on, and connection notices repeat it.

A notice that shouldn't be there?

If you think a notice is showing that shouldn't be — a known-good setup being flagged, or a notice that seems stale — email support@callcore.io and ask for it to be cleared. CallCore can remove any individual notice, and for known false alarms (like the sidecar-archiving case) it stays cleared.