Mike's PBX Cookbook

ERR4000 - 4099

ERR4010 tn key f Predefined secondary DN key with function f on a data service ACD agent set is not MNC, MCR, SNC, or SCR.
ERR4011 tn ici Wrong ICI key removed.
ERR4012 in cr tn msg key Message Reference ID (MRID) mismatch between the MRID contained in the input CSL message and the MRID stored in the call register. This message indicates the CSL message is delayed. When this message repeats, the most likely problem is CPU overload. Where:
in = MRID contained in the incoming CSL message (in hex).
cr = MRID stored in the call register associated with the TN of the incoming CSL
message (in hex).
tn = The TN of the incoming CSL message, in packed format.
msg = The message type of the incoming CSL message.
key = The function of the key message. This appears when the message type is KEY message.
Refer to Application Module Link (AML) documents for msg and key value.
ERR4013 n t There have been n mismatches in Message Reference ID (MRID) between the active CR and AML message CR within t * 2 seconds.
Action: The CPU may be very busy: check total number of Call Registers, provision of Meridian Mail ports, Meridian Mail use, and system I/O.
ERR4016 CSL indirect connect failed.
ERR4017 CLS indirect disconnect failed.
ERR4018 dn c The ACD-DN for customer c is not defined for data services.
ERR4019 dn Invalid DN was sent from a VAS when requesting Message Waiting Indicator (MWI) update. Output: The affected DN.
Action: Check the DN. It may have been removed in the Meridian 1, but not the VAS.
ERR4020 dn c xxx Data Service DN leaf block does not contain a valid ACD DN. Where: c = customer; xxx block contents.
ERR4021 Meridian Mail MP alarm.
{ESDI} {SEER class} {SEER cause}
ESDI - ESDI port number
SEER class - Meridian Mail SEER class number
Minor alarm lamp lit on attendant console.
ERR4022 mt mst vas c dn acc An incoming CSL DATA add data service DN message has been received, but not enough protected memory exists to allocate a DSDN_LIST for the customer.
Output in hex:
mt = message type
mst = message subtype
vas= VAS IDc = customer number
dn = data service DN
acc = access code
ERR4023 An incoming CSL DATA add or validate data service DN message has been received, but the data services customer option is not set. No data services DNs will be accepted. See ERR4022 for output data.
ERR4024 CSL Co-administration error.
ERR4025 An incoming CSL DATA add or delete data service DN message has been received, but the DN could not be added or removed because not enough unprotected memory exists to allocate a WORKAREA. See ERR4022 for output data.
ERR4026 An incoming CSL DATA delete data service DN message has been received, but the DN does not exist for this customer. See ERR4022 for output data.
ERR4027 An incoming CSL DATA add data service DN message has been received, but the DN could not be added because the maximum had been reached. See ERR4022 for output data.
ERR4028 An incoming CSL DATA delete data service DN message has been received, but the DN was not removed because it was not a data DN. See ERR4022 for output data.
ERR4029 An incoming CSL DATA add or delete data service DN message has been received, but the DN was rejected because the access code was invalid (The DN does not exist). See ERR4022 for output data.
ERR4030 An incoming CSL DATA add or delete data service DN message has been received, but the DN was rejected because the access code was invalid (the DN was not an ACD DN). See ERR4022 for output data.
ERR4031 An incoming CSL DATA add or delete data service DN message has been received, but the DN was rejected because the access code was invalid (the ACD DN is not defined as a primary data service access code). See ERR4022 for output data.
ERR4032 An incoming CSL DATA add or delete data service DN message has been received, but the DN was rejected because the access code was invalid (the DN is defined for a different VAS Server). See ERR4022 for output data.
ERR4033 An incoming CSL DATA add or delete data service DN message has been received, but the DN was rejected because the access code was invalid (the DN conflicts with an existing longer or shorter DN). See ERR4022 for output data.
ERR4034 An incoming CSL DATA add or delete data service DN message has been received, but the DN was rejected because the access code was invalid (the DN already exists). See ERR4022 for output data.
ERR4035 Wrong IE for Notify Message.
ERR4036 Wrong extension bit for notification indicator IE.
ERR4037 Wrong extension bit for original called number IE.
ERR4038 Wrong IE length for original called number IE.
ERR4048 c r idc Conflict in data base for DRC key on SL-1 set.
Action: Check the specified customer, route, for IDC setting.
ERR4049 Mandatory Notification description invalid.
ERR4050 data Intercept treatment DN not found.
Action: Define intercept treatment DN in the FGD data block (LD 19).
TRK tn MFR tn ID j ddd ADR j ddd Where:
TRK tn = TN of the FGDT trunk (l s c u, loop ch)
MFR tn = TN of the MF receiver (l s c u, or loop ch)
ID j ddd = ID field, j = number of digits, dddd = digits
ADR j ddd = Address field, j = number of digits, dddd = digits
If the address was not received or was empty, it is not printed.
ERR4051 data Invalid NPA in ID field. If the error repeats with the same MFR, test the MFR card; otherwise suspect a fault on far end outpulsing mechanism. See ERR4050 for a description of output data.
ERR4052 data Incorrect address; cannot determine the category. If the error repeats with the same MFR, test the MFR card; otherwise suspect a fault on far end outpulsing mechanism. See ERR4050 for a description of output data.
ERR4053 c h a More than 20 Attendant console Graphic Modules being updated in one time slice. Where:
c = customer number
h = hundreds group involved
a = attendant not updated
ERR4054 Access to the trunk was disconnected due to Timed Forced Disconnect (TFD) timeout.
ERR4055 data This message may indicate that a caller dialed an invalid authorization code. It can also refer to MF inter-digital or inter-field timeout. See ERR4050 for a description of output data.
Action: Check the ID and ADR fields to see if the digits are for a phone number or an authorization code. If it is an incomplete phone number, increase the DGTO or IFTO parameters in the FGD block in LD19.
ERR4056 data FGD or M911 trunk received TTR input before end of start-dial wink. Output: trktn mfrtn trunkpm input_message
Action: Test the FGDT trunk and MFR card.
ERR4057 CFNA cannot terminate on the Forward DN (FDN) because the FDN is an ACDDN which is not a Message Center, or the set on which the FDN is defined does not have Message Waiting Allowed (MWA) Class of Service (COS).
Action: Either redefine the FDN, or give the dialed set MWA COS.
ERR4058 Undefined or invalid Attendant Alternative Answering (AAA) DN type was found at AAA timeout. Valid types are Set DN and ACD-DN.
ERR4059 dn Tenant to tenant access denied between the caller and the specified Attendant Alternative Answering (AAA) DN at AAA timeout.
ERR4060 SUPL loop HW c Parameter downloading failed. Unable to send messages through Network card message interface.
Action: Try to download to the card by using the appropriate enable command.
Where: c = NT8D01 Controller card
ERR4061 CPG_DATA_PTR or CPG_BLK_PTR pointer is nil (DUMP module).
ERR4062 Digitone Receiver (NT8D16) failed self-test.
ERR4064 x y z Feature is not allowed for this interface.
x = DCH Interface ID
y = D-channel number
z = Mnemonic for the feature
ERR4067 c x No unprotected CPG data block for CPG x of customer c.
ERR4068 c No unprotected CPG data block for CPG 0 of customer c.
ERR4069 c No protected CPG data block for CPG 0 of customer c.
ERR4070 c x Customer c data block exists, but there is no CPG_PTR_BLK for CPG number x.
ERR4071 tn The type of trunk (COT, DID, Tie, etc.) specified during the audit did not match the trunk type stored within IPE trunk card. The trunk type stored within the card has been set to the trunk type specified in the audit message. (The audit process obtains trunk type from the TN block contained within the database.)
Action: If this message persists, disable and enable the offending unit with LD 32 (which causes a parameter download). If the problem persists, suspect a faulty card.
ERR4072 tn Impedance setting conflict found on an IPE trunk during audit parameter download.
ERR4073 tn Dialing speed setting conflict found on an IPE trunk during audit parameter download.
ERR4074 tn Carrier pad setting conflict found on an IPE trunk during audit parameter download.
ERR4075 tn Companding law (A-Law or Mu-Law) setting conflict found on an IPE trunk during audit parameter download.
ERR4076 tn 10pps1 conflict found on IPE trunk during audit parameter download.
ERR4077 tn 10pps2 conflict found on the IPE trunk during audit parameter download.
ERR4078 tn 20pps conflict found on the IPE trunk during audit parameter download.
ERR4079 tn The hardware ID (type of unit (COT, DID, etc.) and signaling (LOP,GRD, EAM, etc.) is not supported by the card (XUT, XEM, or any other IPE trunk card). The software configuration no longer matches the hardware configuration for the unit.
Unit is disabled.
Action: Check that correct card for desired trunks is in configured slot. Check configuration of unit.
ERR4080 D-channel was not found for sending a facility Message. Output appears as follows (with X11 Release 16 and later software):
NTFERR a b c
DIGPR a b c
INVDN p a b c
Where:
a = originating digits
b = destination digits
c = customer number
p = TCAP package type
X11 Release 15 messages appear as follows:
FAIL
ORIG: xxx DEST: xxx CUST: xx
ERR4081 A Facility Reject message was received. Destination digits cannot be translated.
Output with message:
PKG: xxx NOXLAN
ORIG: xxx DEST: xxx CUST: xx
ERR4082 TCAP Package type is not recognized by Network Message Center (NMC) feature. Output with message:
PKG: xxx
ORIG: xxx DEST: xxx CUST: xx or
CP does not support more than 4 digit DNs. Procedure ICP_ESTABLISH and ICP_FIND_DN
ERR4083 TCAP Component is not recognized by Network Message Center (NMC) feature.
Output with message: PKG: xxx COMP: xxx ORIG: xxx DEST: xxx CUST: xx.
ERR4084 TCAP Operation is not recognized by Network Message Center (NMC) feature.
Output with message:
PKG: xxx COMP: xxx OPER: xxx
ORIG: xxx DEST: xxx CUST: xx
ERR4085 TCAP parameter is not recognized by Network Message Center (NMC) feature.
Output with message:
PKG: xxx COMP: xxx OPER: xxx PARM: xxx
ORIG: xxx DEST: xxx CUST: xx
Home » Meridian » Maint » Err » Err4000 4099