Spectralink 84-Series Series Wireless Telephones Administration Guide
1725-86984-000_P.docx
September 2016
217
event class
cumulative log events missed due to excessive CPU load
free form text - the event description
Three formats are available for the event timestamp:
Table 10-9: Event Timestamp Formats
Type
Example
0 - seconds.milliseconds
011511.006
-- 1 hour, 15 minutes, 11.006 seconds since
booting.
1 - absolute time with minute resolution
0210281716
-- 2002 October 28, 17:16
2 - absolute time with seconds resolution
1028171642
-- October 28, 17:16:42
Two types of logging are supported:
<level/
>
<change/
>
and<render/
>
<sched/
>
<level/> <change/>and<render/>
Table 10-10: Logging Level, Change, and Render Parameters
Parameter
Permitted Values
Default
log.level.change.xxx
0 to 6
4
Controls the logging detail level for individual modules. These are the input filters into the internal memory-based
log system which produces the [MACaddress]-app.log file.
The most commonly-used values for xxx are listed below. Additional log modules can be found in the log.cfg file.
app1
brow
cfg
dot1x
httpd
ice
key
pps
push
sip
so
tickt
tls
utilm
wlan
wmgr
This parameter and the associated render level (see below) can be set for a single phone in the Admin menu at
Advanced Settings> Administrative Settings> Logging. (Skype for Business only.)
log.render.file
0 or 1
1
Set to 1. Spectralink recommends that you do not change this value.
log.render.file.size
positive integer, 1 to 180
32
Maximum size of flash memory for logs in Kbytes. When this size is about to be exceeded, the handset will upload
all logs that have not yet been uploaded, and erase half of the logs on the handset. The administrator may use
Web browser to read all logs on the handset.
log.render.file.upload.append
0 or 1
1
If set to 1, use append mode when uploading log files to server.
Note: HTTP
and TFTP don’t support append mode unless the server is set up for this.