Error type 0: Run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures.

Error type 18: The D-Channel is demand busied out by command. No calls can be made over this D-Channel.

Error type 130: The media module has been removed or has been insane for more than 11 minutes. To clear the error, reinsert or replace the media module.

Error type 1537: Link error. This error occurs when the port receives an invalid frame over the D-Channel. This error normally indicates an off-board problem usually related to transmission errors on the DS1 facility. Enter list measurements ds1-log for the UDS1 TN464 DS1 Media Module where the D-channel resides. If MG-DS1 is reporting errors, the DS1 facility has experienced transmission problems that could have caused the ISDN-PLK to report a Link Error.

If MG-DS1 is not reporting errors, execute the long test sequence for the D-Channel. Investigate any errors. If there are none, execute a long test sequence for DS1 Media Module (MG-DS1). Investigate any errors.

If no errors could be found by testing, the Link Error is probably not affecting service. However if this Link Error continues to be logged, follow normal escalation procedures.

Error type 1793: DS1 Interface Media Module is out of service. Look for and resolve MG-DS1 errors in the hardware error log.

Error type 3585: Transmit FIFO overflow error. The media module is having problems transmitting data to the packet bus, thus affecting the conveyance of signaling information over the D-Channel. Specifically, this error occurs when the packet bus transmit buffers overflow. This condition probably indicates a hardware problem.

The actual alarming level will depend on the options chosen via the set options command. ISDN-PRI Signaling Link port alarms are treated as Station alarms, and their default alarming option is to downgrade every alarm to Warning. The value shown in the preceding table indicates the normal, unfiltered case option yon the set options screen.

Error type 3841: Bad DLCI error. This error occurs when a LAPD frame is received across the DS1 facility that contains a DLCI that does not have a valid entry in the on-board translation memory. This error normally indicates an off-board problem usually related to a broken endpoint or a state mismatch between a remote endpoint and the local call-processing software. Maintenance will not start any testing or generate any alarms in response to this error.

Error type 3842: Receive FIFO overflow error. This error occurs when the media module detects an overflow of its receive buffers. If it occurs frequently, it may indicate a LAPD parameter mismatch between the two endpoints of a packet-switched connection. LAPD should be able to recover from this problem, but it may degrade the performance of the LAN bus. Maintenance will not start any testing or generate any alarms in response to this error.

Error type 3843: The Signaling Port LAN Loopback test (#939) failed. Run the long test sequence and note the results of the Signaling Port LAN Loopback Test 939.