AudioCodes MP-26 series, User Manual

Page: 229 / 464

User's Manual 13. Remote Device Management
Version 4.4.0 229 MP26x/MP27x
13.1.2.3 Alarms, Notifications and Logging
Instead of periodically polling the device to obtain its current status, the service provider
may want the device to notify abnormal events or to send regular reports to a logging
server. Both options are supported by the device. The table below lists the relevant
interfaces for alarms and notifications.
Table 13-3: Notifications and Logged Events
Group Notifications and Logged Events
VoIP

Notifications: Registration error or timeout

Logged Events:

End of call (Call Detail Record logging)

SIP messages logging (optional - for debugging)
Network Connections

Notifications: Connection up / down
Security

Logged Events: Security log (configurable)
System

Notifications:

System restart

Firmware / configuration update

Logged Events: Debug-level logging (optional)
Note that the terms Alarm and Notification represent the same thing. The difference
between alarm/notification and logging is that an alarm is normally used to represent an
abnormal event (e.g. registration error), while logged events can represent either regular
events (e.g. end of call) or abnormal events.
The table below lists the event severity levels defined in the device. Typically, events with
severity of Error or Emergency are notified in addition to being logged.
Table 13-4: Severity of Logged Events
Severity Description
Debug
Debug-level messages.
Notice Normal but significant condition. Notices requiring attention at a later time.
Non-error conditions that might require special handling.
Error
Recoverable / temporary error condition.
Emergency System is unusable. The most severe messages that prevent continuation
of operation, such as immediate system shutdown.