|
|
Description:
|
sigChanEIsdnTracing OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This attribute defines which types of tracing are active on the
signalling channel. The tracing messages are sent to the debug
stream. To see the messages the agentQueueSize attribute of the
Lp/x Eng Ds/debug component must be greater than 0 and the
operator's NMIS session must have the debug stream included in its
data stream list (for example: set Nmis Telnet Session/1
dataStreams deb). Several types of tracing can be enabled
simultaneously.
Note that tracing consumes additional CPU resources and slows
down call processing on a heavily loaded card. If there is message
block exhaustion tracing is suspended for a period of time and then
automatically re-enabled. An alarm is generated on tracing
suspension and resumption. This mechanism protects the function
processor against excessive numbers of tracing messages.
Types of tracing include:
protocolErrors - get details of any protocol errors which are
occurring. Protocol errors are also reported in summary form as
alarms.
q931Summary - summary of the Q.931 messages on the signalling
link.
q931Hex - Q.931 messages displayed in hex format. Useful to
determine protocol compliance in case of errors reported on local or
remote ends.
q931Symbolic - Q.931 messages parsed to give maximum detail.
Useful for understanding content of messages flowing on the link.
portHex - Q.921 messages in hex format being sent and received on
the link.
Description of bits:
protocolErrors(0)
q931Summary(1)
q931Hex(2)
q931Symbolic(3)
portHex(4)"
|
|
|
|
