logo.gif MCU 4210
host: mcu_febras

Working with the event logs

If you are experiencing complex issues that require advanced troubleshooting, you may need to collect information from the MCU logs. Typically, you will be working with Customer support who can help you obtain these logs.

Event log

The last 2000 status messages generated by the MCU are displayed in the Event log page (Logs > Event log). In general these messages are provided for information, and occasionally Warnings or Errors may be shown in the Event log. The presence of such messages is not cause for concern necessarily; if you are experiencing a specific problem with the operation or performance of the MCU, Customer support can interpret logged messages and their significance for you.

You can:

Event capture filter

The Event capture filter allows you to change the level of detail to collect in the Event log traces.

Note: You should not modify these settings unless instructed to do so by Customer support. Modifying these settings can impair the performance of your MCU.

Normally, the capture filter should be set to the default of Errors, warnings and information for all logging sources. There is no advantage in changing the setting of any source without advice from Customer support. There is a limited amount of space available to store logged messages and enabling anything other than Errors, warnings and information could cause the log to become full quickly.

Event display filter

The Event display filter allows you to view or highlight stored Event log entries. Normally, you should not need to view or modify any of the settings on this page.


You can configure the MCU to send event messages to up to four syslog servers. To add or remove a syslog server, go to Logs > Syslog and make the changes you require. See Logging using syslog.

H.323/SIP log

The H.323/SIP log page records every H.323 and SIP message received or transmitted from the MCU. The log can be exported in an .xml file by clicking Download as XML.

By default the H.323/SIP log is disabled because it affects performance, but Customer support may ask you to enable it if there is a problem with an MCU in your network. To do this, click Enable H323/SIP logging.

Note that although the H.323/SIP log page can display up to 10 pages of logged messages the log file may begin to overwrite itself before the 10 pages are full.

Audit log

The audit log records any user action on the MCU which might compromise the security of the unit, of its functions, or of the network. For more information, refer to Working with the audit logs.

Call Detail Records

In addition to the logs described above, the MCU can also store Call Detail Records (CDR) which may be used for auditing and billing purposes. Events in the log are displayed in the CDR log page. See Working with Call Detail Records for more details.

Related topics