Polycom Version 2.0.3B manual Syslog on SoundPoint IP Phones

Page 32

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.

This information applies to SoundPoint IP phones running SIP application 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 http://www.ietf.org/rfc.html .

The log.render.level maps to syslog severity as follows:

0 -> SeverityDebug (7)

1 -> SeverityDebug (7)

2 -> SeverityInformational (6)

3 -> SeverityInformational (6)

4 -> SeverityError (3)

5 -> SeverityCritical (2)

6 -> SeverityEmergency (0)

7 -> SeverityNotice (5)

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.

<December, 2006> 3725-17482-001/A

Image 32
Contents SIP 2.0 Administrator’s Guide SoundPoint/SoundStation IP SIP Polycom, Inc Handset, Headset, and Speakerphone Configurable Feature KeysAttribute Default Attribute Permitted Default Interpretation Values LCD BacklightExpanded Memory and Expanded Flash Memory Permitted Attribute Values Default InterpretationDefault RAM Disk ramdisk Permitted Values Default InterpretationMicroBrowser 6 G.722 Audio Codec Attribute ValuesAttribute Default Receive rxEq USB Diagnostics Administrator’s Guide SoundPoint IP / SoundStation IP Syslog Digit MapBilling Code Server Redundancy Supported Platforms Unsupported PlatformsDisable Message Waiting Indicator by Registration Daylight Saving Time Changes forDST Platform Key IDs Miscellaneous Configuration File Changes 9.1 sip.cfgPorted on SoundPoint IP Attribute Permitted Default Interpretation Values Phone1.cfg Device Parameter Configuration File Changes Boot server Sip.cfgIntroduction CentralLocal Dial Plan in Application Configuration FileAttribute Permitted Default Interpretation Values Permitted Attribute Values Default Interpretation Dial Plan in Per-Phone Configuration File Attribute Permitted Values Default InterpretationDial Plan in Application To Digit Map digitmap/ on Trademark Information Dialplan.x.digitmap isBilling Code Entry Billing Code Entry on SoundPoint IP Phones with SylantroTrademark Information Syslog on SoundPoint IP Phones Network Configuration Changes Name Possible Values DescriptionFlash Parameter Configuration Name Possible Values DescriptionSIP Server Fallback Enhancements on SoundPoint IP Phones SIP 2.0 Administrators Guide TerminologySIP 2.1 Server Fallback Implementation Example DeploymentReg.1.server.2.address=172.23.0.1 Behavior When the Primary Server Connection Fails Before SIP Recommended Practices for Server Fallback DeploymentsChanges From Previous Phone Behavior Releases Before SIP Protocol in Application Configuration File Boot serverRegistration in Per-Phone Configuration File References Trademark Information