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 Technical support who can help you obtain these logs.
The capture filter allows you to change the level of detail to collect in the Event log traces.
You should not modify these settings unless instructed to do so by Technical 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 Technical support. The diagnostic information generated by the MCU can be very verbose and enabling excessive debugging without advice can cause the Event log to become full very quickly and is not advised.
The 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 Events > Syslog and make the changes you require. See Logging using syslog.
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 default the H.323/SIP log is disabled because it affects performance, but Techincal support may ask you to enable it if there is a problem with a unit in your network.
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.
|(c) Copyright TANDBERG 2003-2009, License information|