Filter
Top Products
Troubleshooting Your SoundPoint IP / SoundStation IP Phones
5 - 5
Log Files
SoundPoint IP and SoundStation IP phones will log various events to files
stored in the flash file system and will periodically upload these log files to the
boot server. The files are stored in the phone’s home directory or a
user-configurable directory.
There is one log file for the bootROM and one for the application. When a
phone uploads its log files, they are saved on the boot server with the MAC
address of the phone prepended to the file name. For example,
00f4f200360b-boot.log and 00f4f200360b-app.log are the files associated with
MAC address 00f4f200360b. The bootROM log file is uploaded to the boot
server after every reboot. The application log file is uploaded periodically or
when the local copy reaches a predetermined size.
Both log files can be uploaded on demand using a multiple key combination
described in Multiple Key Combinations on page C-10. The phone uploads
four files, namely, mac-boot.log, app-boot.log, mac-now-boot.log, and
mac-now-app.log. The “now_” logs are uploaded manually.
The amount of logging that the phone performs can be tuned for the
application to provide more or less detail on specific components of the
phone’s software. For example, if you are troubleshooting a SIP signaling
issue, you are not likely interested in DSP events. Logging levels are adjusted
in the configuration files or via the web interface. You should not modify the
default logging levels unless directed to by Polycom Technical Support.
Inappropriate logging levels can cause performance issues on the phone.
In addition to logging events, the phone can be configured to automatically
execute command-line instructions at specified intervals that output run-time
information such as memory utilization, task status, or network buffer
contents to the log file. These techniques should only be used in consultation
with Polycom Technical Support.
Application Logging Options
Each of the components of the application software is capable of logging
events of different severity. This allows you to capture lower severity events
in one part of the application, while still only getting high severity event for
other components.
The parameters for log level settings are found in the sip.cfg configuration file.
They are
log.level.change.module_name
. Log levels range from 1 to 6 (1 for
the most detailed logging, 6 for critical errors only). There are currently 27
different log levels that can be adjusted to assist with the investigation of
different problems.
When testing is complete, remember to return all logging levels to the default
value of 4.