ERR5100 - 5199
ERR5100 | Invalid Cardlan message. Received an unrecognizable message. |
ERR5101 | Cardlan received a message out of sequence. |
ERR5102 | A write to 64180 Interrupt control register failed. |
ERR5103 | A write to 64180 Data control register failed. |
ERR5104 | Invalid Cardlan Message. |
ERR5105 | Received a retransmit message from an XPE pack. |
ERR5106 | Cardlan audit has detected a stuck cardlan state. |
ERR5107 | An invalid 64180 message has been received. |
ERR5108 | Hardware type error message received from cardlan. |
ERR5109 | Input IVD message has been discarded. |
ERR5110 | Output SSD message has been discarded. Action: Contact your technical support group if this problem persists. |
ERR5111 | Invalid sequence type has been detected in a transmit XI type message. |
ERR5112 | Overload condition has been detected on an XPE line card. (Signaling to the card has
been disabled.) The card will be automatically enabled after 30 seconds. Action: If problem persists, replace the faulty line card. |
ERR5113 | Three consecutive overload conditions have occurred for this card. The card will be
disabled and will not be re-enabled. Action: You must replace the card. |
ERR5114 | A signaling channel has been disabled. The channel will be enabled automatically. |
ERR5115 | An overload card has been enabled again. Card should be operational. |
ERR5120 | The 1.5 Mb/s International ISDN Gateway feature does not support the QPC472 DTI hardware for the MU/A law conversion and loss level adjustments. Use the QPC720C PRI hardware for DTI trunk connectivities. |
ERR5132 | data For a tandem CDP DSC call, the incoming route and outgoing route belong to the same Route List Index (RLI). To avoid potential looping problems, the CDP DSC database may need to be modified. The output data is: customer number, incoming route, outgoing route, outgoing route list index, outpulsed digits. |
ERR5133 | Invalid content of optional information element. |
ERR5134 | Invalid information element for the message type. |
ERR5135 | Mandatory Cause Information Element missing in Release or Release Complete message. Procedure I_RELEASE. |
ERR5136 | Invalid octet 3A in Calling Party Number Information Element. Procedure CALLING_PTY_#. |
ERR5137 | Protocol error. Procedure DEC_STATUS. |
ERR5138 | Global Call Reference not supported. Procedure GLOBAL_CREF. |
ERR5139 | a b c d e f A data corruption in the ISA_ACTIVE_CALL variable for the ISA service
route has been detected and fixed. The data output is: a = customer number b = ISA master route number c = ISA service route number d = number of trunks configured for the master route e = audited active call count f = active call count in data store |
ERR5140 | a b c d e A data corruption in the ISA_B_RESERVED variable for the ISA service route
has been detected and fixed. The data output is: a = customer number b = ISA master route number c = ISA service route number d = number of B-channels reserved in data store e = audited number of B-channels reserved |
ERR5141 | a b c d e f g h A data corruption in the ISA_BCH_AVAIL variable for the ISA service
route has been detected and fixed. The data output is: a = customer number b = ISA master route number c = ISA service route number d = audited number of channels available e = number of trunks configured for the master route f = audited number of busy channels g = number of channels available in data store h = number of channels reserved in data store |
ERR5144 | Invalid length of information element. |
ERR5145 | Extension bit or IE length error in Party Category IE. |
ERR5146 | Extension bit or IE length error in Transit Counter IE. |
ERR5147 | Invalid numbering type, numbering plan combination. |
ERR5148 | Invalid restart class. |
ERR5149 | Receipt of a Status reporting a Cause different than response to STATUS ENQ. |
ERR5150 | T308 timed out twice in U19 channel. Put in maint-busy state followed by INT (MSG_CR), D-channel number, UTN, State, Call Reference. |
ERR5151 | Undesirable Interface Indicator present in Channel ID IE. |
ERR5155 | OHAS treatment not given because it is not a legal OHAS DN. |
ERR5156 | The input buffer for the CDR TTY is still loaded. There is not enough space for the number of characters to be output. The last character of the field may be lost. |
ERR5157 | BRI call in wrong state. Call is cleared. |
ERR5158 | Invalid BRI call reference. |
ERR5159 | BRI B-channel status out of sync between Meridian 1 and the MISP; call attempt is aborted. |
ERR5160 | BRI calls exceeded the limit for the DSL. |
ERR5161 | BRI call cannot be connected because of incompatibility of the call type with the B-channel. |
ERR5162 | BRI call cannot be connected because a Call Register cannot be allocated. |
ERR5163 | BRI call processing message has timed out. |
ERR5164 | The BRI B-channel is in maintenance busy state. |
ERR5165 | Message received from invalid loop. |
ERR5166 | Message received from wrong line card type. |
ERR5167 | Invalid message received from BRI line card. |
ERR5168 | No output buffer available to send SSD message. |
ERR5169 | Message problem report from BRI line card. |