Monitoring your Phone System
Monitoring your Phone System
3CX Phone System is easy to monitor for any Windows administrator, since it behaves just like any other Windows Server application. You can monitor 3CX Phone System using your favourite network monitoring solution, for example ActiveXperts or Microsoft Operations manager.
Screenshot - Monitoring System Extensions
3CX Phone System uses system extensions for services such as IVR, Queue, Fax, Parking and so on. Using the System extensions node in the 3CX Management Console you can quickly monitor if all these system extensions are working and registered correctly.
A good first check is to monitor all 3CX services are running. You can view all 3CX services from the services node in the 3CX Management Console. Any network monitoring package can monitor windows services remotely.
Screenshot - Server Event Log
The Server Event Log node lists events related to 3CX Phone System. You can configure email alerts to be sent to you for critical events from the Settings > General > Email notifications tab.
These events are also posted to the Windows events log as application events so that you can monitor the events using your network monitoring package. The following server events are posted to the log:
- A person dialling the Emergency number (ID 4099).
- Changes to the status of a SIP Trunk (ID 4100).
- A trunk failover occurs, i.e. the backup rule is triggered (ID 12289).
- A Trunk or VoIP provider account responds with an error code (ID 12294) - This could happen if your account is inactive or reached the credit limit.
- Upon registration or unregistering of an IP Phone (ID 4101).
- The licence limit has been reached (ID 8193).
- An IP is blacklisted (ID 12290) – This can happen if an IP has reached the maximum number of failed authentication attempts. Frequently this points to a hacking attempt.
- An IP is blacklisted because of too many requests (ID 12292) – This happens if the web server anti hacking module blocks an IP because of too many requests.
- A Call Back request is triggered by the queue module (ID 102).
- Failure of a DNS resolution - (ID 12293) - This event occurs when the remote VoIP provider could not be contacted. This could occur when your internet connection is down or the specified IP or FQDN for the VoIP provider is incorrect or down.
- Failure of resolving an IP via STUN (ID 12295) – This happens when the STUN server is down. This event will also be triggered when the internet goes down.
Screenshot - Configuring Email Alerts
Additionally, you should create checks that regularly check the IP VoIP gateways.
Screenshot - 3CX Phone System Activity Log
Monitor the server status log to troubleshoot issues. This utility shows the activity log of the server, and logs potential reasons for error conditions.
The Server Activity log allows you to easily filter based on Extension, or particular call. In addition, you can filter the logging by date and time. Enabling Verbose Logging will show additional advanced logging including the SIP messages for the filtered logging.
Was this answer helpful?
Creating Outbound Call Rules An outbound rule denotes on which VoIP gateway/provider an outbound...
Configuring the Clients – 3CXPhone Introduction 3CXPhone is a SIP client that allows users to...
Call Queues Introduction Call Queues allow calls to be queued whilst agents (members of a call...
The Digital Receptionist / Auto Attendant Introduction The digital receptionist feature allows...
Extension Management Introduction This chapter explains how to create and configure extensions...
Powered by WHMCompleteSolution