·Tutorial (w/images) showing how to update a 5861 using the Config Manager?
·How do I troubleshoot connecting with Configuration Manager?
·How do I access the 5861 Management Interfaces?
·Where can I download the latest Configuration Manager?
·What do these 0x?? ADSL error message codes mean?
·How do I setup the dial back-up feature using the Web Interface (aka GUI)?
·Where can I get Documentation for the 5861?
·I have a BT branded 5861 and it only has a Login Screen?
·Where can I download firewall scripts for the 5861?
·Where can I download 5861 Kernels?
·5861 DSL router network TCP SYN scan logging denial of service vulnerability?
·My 5800 Series is missing the serial # or it's unreadable, what can I do?
·Installing Kernels via Reset Button (covers 5700/5800 & 2614)
·Where to get Amperor Power Supplies to replace old Tiger Power Supply?

0x0F PROTOCOL_ERROR: A failure occurred during the ACTIVATING process.

0x14 MESSAGE_ERROR: A message from a peer modem during ACTIVATING could not be understood, had the wrong format, or had a CRC error.

DYING GASP SENT: This usually means that the router is sensing insufficient power. This could be introduced by a power surge or bad power source.

ADSL_OPEN: This command can be given when ATU is in idle or full-on state. ATU enters Wait for ACTIVATING State on reception of this command.

ERROR CODES FOR ADSL_OPEN_FAILED: There are several sub-codes, described as follows.

-- 0x05: UNCOMPATIBLE_LINECONDITIONS: When combination of requested minimum ATM rate, target noise margin, and allowed PSD is not possible on the line.

-- 0x0A: NO_LOCK_POSSIBLE: Unable to lock with ATU-C.

-- 0x0F: PROTOCOL_ERROR: A failure occurred during the ACTIVATING process.

-- 0x14: MESSAGE_ERROR: A received message from a peer modem during ACTIVATING could not be understood, had the wrong format, or had a CRC error.

-- 0x19 SPURIOUS_ATU_DETECTED: A signal on the line was present, but after starting the activation, the ATU concluded that signal did not really originate from a peer ATU, e.g. it received noise that could be mistaken for activation tones. This failure is sent in the ACTIVATING state when an error occurs before the first message covered by CRC is received.

-- 0x28 FORCED_SILENCE: The ATU received a message from peer ATU during ACTIVATING to be quiet for one (1) minute.

-- 0x2D UNSELECTABLE_OPERATION_MODE: The ACTIVATING protocol has not succeed in selecting a common mode of operation.

show feedback form

close

Any feedback you provide (corrections, updates or suggestions) are sent to the owner of this FAQ
and anyone else involved in writing or editing this item.

by Doctor Olds
last modified: 2005-08-05 19:35:53