User's Manual 798 Document #: LTRT-89730
Mediant 3000
Error Abbreviation Error Name Description
AL
Invalid Header Length
AO
Invalid Codec Type
AP
Unknown Aggregation Payload Type
AR
Invalid Routing Flag Received
53.2.1.2 Unique Device Identification in Syslog Messages
Syslog messages include the following unique string for the device:
The main operations and events of the Mediant 3000 High Availability (HA) are sent to
the Syslog with the prefix "M3K_HA". All Syslog messages and events of the
redundant TP-6310 blade are sent to the Syslog by the active TP-6310 blade with the
"Redundant module message" message prefix.
53.2.1.3 Maintaining Same Syslog SID/BID over Multiple Devices
You can enable the device to maintain the same SIP session ID (SID) and board ID (BID)
in debug log messages (Syslog) for calls traversing multiple AudioCodes' devices. The
feature is useful in that it allows you to use a single SID/BID to easily identify log messages
pertaining to the same call session even though it has traversed multiple devices. Instead
of the log messages being sent with different SIDs/BIDs per traversed device, one unique
SID and BID is used throughout the call session. The SID is also used when
communicating with external servers such as a Routing server, and this feature allows
them to identify the same session over different devices.
To enable the feature, use the SendAcSessionIDHeader parameter. When you enable the
feature, the device includes the proprietary SIP header, "AC-Session-ID" whose value is
set to the device's SID value in SIP dialog request messages (e.g., INVITE) that the device
initiates. All other devices (even if they have this feature disabled) receiving the SIP
request, use this same SID value in their generated debug log messages. Below is an
example of such a SIP header:
AC-Session-ID: 2ed1c8:96:5
For more information on how the device creates the SID/BID value, see ''Syslog Message
Format'' on page 794.
53.2.1.4 Identifying AudioCodes Syslog Messages using Facility Levels
The device’s Syslog messages can easily be identified and distinguished from Syslog
messages from other equipment, by setting its Facility level. The Facility levels of the
device's Syslog messages are numerically coded with decimal values. Facility level may
use any of the "local use" facilities (0 through 7), according to RFC 3164. Implementing
Facility levels is useful, for example, if you collect the device’s as well as other equipments’
Syslog messages on the same server. Therefore, in addition to filtering Syslog messages
according to IP address, the messages can be filtered according to Facility level.
The Facility level is configured using the SyslogFacility ini file parameter, which provides
the following options:
To Next Page
Loading...
Need help?
General
