MP-40x SIP MediaPack BRI Series
SIP User's Manual
124
Document #: LTRT-53301
6.6.4
Level Monitor Concept
Table
6-26: Configurable options
sys-log level
[sys-log level <level>]
Set the debug level
Valid options include:
[0] = Debug is disabled (default) – except for Error and warning messages
[1] = ISDN related messages
o
Received and transmitted ISDN L3 Messages containing
message type, important information (e.g. source number,
destination number, ..) and a binary representation of the
message
[2] = Level [1] + ISDN Layer 1 and 2 messages including TEI negotiation and
information about “slips”
[3] = SIP call flow & SDP messages
o
Received and transmitted SIP messages including message type,
from and to for invite messages and raw sip message.
o
SIP Call state information
o
SDP state information
o
SDP negotiation results
[4] = DSP and Data-path information
o
Data-path
activation/deactivation
o
Tone and DTMF events
o
FAX and coder change events
o
RTP buffer under/overflow messages
[5] = All messages of Level 1 and 3
[6] = All messages (level 1 .. 5)
Note 1: On all debug levels all Error and Warning messages are enabled.
Note 2: The message will be truncated if the message is too long. This also
applies to raw data (SIP & ISDN)
sys-log isdn port [0..4]
[sys-log isdn port [0..4] ]
Select which ISDN interfaces are debugged. This option only applies if Level [2] is
selected. I.E ISDN Layer 1 and 2 is logged.
Indenting Messages:
Message indenting is not required
Message Format:
The following message format is used
( local src ) (sequence nr) [cid: CallId] message
Local src:
The local source should help NetModule to identify the source of the message. ACL does
not “use” this information.
Sequence Nr:
The sequence number must be increased by one for each message. This number is
used to verify if packets have been lost during transmit trough the network.
[cid: CallId]:
Call flow messages (level [1] and [3]) can contain a call Id. This allows the user to filter
messages for a certain call. Note: it will not be possible to add a call id to all call flow related
messages. In some cases the log message will be printed prior to allocating a call id. And in some
messages the code generating the message does not have access to the call id. In these cases the
call id will be left away.
