321 Studios (ITG) Trunk 2.0 - page 299

Maintenance Page 299 of 378
ITG Trunk 2.0 ISDN Signaling Link (ISL) Description, Installation and Operation
ITG0250 Invalid X12 message receive d.
Message discarded. Verify that the card type is correctly configured in Meridian 1. Print TNB
in LD20. Ensure that the card is
configured as a TIE Trunk with
XTRK=ITG2.
Major Alarms – Intervention required, but not immediately
This fault class can result in a trap that automati cally resets a processor on the card
and clears the fault after a service interruption of several seconds or minutes. Talkpath
is cut off for existing calls and no new calls can be made on the card until it finishes
resetting.
If the problem occurs frequently the ITG Trunk 2.0 card requires manual intervention.
For example, you can upgrade to an enhanced software version or replace the ITG
Trunk 2.0 card.
ITG0300 Memory allocation failure. Check
configuration. Indicates a dynamic
memory allocation problem.
If this occurs frequently, contact
Nortel Networks technical support.
ITG0301 DSP channel not responding. DSP
channel is disabled. Card sends
message to Meridian 1 to busy the
trunk. This ensures that user’s
calls go through on good DSPs.
These DSP errors are not cleared
automatically. If the occu rs
frequently, replace the card.
ITG0302 DSP device failure. Operating on
reduced capacity. DSP failed to
return to normal service.
Hardware fault cleared by
automatic trap.
ITG0303 DSP subsystem failure. Initiating
card reboot. DSP fatal error
detected.
Hardware fault cleared by
automatic trap.
ITG0304 Cannot write to file. I/O error. Can indicate /C: drive corruption.
ITG0305 Cannot open configuration file.
Using default settings. Can occur
after a reboot.
ITG0306 Meridian 1 messaging error
threshold exceeded. Too many
invalid A07 or X12 messages.
Table 44
ITG Trunk 2.0 alarms (Part3 of 6)
Alarm Description Fault Clearing Action