BUG4231 ERROR

[breakbuddy]

Getting this error repeatedly on my PBX it's meaning is -

"Procedure SETLAMPSTATE, PASSED, SSDKEY is greater than 2009, 2112, or 2018 last key."

Severity: Minor

Anyone know of how to repair?

Many thanks!
-bb.

 

[janaya]

Found this Solution. Looks like it only applies to those using Call Pilot 1.07

Solution ID: NORT99222 Product Family: Enterprise Voice Create Date: 08/26/2002

Title:
BUG: BUG4231
Facts:
Meridian 1 - Core
Rls. 25.40
CallPilot
CallPilot 1.07.09


Symptoms:
BUG: BUG4231
BUG: BUG4231: Procedure SETLAMPSTATE, PASSED, SSDKEY is greater than 2009, 2112, or 2018 last key.

TERTN in Callregister field is always a CallPilot port TN.


Fix:
Reprogram all CallPilot ports on M1 side. Deacquire ports prior to removal of ports. Reboot CallPilot after reinstall of ports.


John

 

[janaya]

If you have an Option 11C, there seems to be a problem with corruption and a patch needs to be installed.

Notes on problem:

Solution ID: 8.0.6367794.2192564 Product Family: Enterprise Voice Create Date: 06/17/1999

Title:
BUG: BUG4231
Facts:
PBX
Option 11

Symptoms:
BUG: BUG4231
Key lockup.
Key number is larger than maximum keys allowed for set.
TN corruption
DN corruption

Fix:
Install patch MPLR12638.

Post the actual BUG error with all the information afterwards. The corrupted TN is embedded in the information and can be converted from HEX to TN information and you can find out what phone is causing the problem.

John

 

[janaya]

Then there is the Generic BUG4231 error message with another patch solution.


Solution ID: NORT40368 Product Family: Enterprise Voice Create Date: 11/14/2001

Title:
BUG4231

Facts:
PBX


Symptoms:
BUG4231
BUG4231 Procedure SETLAMPSTATE, PASSED. SSDKEY is greater than 2009, 2112, or 2018 last key.
Cause:
Refer to PRS MP13853. <--info unavailable.
Fix:
Install patch MPLR15726.

 

[janaya]

Then they post the big daddy problem with a bunch of information as it relates to other problems:

For software 23.x


Solution ID: 8.0.17047313.2523999 Product Family: Enterprise Voice Create Date: 02/04/2000

Title:
TN Corruption

Facts:
Commercial Processor Platforms

23.55


Symptoms:
TN Corruption

DN Corruption

Digital sets going dead

Digital sets are locking up

Conference key will start flashing on digital sets

Stat TN shows unequipped

Unprotected line pointer disappears

Can print the TNB of set that shows unequipped

TNT in PDT shell shows unprotected line pointer with all 00000

A DNB of the set's DN indicates the DN does not exist

Examination of the DN translator shows that the DN does exist

BUG4231

BUG4231 Procedure SETLAMPSTATE, PASSED. SSDKEY is greater than 2009, 2112, or 2018 last key

BUG195

BUG195 BLOCK_PTR could not be found in specified queue

BUG6246

BUG6246 ACD TN found with its ACD CR in the main queue
Output: ACD TN (unpacked format), ACD ID (DN format)

BUG681

BUG681 SET_ACD_PTRS failed

BUG4498

BUG4498 Not documented at present time

BUG115

BUG115 TERMINAL does not match DN or TN in CR. Terminal (packed), CRptr

AUD338

AUD338 Queue length in APL queue block differs from number in queue. Queue length
corrected. APL_NO, LINK_NO:ENDPTR, CRWORD[0 -3], *IMS_MSG.

BUG4398

BUG4398 ACNT key WINKING or LIT, but agent not active on ACD call


Cause:
ORIKEY:CRPTR or TERKEY:CRPTR is invalid Refer to PRS BV82940


Fix:

Install patch MPLR12638 :Note this is a replacement for MPLR11890

 

[janaya]

Post your software level and adjuct equipment if this is not enough. There are more reasons for this BUG message, but they all seem to be fixed with patches.

John

 

[breakbuddy]

this is related to my other problems with reprogramming of ACD SPV and it's agnts. i found the fix- in my haste to reprogram the SPV set i neglected to add KBA 1.

but still doesn't resolve my original issue in trying to remove 4 agt's from the spv set, to program onto a new acd group. I managed to remove 1 agt from the spv's kba key 42 (she was the only agt programmed on their) looking at the physical set itself i see that many agts are programmed.

so to sum i've got 2 spid's 84001 and 84141 programmed onto the same tn 40 0 1 1. i can't remove an agt because it's SCH0750 and SCH0707 conflicting DNB and Agt already has a super.

need some serious help from ACD gurus!

-bb.

 

[janaya]

Post the TN that has the duplicate SPIDS. Have you tried X'ing out the SPID, or just outing the phone and reprogramming it?

John

 

[breakbuddy]

Outed the SPV's SPID on key 0 and tried to program it to the correct SPID gives me-

SCH0718
ACD-ID already exists

-bb.

 

[janaya]

so you have something like this:

Key 0 ACD 1234 0 9999
SPV

And what you are trying to do is:

Req: chg
Type: 2616
TN: 12 0 0 0
ECHG: yes
Item: Key 0 acd 1234 0 8888

And it is telling you that 8888 already exists?

If you print a DNB on the new id does it show you what TN that number is programmed on?

If it is on another phone you have to remove it.

If you are trying to change the ACD DN
ex.
Key 0 ACD 2468 0 9999 changing the 2468, then you will NOT be able to do this. It sees the 9999 as already being used. You need to either change the SPID as well and change it back, or out the phone and rebuild. (what I would do), but then you have to remove the SPID settings on each of the agent phones in order to out the SPID.

In all this, I am assuming that you are using MAX or just basic ACD features?

John

 

[breakbuddy]

that's exactly what i am trying to do..

but the problem is that the acid says that it's on the same tn. so when i out the phone and rebuild to the correct spid it says that it already exists. it seems like the correct spid is programmed to the right tn but is out in limbo somewhere.

and we are using basic ACD

-bb.