Automated 3CX Extension Registration Alerts
Every 15 minutes, WebRun checks the 3CX management console for any extension or SIP trunk that has dropped its registration, opens a Trello incident card with the affected extension, and alerts IT in Microsoft Teams so a phone outage gets caught before someone reports a dead line.
How do I get alerted when a 3CX extension stops registering?
WebRun checks the 3CX management console every 15 minutes for extensions or SIP trunks that dropped registration, opens a Trello incident card naming the affected line, and alerts IT in Microsoft Teams, so a phone system outage is caught and worked before a caller notices a dead line.
- Dropped registrations are caught within 15 minutes
- IT gets a Teams alert before a caller reports a dead line
- Every incident stays logged until registration is confirmed restored
Built for IT teams · telecom admins · managed service providers · office managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
customer.3cx.comin a real browser with your saved login - no setup, no API keys. -
1
3CX - check registration status
3cx.com
WebRun opens 3CX to check registration status. - Open the 3CX management console
- List extensions and SIP trunks currently registered
- Flag anything that dropped registration since the last check
Done when Every extension or trunk that dropped registration is identified.
-
2
Trello - open an incident card
trello.com
WebRun opens Trello to open an incident card. - Add a card to the Phone System Incidents board
- Name the affected extension or trunk and when it dropped
- Leave the card open until registration is confirmed restored
Done when Every registration failure has an open incident card.
-
3
Microsoft Teams - alert IT
microsoft.com
WebRun opens Microsoft Teams to alert IT. - Post a message to the IT channel naming the affected extension or trunk
- Link to the Trello incident card
- Note how long it has been unregistered
Done when IT has been alerted in Teams with a link to the incident.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun restart the extension or trunk itself?
No. It only detects that registration dropped and opens an incident for IT to act on. Restarting or reconfiguring the extension is done by your IT team.
How fast is a dropped registration caught?
WebRun checks the 3CX console every 15 minutes, so a dropped extension or trunk is caught and alerted within that window.
When does the incident card close?
Once a later check confirms the extension or trunk has registered again, the card is marked resolved rather than left open indefinitely.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.