Monitoring the 3CX Phone System
pixel500w-500x1
Zero Admin
With the new Dashboard
pixel500w-500x1
Bulletproof Security
With SSL certs and NGINX
pixel500w-500x1
Install on $100 Appliance
Intel MiniPC architecture
pixel500w-500x1
New, Intuitive Windows Client
More themes, more UC
pixel500w-500x1
More CRM Integrations
Scripting Interface to add your own
pixel500w-500x1
Improved Integrated Web Conferencing
iOS and Android apps included
pixel500w-500x1
Personal Click2Meet URLs

Monitoring the 3CX Phone System

Monitoring your Phone System

On this topic

Monitoring your Phone System

Introduction

Things to Monitor

System Extensions

3CX Services

Server Events

Troubleshooting

Activity Log

Event Log

See Also

Introduction

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.

Things to Monitor

System Extensions

3CX Phone System uses system extensions for services such as IVR, Queue, Fax, Parking and so on. Using the “System Status” > System Extensions node in the 3CX Management Console you can quickly monitor if all the system extensions are working and registered correctly.

3CX Services

A good first check is to monitor that all 3CX services are running. You can view all 3CX services from the “System Status” > Services node in the 3CX Management Console. Any network monitoring package can monitor Windows services remotely.

Server Events

You can configure email alerts to be sent to you for critical events from the “Settings” > “Email” > “Email &  Notifications” tab.

Troubleshooting

To troubleshoot 3CX Phone System you can use the Activity log and Event logs inside the Troubleshooting node.

Activity Log

Monitor the Activity Log to troubleshoot issues. It shows the activity of the server, and logs potential reasons for error conditions. The Activity Log allows you to easily filter based on an Extension, or a particular call. In addition, you can filter the logging by date and time.

Click the “Logging” button to enable verbose logging which will show whole SIP messages and debug information. You can also configure for how many days to keep backup logs.

Note: Verbose logging consumes a lot of disk space and uses more processing power. It is important to change the level back to low or medium after the troubleshooting session is complete.    

Event Log

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). The 3CX license limit on concurrent calls. If this event occurs frequently you should consider upgrading your license.
  • 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.

See Also

You might also be interested in:


Ask a Question

Please only post questions in regards to the document you are currently reading.
Technical support or pre sales questions must be posted via the support or sales channels and such comments will be deleted. Thank you for understanding

Leave a Reply

<