Troubleshooting; Troubleshooting Methods; Viewing Log Files - Yealink W60P Administrator's Manual

Troubleshooting

This chapter provides an administrator with general information for troubleshooting some
common problems that he (or she) may encounter while using DECT IP phones.

Troubleshooting Methods

DECT IP phones can provide feedback in a variety of forms such as log files, packets, status
indicators and so on, which can help an administrator more easily find the system problem and
fix it.
The following are helpful for better understanding and resolving the working status of the
DECT IP phone.

Viewing Log Files


Capturing Packets

Enabling Watch Dog Feature

Analyzing Configuration File

Exporting All the Diagnostic Files

Viewing Log Files
If your DECT IP phone encounters some problems, commonly the local log files or syslog files
are needed.
You can configure the phone to log events locally. There are two types of local log files:
<MAC>-boot.log (e.g., 0015659188f2-boot.log) and <MAC>-sys.log (e.g., 0015659188f2-
sys.log). These two local log files can be exported via web user interface separately. You can
configure the DECT IP phone to periodically upload the local log files to the provisioning server
(only support an FTP/TFTP as the provisioning server) or the specific server (if configured),
avoiding the local log loss. You can specify the severity level of the log to be reported to the
<MAC>-sys.log file. The default local log level is 3.
You can also configure the DECT IP phone to send syslog messages to a syslog server in real
time. You can specify the severity level of the syslog to be sent to a syslog server. The default
system log level is 3.
Troubleshooting
425