Polycom Video Game Sound System Version 2.0.3B User Manual
<December, 2006>
3725-17482-001/A
Technical Bulletin 17124
Syslog on SoundPoint
®
IP Phones
This technical bulletin provides detailed information on how the SIP
application has been modified to support logging system level messages and
error conditions with communications networks to a centralized location.
error conditions with communications networks to a centralized location.
This information applies to SoundPoint IP phones running SIP application
version 2.1 or later.
version 2.1 or later.
Introduction
Syslog is a de facto standard for forwarding log messages in an IP network.
The term "syslog" is often used for both the actual syslog protocol, as well as
the application or library sending syslog messages.
The syslog protocol is a very simplistic protocol: the syslog sender sends a
small textual message (less than 1024 bytes) to the syslog receiver. The receiver
is commonly called "syslogd", "syslog daemon" or "syslog server". Syslog
messages can be sent through UDP or TCP. The data is sent in cleartext.
Syslog is supported by a wide variety of devices and receivers. Because of this,
syslog can be used to integrate log data from many different types of systems
into a central repository.
The syslog protocol is defined in RFC 3164. For more information on syslog,
go to
The term "syslog" is often used for both the actual syslog protocol, as well as
the application or library sending syslog messages.
The syslog protocol is a very simplistic protocol: the syslog sender sends a
small textual message (less than 1024 bytes) to the syslog receiver. The receiver
is commonly called "syslogd", "syslog daemon" or "syslog server". Syslog
messages can be sent through UDP or TCP. The data is sent in cleartext.
Syslog is supported by a wide variety of devices and receivers. Because of this,
syslog can be used to integrate log data from many different types of systems
into a central repository.
The syslog protocol is defined in RFC 3164. For more information on syslog,
go to
http://www.ietf.org/rfc.html
.
The log.render.level maps to syslog severity as follows:
For more information on log.render.level, refer to Basic Logging
<level/><change/> and <render/> on page 138 of the SIP 2.1 Administrator’s
Guide.
Network configuration changes required to support this feature are described
in the following section,
Network configuration changes required to support this feature are described
in the following section,
0 -> SeverityDebug (7)
1 -> SeverityDebug (7)
2 -> SeverityInformational (6)
3 -> SeverityInformational (6)
4 -> SeverityError (3)
5 -> SeverityCritical (2)
6 -> SeverityEmergency (0)
7 -> SeverityNotice (5)