Hipath 4000 error - This station does not support key layouts (28045) 1

[nick1977]

VADSU Alarm Snapshot indicates Maintenance Note / Major / Central / BPA with error number 29. It will reappear in a few minutes after clearing the alarm, but the phone system seems functional other than not being able to make any key layout changes.

Thanks,
Nick

 

[sbcsu]

Your call charging is not working.
If you are not using the call charging then turn it off other wise you will get the alarm.

 

[nick1977]

CDR: CDB POOL FULL - LOSS OF DATA IN SWU"
F4684 M4 N3519 NO ACT BPB CDR MAINTENANCE 13-07-17 06:32:53

Our call logger had stopped last time maintenance was performed. Thank you for pointing me in the right direction. I am still receiving the above message. Is there anyway to increase this pool or wipe its contents? I am a simple Windows tech that has become slave to the Hipath ;]

Thank you again for getting our call logging working.

Nick

 

[sbcsu]

The alarm will go away when the HiPath buffer is empty.
Its a buffer on the Hard Disk that normally gets overwritten by the latest records if it is already full (not collected)
That is when the alarm is generated.
When your call logging program has received all the data on the HiPath then the alarm will normally clear.
If you want to clear the alarm now
DEL-GRA:BP,29;
should do it
You can increase the pool but I dont have the info to hand.
You are better off just having the call logging running all the time.

 

[sbcsu]

To see the status of the CDR Collection (On the LAN I presume)
DIS-LSSM;
You should see the local ports and if it is collecting you will see the port numbers on the collection server/pc

 

[sbcsu]

No idea about key layout changes,
do you use comwin to make changes or the assistant or both?

 

[nick1977]

DIS-LSSM;
H500: AMO LSSM STARTED

+=========================================================================+
| STATE OF LAN - CHANNELS |
+=========================================================================+
| | | SYSTEM | USER |
| TCP- | STATE |=========================================================|
| LINE | | IP ADRESS | PORT | IP ADRESS | PORT |
+=========================================================================+
| 1 | ON | 192.0.2.3 | 1201 | 192.0.2.55 | 4543 |
| 2 | ON | 192.0.2.3 | 1202 | 0.0.0.0 | 0 |
| 3 | OFF | 0.0.0.0 | 0 | 0.0.0.0 | 0 |
| 4 | OFF | 0.0.0.0 | 0 | 0.0.0.0 | 0 |
| 5 | OFF | 0.0.0.0 | 0 | 0.0.0.0 | 0 |
| 6 | OFF | 0.0.0.0 | 0 | 0.0.0.0 | 0 |
+=========================================================================+

Thanks,
Nick

 

[sbcsu]

Looking at that you are logged on to the system using IP address 192.0.2.55
however you are not collecting the CDR
You would see it on Line 2
try deactivating and activating the line as follows:

DEA-LSSM:A1,2;
ACT-LSSM:A1,2;

and then display again to see if you get the IP address of the CDR machine and port

 

[nick1977]

Thank you for your help. We have all the alarm lights out on the system. I can make changes from expert mode to the individual phones, but the java interface refuses to let me edit the phone layout. A keytest simulation will show all the buttons on the phone and let me dial from the gui. We even reverted back to the java version that came with the hipath v4, so I am out of ideas, but I appreciate your help. Thank you again SBCSU.

The SDCARD slot is deactivated and I was wondering if you knew of anyway to reactivate it without restarting the entire system as we are at a hospital. We were told the SDCard has to be in the slot on a reboot, if this is the case, that fine, I will continue FTP backups, but I would really like to get the flash cards working again if possible without taking down the facility.

Either way, you have been a great asset, and thank you for taking time out of your day to respond to everyones questions.

Best Regards,
Nick

 

[donb01]

Please note, I have been unable to get the assistant for V5 to run with Java versions higher than 6.x. I would suggest you downgrade your Java, even though you will get lots of warnings, on your maintenance PC. Then go through the assistant setup process again to make sure everything is still configured right. Don't keep the newer version of Java on your PC.

I made the mistake of taking the last upgrade because I wanted all the annoying "insecurity" messages to stop, and it trashed assistant. After I went back to the last release of V6 Java I also noticed an item on the error message that says "always ignore this error for this site" - I have lived happily ever after since then. I also prefer to use firefox to run the assistant. They claim it doesn't work, but it works just fine for me, and it opens the different screens so they are a lot easier to find.

 

[sbcsu]

So many versions now = what I am using at the minute is Windows Virtual PC from Microsoft.
I am using it on Win 7 and anytime I have problems on the Assistant I can open the Virtual XP and it works

 

[donb01]

I had to do that with the ProCenter Manager until I got a newer version that supports Win 7. Took me a while to get virtual PC loaded because IT had something in the group policy that was preventing me from installing it. Once I figured that out everything worked great!

The only problem I have ever had with the assistant is using what Siemens terms "unsupported versions of Java", but in most cases before V7 came out I was able to work around it. V7 claims Assistant has been coded in an insecure format and thus it will not allow it to run. I looked all over for a setting for "shut up and run it anyway" but couldn't find one.