Trunks
Every SIP trunk, up or down, with 30 days of uptime history. Alert when the proportion of trunks up falls below the percentage you set.
Know your 3CX is up
before your customers do
CommsAlert watches every part of your 3CX system around the clock and alerts you by email and SMS the moment something changes. Nothing is installed on the server and no configuration is altered.
TRUNKSSBCSEXTENSIONSSERVICESLICENCECPU / MEM / DISK
What we watch
Everything that matters, checked continuously
The 3CX monitor reads your system through a dedicated API key and records every check. Each of these is tracked continuously, with its own history.
SBCs
Session Border Controllers tracked alongside the trunks, with their own uptime history and log.
Extensions
Registered extensions against the total, with history. Set the threshold to suit your business hours so after-hours drop-off does not cry wolf.
Services
All 3CX services, each with status, memory use and its own uptime history, plus the most recent service logs.
Licence
Licence type, simultaneous calls and expiry date. Warning and critical alerts a set number of days before the licence runs out.
System version
The version each server is running, checked against the current 3CX release, so systems falling behind are flagged as outdated.
CPU, memory and disk
CPU, memory, physical memory and disk usage sampled continuously, with resource history charts and alarms at the percentages you choose.
System alarms and event log
3CX system alarms surfaced directly, and an optional alert whenever new error events appear in the 3CX event log.
Alarms
You decide what counts as a problem
Every alarm below can be set once as a global default across all your 3CX systems, then overridden on any individual server. Set a value to 0 to turn that alarm off.
| Trunk alert | Alert when the total trunk up percentage falls below this. |
|---|---|
| SBC alert | Alert when the total SBC up percentage falls below this. |
| Extension alert | Alert when the total extension up percentage falls below this. |
| Service alert | Alert when the percentage of 3CX services running falls below this. |
| Disk usage | Alert when disk usage exceeds this percentage. |
| CPU usage | Alert when CPU usage exceeds this percentage. |
| Memory usage | Alert when memory usage exceeds this percentage. |
| Physical memory usage | Alert when physical memory usage exceeds this percentage. |
| Event log alert | Alert when new error events are detected in the 3CX event log. |
| Licence expiry warning | A warning this many days before the licence expires. |
| Licence expiry critical | A critical alert this many days before the licence expires. |
Alerts are delivered to your global alert email addresses and SMS numbers, or to addresses set for an individual system.
Setup
Connected in minutes, with no downtime
Connecting a 3CX system takes a few minutes and needs no downtime.
- 1
Allow our IP
Add the CommsAlert monitoring IP to your 3CX blacklist exemptions so 3CX never blocks the monitor if a key is entered wrongly. The current IP for your region is shown in the portal when you add a 3CX server, and in the User Guide once you are signed in.
- 2
Create an API key or User with System Admin permissions
In 3CX, create a dedicated API key for CommsAlert. We recommend a key used for nothing else. Or for an HTTPS connection, create a dedicated System Owner for the dashboard.
- 3
Add the server
Enter the name, URL, API Client ID and API key — or a username and password if you are using the HTTPS method. Then the HTTPS port (443 or 5001), along with your check interval.
- 4
Set your alarms
Apply your global alarm defaults, or tune the thresholds for this particular system.
Adding a 3CX server also creates server, webpage and SSL monitoring for it automatically — you do not have to add those separately.
Questions
Frequently asked
Do I have to install anything on my 3CX server?
No. CommsAlert connects through the 3CX API over HTTPS. Nothing is installed and no 3CX configuration is changed, beyond creating an API key for us to use.
Is my API key safe?
Saved passwords and API keys are encrypted. We recommend creating a dedicated key used only for CommsAlert, so it can be revoked without affecting anything else.
What happens if I re-add a server?
You will need to regenerate the 3CX API key and enter the new one in the portal.
Which 3CX versions are supported?
CommsAlert monitors current 3CX releases and flags systems running an older version than the latest you have configured as outdated.
Try it free for 3 months
The trial covers 15 servers, 15 webpages, 15 SSL certificates and 10 phone systems — the full feature set, at no cost.