This attribute defines which types of tracing are active for this
signalling channel. The tracing messages are sent to the debug
stream. To see the messages the agentQueue attribute in Col/debug
must be greater than 0 and a Telnet NMIS session must list the
debug stream in in its data streams (ex. set nmis telnet session/1
dataStreams debug). Different types of tracing can be enabled
simultaneously.
Note that tracing consumes additional CPU resources and will slow
down call processing on a heavily loaded card. If there is message
block exhaustion tracing will be suspended for a period and then
automatically reenabled. 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
occuring. Protocol errors are also reported in summary form as
alarms.
q931Summary - Summary of the Q.931 messages on the signalling
link, including certain call details (calling number, called number,
release codes).
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 - Messages in hex format being sent and received on the
link.
Description of bits:
protocolErrors(0)
q931Summary(1)
q931Hex(2)
q931Symbolic(3)
portHex(4)
Parsed from file nortelPC-vnetEtsiQsigV1.mib.txt
Company: None
Module: Nortel-MsCarrier-MscPassport-VnetEtsiQsigMIB
This attribute defines which types of tracing are active for this
signalling channel. The tracing messages are sent to the debug
stream. To see the messages the agentQueue attribute in Col/debug
must be greater than 0 and a Telnet NMIS session must list the
debug stream in in its data streams (ex. set nmis telnet session/1
dataStreams debug). Different types of tracing can be enabled
simultaneously.
Note that tracing consumes additional CPU resources and will slow
down call processing on a heavily loaded card. If there is message
block exhaustion tracing will be suspended for a period and then
automatically reenabled. 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
occuring. Protocol errors are also reported in summary form as
alarms.
q931Summary - Summary of the Q.931 messages on the signalling
link, including certain call details (calling number, called number,
release codes).
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 - Messages in hex format being sent and received on the
link.
Description of bits:
protocolErrors(0)
q931Summary(1)
q931Hex(2)
q931Symbolic(3)
portHex(4)
Parsed from file Nortel-MsCarrier-MscPassport-VnetEtsiQsigMIB.mib
Module: Nortel-MsCarrier-MscPassport-VnetEtsiQsigMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-MsCarrier-MscPassport-VnetEtsiQsigMIB
[Automatically extracted from oidview.com]
mscSigChanEQsigTracing OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1)) ACCESS read-write STATUS mandatory DESCRIPTION "This attribute defines which types of tracing are active for this signalling channel. The tracing messages are sent to the debug stream. To see the messages the agentQueue attribute in Col/debug must be greater than 0 and a Telnet NMIS session must list the debug stream in in its data streams (ex. set nmis telnet session/1 dataStreams debug). Different types of tracing can be enabled simultaneously. Note that tracing consumes additional CPU resources and will slow down call processing on a heavily loaded card. If there is message block exhaustion tracing will be suspended for a period and then automatically reenabled. 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 occuring. Protocol errors are also reported in summary form as alarms. q931Summary - Summary of the Q.931 messages on the signalling link, including certain call details (calling number, called number, release codes). 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 - Messages in hex format being sent and received on the link. Description of bits: protocolErrors(0) q931Summary(1) q931Hex(2) q931Symbolic(3) portHex(4)" ::= { mscSigChanEQsigToolsEntry 1 }
mscSigChanEQsigTracing OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1)) ACCESS read-write STATUS mandatory DESCRIPTION "This attribute defines which types of tracing are active for this signalling channel. The tracing messages are sent to the debug stream. To see the messages the agentQueue attribute in Col/debug must be greater than 0 and a Telnet NMIS session must list the debug stream in in its data streams (ex. set nmis telnet session/1 dataStreams debug). Different types of tracing can be enabled simultaneously. Note that tracing consumes additional CPU resources and will slow down call processing on a heavily loaded card. If there is message block exhaustion tracing will be suspended for a period and then automatically reenabled. 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 occuring. Protocol errors are also reported in summary form as alarms. q931Summary - Summary of the Q.931 messages on the signalling link, including certain call details (calling number, called number, release codes). 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 - Messages in hex format being sent and received on the link. Description of bits: protocolErrors(0) q931Summary(1) q931Hex(2) q931Symbolic(3) portHex(4)" ::= { mscSigChanEQsigToolsEntry 1 }