Problem overview.
The challenge this resource is designed to solve.
3CX is a vital VoIP solution for business communications. A stopped 3CX service can disrupt phone systems, call queues, and conferencing. This policy ensures minimal communication downtime by automatically restarting stopped services and alerting your team.
About this resource.
What it does and how it fits into your workflow.
This policy monitors the 3CX service on devices tagged with “3CX.” If the service stops, it attempts an automatic restart and sends an immediate alert to the operations team. By ensuring service availability, it prevents disruptions in business-critical voice and video communications.
| Monitor name | Monitor type |
|---|---|
| 3CX Core System Server Status (Service monitor) | 3CX Core System Server Status (Service monitor) |
| 3CX Call Queue Manager Status (Service monitor) | 3CX Call Queue Manager Status (Service monitor) |
| 3CX Management Console Status (Service monitor) | 3CX Management Console Status (Service monitor) |
| 3CX SIP Server Status (Service monitor) | 3CX SIP Server Status (Service monitor) |
| 3CX Media Server Status (Service monitor) | 3CX Media Server Status (Service monitor) |
| 3CX IVR Service Status (Service monitor) | 3CX IVR Service Status (Service monitor) |
| 3CX Gateway Service Status (Service monitor) | 3CX Gateway Service Status (Service monitor) |
| 3CX Firewall Service Status (Service monitor) | 3CX Firewall Service Status (Service monitor) |
| 3CX Event Notification Manager Status (Service monitor) | 3CX Event Notification Manager Status (Service monitor) |
Included with this resource.
Everything added when you import.
Tags
- 3CX
Use cases.
Common ways to put this resource to work.
- Ensuring uptime for 3CX servers used for VoIP and telephony.
- Monitoring 3CX systems in contact centers or sales teams.
- Proactively managing disruptions in call conferencing services.
- Supporting hybrid work environments dependent on 3CX for communication.
Recommendations.
Practical guidance for a reliable rollout.
- Tagging: Ensure all relevant devices running 3CX are tagged with “3CX.” We recommend automatically tagging to avoid missing key devices. See “Service Based Tagging” automation as an example.
- Testing: Simulate service stoppages to validate automatic restarts and alerts.
- Backup Configurations: Regularly back up 3CX configurations to ensure quick recovery in case of hardware or software failures.
- Alert Management: Configure alert rules to route notifications to the appropriate IT or telephony team.