Polycom SIP 3.1 manual Basic Logging level/change/ and render, Scheduled Logging Parameters sched

Models: SIP 3.1

1 347
Download 347 pages 532 b
Page 239
Image 239
Example:

Configuration Files

Each event in the log contains the following fields separated by the character:

time or time/date stamp

1-5 character component identifier (such as “so”)

event class

cumulative log events missed due to excessive CPU load

free form text - the event description

Example:

011511.006so 200soCoreAudioTermChg: chassis -> idle

time stamp

ID

event class missed events text

Three formats are available for the event timestamp:

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:

Basic Logging <level/><change/> and <render/>

Scheduled Logging Parameters <sched/>

A - 85

Page 239
Image 239
Polycom SIP 3.1 manual Basic Logging level/change/ and render, Scheduled Logging Parameters sched, Example