AudioCodes Mediant 4000 SBC User Manual page 852

CHAPTER 52 Syslog and Debug Recording
Message Item
Log Number
(lgr)(number)
Session ID
(SID)
Board ID (BID)
18:38:14. 52 : 10.33.45.72 : NOTICE: [S=235]
[SID:2ed1c8:96:5] (lgr_psbrdex)(619) recv <-- DIGIT
(0) Ch:0 OnTime:0 InterTime:100 Direction:0 System:1
[File: Line:-1]
18:38:14. 83 : 10.33.45.72 : NOTICE: [S=236]
[SID:2ed1c8:96:5] (lgr_flow)(620) #0:DIGIT_EV [File:
Line:-1]
18:38:14. 83 : 10.33.45.72 : NOTICE: [S=237]
[SID:2ed1c8:96:5] (lgr_flow)(621) | #0:DIGIT_EV
[File: Line:-1]
18:38:14.958 : 10.33.45.72 : NOTICE: [S=301]
[SID:2ed1c8:96:5] (lgr_flow)(625) | #0:DIGIT_EV
[File: Line:-1]
You can disable the inclusion of the message sequence number in Syslog
messages, by setting the 'CDR Syslog Sequence Number' parameter to
Disable (see Configuring
Ignore this number; it has been replaced by the Message Sequence
Number (described previously).
Unique SIP call session and device identifier. The device identifier
facilitates debugging by clearly identifying the specific device that sent the
log message, especially useful in deployments consisting of multiple
devices. In addition, the benefit of unique numbering is that it enables you
to filter the information (such as SIP, Syslog, and media) according to
device or session ID.
The syntax of the session and device identifiers are as follows:
[SID=<last 6 characters of device's MAC address>:<number of times
device has reset>:<unique SID counter indicating the call session;
increments consecutively for each new session; resets to 1 after a device
reset>]
For example:
14:32:52.028: 10.33.8.70: NOTICE: [S=9369]
[SID=2ed1c8:96:5] (lgr_psbrdex)(274) recv <-- OFF_
HOOK Ch:4
Where:
■ 2ed1c8 is the device's MAC address.
■ 96 is the number of times the device has reset.
■ 5 is a unique SID session number (in other words, this is the fifth call
session since the last device reset).
✔
A session includes both the outgoing and incoming legs, where
both legs share the same session number.
✔
Forked legs and alternative legs share the same session number.
Unique non-SIP session related (e.g., device reset) and device identifier.
The device identifier facilitates debugging by clearly identifying the
specific device that sent the log message, especially useful in
deployments consisting of multiple devices. In addition, the benefit of
unique numbering is that it enables you to filter the information according
to device.
- 819 -
Mediant 4000 SBC | User's Manual
Description
Syslog).