Level Verified

3CX Service Monitoring

Proactively monitor and restart 3CX VoIP services to ensure seamless business communication. Get real-time alerts for service interruptions.

Import into Level

Problem overview

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.

Monitors

critical 9 checks
  • 3CX Core System Server Status (Service monitor) 3CX Core System Server Status (Service monitor)
  • 3CX Call Queue Manager Status (Service monitor) 3CX Core System Server Status (Service monitor)
  • 3CX Management Console Status (Service monitor) 3CX Core System Server Status (Service monitor)
  • 3CX SIP Server Status (Service monitor) 3CX Core System Server Status (Service monitor)
  • 3CX Media Server Status (Service monitor) 3CX Core System Server Status (Service monitor)
  • 3CX IVR Service Status (Service monitor) 3CX Core System Server Status (Service monitor)
  • 3CX Gateway Service Status (Service monitor) 3CX Core System Server Status (Service monitor)
  • 3CX Firewall Service Status (Service monitor) 3CX Core System Server Status (Service monitor)
  • 3CX Event Notification Manager Status (Service monitor) 3CX Core System Server Status (Service monitor)
Tags 3CX
3CX Service Monitoring

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.

Use cases

  • 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

  • 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.
3CX

Frequently asked questions.

Can this monitor check 3CX call quality or connectivity?

No, this policy focuses on service availability. Use 3CX’s built-in tools or additional monitors for performance metrics.

What should I do if the service doesn’t restart?

Check 3CX logs for errors and verify system resources like memory and disk usage.

Is this policy compatible with both Windows and Linux deployments of 3CX?

No, it's designed for Linux. Contact support if you need a Windows version, and we'll add that to this monitor.

Can I customize the number of restart attempts?

Yes, modify the policy settings to adjust the retry limits based on your requirements.

Ready when you are.

No credit card. No sales call. Just sign up and start managing.

Start for free Talk to us