Specific Events - Snom ONE IP Technical Manual

Deploying the snom ONE IP Telephone System
62
the year, mm
good practice to write the logs there (e.g.,
Warning: Please note that using a log file without a dollar sign as part of the
name is a ticking time bomb. While the system may initially run fine, system
instability is likely to occur as disk space becomes consumed.
Warning: Be sure to lower the log level once the system is running, especially
when you write the log messages to a file. Sooner or later, you will get a hard
disk full error, which is a severe situation because the system will not be able
to save runtime data.

Specific Events

You can enable or disable logging on a subsystem level (available subsystems are shown
below):
•
Log general events: These events are of general interest, for example, informa-
tion about the working directory.
•
Log SIP events: Events in this module relate to the SIP traffic of the system.
•
Log media events: The system reports events about media processing, for
example, a one-way audio RTP timeout.
•
Log IVR events: This module logs events related to processing user input
(e.g., all DTMF events, including the auto attendant and the mailbox).
•
Log email events: If you want to troubleshoot the email server interaction,
turn this module on so that you'll see SMTP events.
•
Log http events: This flag controls whether events in the internal HTTP
server should be logged.
•
Log registration events: When a device registers or deregisters, it appears in
this module.
•
Log SNMP events: SNMP events occur when an external SNMP agent
requests information from the system (see also page 58).
•
Log trunk events: Log events are related to trunks (e.g., when a trunk regis-
ters for the first time or when an inbound trunk calls).
is the month, and dd is the date. If you have multiple drives, it is
D:\logs
).