New Error Message

tomso · Post by **tomso** » 30 Jun 2006 16:55

Hi there -

We are in the middle of implementing a new trunk group and recently our CPU board needed to be replaced. We were able to use the harddrive with the configuration from the old CPU board to get back up and running. However recently we just started to experience at around the same time everyday when an incoming call comes in the 4035T headsets message area reads "Unauthorized feature call for repair" and all functionality of the headsets is gone. After switching the cpu's thru bascul and then switching them back the problem goes away until the next day. Also when changing an user with the "Dial by name and text msg" option to yes the following error occurs "Software Protection Error".

What could be causing these issues? Could the new PRI trunk group have a feature that is not supporting on the PBX? And why would it happen around the same time everyday? Also is the Dial by name error related?

Thanks in advance

cavagnaro · Post by **cavagnaro** » 30 Jun 2006 17:29

uhh that is license. weird, if it was working should work, i would syncronize the cpu's again or reinstall the licenses.

tomso · Post by **tomso** » 30 Jun 2006 18:24

I ran spadmin -m on the main cpu and noticed that the PANIC Flag was indeed set to 1. I took a look at the stand-by cpu and it had all the same active counts but the PANIC Flag was set to 0. How do I now which licensing the PANIC Flag is referring to and how would I go about clearing it. Do you think that with the PANIC Flag set to 1 would that cause the 4035T headset to get the "Unauthorized feature call for repair" message that I noted previously in this topic.

Also how would i go about clearing the PANIC flag or reinstalling licensing.

Thanks again

cavagnaro · Post by **cavagnaro** » 30 Jun 2006 18:36

Well, to reinstall your licenses do this:

On the good CPU:
swinst
5 - OPS Management
1- Backup on CPU Disk
then go to /DHS3dyn/BACKUP/OPS/
copy these files to the same folder on the BAD CPU (or to your PC and then to the bad cpu using FTP)

Then on the bad CPU:
swinst
5- OPS Manag.
2- Restore from CPU

reset

and should work

Regards

Post by **frank** » 30 Jun 2006 18:59

Also, when you have the error on the set, to get ride of it momentarily, just type on the console sprecover

tomso · Post by **tomso** » 03 Jul 2006 01:26

I restored the licenses on the problem CPU hard drive and the PANIC flag was cleared until the next morning. I ran CHECKDB on the CPU with the PANIC flag set and got the following error message "ERROR 4351: Invalid UTAM key 200406291000" also got "ERROR 4351: DATA INCONSISTENCY ENTITY invalid cdt info1=1 info2=-1 info3=-1". Any suggestions for what to try next.

-- Thanks

alex · Post by **alex** » 03 Jul 2006 02:16

tomso wrote:I restored the licenses on the problem CPU hard drive and the PANIC flag was cleared until the next morning. I ran CHECKDB on the CPU with the PANIC flag set and got the following error message "ERROR 4351: Invalid UTAM key 200406291000" also got "ERROR 4351: DATA INCONSISTENCY ENTITY invalid cdt info1=1 info2=-1 info3=-1". Any suggestions for what to try next.

-- Thanks

The only way to get rid of "Unauthorized feature call for repair" - you should order new OPS files with CPUID of your new CPU on BPWS or ask your supplier

Post by **frank** » 03 Jul 2006 09:43

tomso, contact me through aim

tomso · Post by **tomso** » 04 Jul 2006 10:46

Problem solved thanks for your help everyone. The solution ended up being removing the hard key from the bad cpu and replacing it on the new cpu.