sundance-communications.com/forum Forums TDM Business Telephone Systems Samsung Telephones & Systems AA Card in OS500 Causes system crashes

The below text is an excerpt of text sent to Samsung tech support. I'd appreciate any thoughts or comments on what you guys/gals might think. Thank you in advance!

Initially, the AA card was installed in slot 8. About 15 hours after it was installed the entire system just froze. The clinic was still open then and I was still there. All the LCD's looked normal, but phones were non responsive. Calls in progress continued. People calling in on the PRI received a reorder tone. Since I had been running around changing things I attributed it to something I had done, so I reset the switch. Everything came back up normally at that time. This was about 3:40 in the afternoon. Sometime about 6pm that night the system locked up again. I met the customer out of sight, powered it down, and reseated all the cards. Powered back up just fine, but then froze up sometime again during the night. I spoke to you the next morning and we both agreed we should remove the AA card and see if the system freeze problem clears. It does. Whenever the AA card is not installed, the system works fine. FYI, when I look in xxx Alarm Reporting, there is no event that shows up other than when the system is reset manually to restore the system.

FAST FORWARD several days. I ordered a new AA card to eliminate that. I powered the system down and this time put the AA card in SLOT 6 instead of SLOT 8. First I used xxx to clear slot 8 and then used xxx to add slot 6 as an AA card. This was yesterday morning, 10/4 at 8am. I brought the system back up and they ran flawlessly all day. Sometime last night, about 7 or 8pm, the system froze again. The administrator went down to the office, powered the system down, removed the AA card and restarted the system. The system is up and running again.

So, we have eliminated the possibility that it's the AA card, and since we moved slots, I'm feeling pretty good about thinking it's not the cabinet (since we've tried both slots 8 and 6). It used to drive me crazy when previous techs would always blame everything on a corrupt database...but, that being said I am wondering if this is the case. A couple things I've noticed here and there. Once, the customer called me and said that sporadically there were inbound calls to DID numbers on the PRI that were not going where they should be. As I looked around in OSM I found that one of the PRI channels in xxx had some erroneous data in it, so it appeared that whenever a call hit that particular channel, the call was routed incorrectly. I changed it to match the other channels and the proglem cleared. Also, extension 5483 which is an 18 button phone will not let me program any buttons via OSM. Other extensions allow it, but not that one. I have changed the extension number in xxx and then tried it...but still I cannot program buttons using 722 in OSM. Using a phone to do programming works fine.

The reason I mention the above issues is because I think this might actually be the database. So, I'm looking for your suggestions. Do you think it could be anything other than the database? If the database, I know you would recommend using xxx to clear the memory a couple times and then starting over on the programming manually....but would it be worth a shot to backup the database, use xxx to clear the memory and the re-upload the backup into the system? If I did the latter and then was able to program buttons on 5483 via OSM...would that be an indicator? See below for the card configuration.


The system configuration is: V2.69M and is carded as below. Also, MISC card is installed on the MCP in position #3.
PSUB
PSUB

SLOT 1 PRI
SLOT 2 DLI16
SLOT 3 DLI16
SLOT 4 DLI8
SLOT 5 SLI
SLOT 6 OPEN
SLOT 7 MGI3
SLOT 8 OPEN
SLOT 9 SVMI8e

I would back up the database on your laptop. Clear the memory by the MCP switch for at least 2 minutes. Upload the database to the system from the laptop. The laptop database has no software pointers attached to it. The SM card does. Next step is to default and only program the basic stuff and test. BTW, make sure you have the correct launchpad and OSM. Verify the date on the launchpad not just the version. Old date launchpad used with new OSM will mess up your software

Is extn 5483 on the DLI8 card?

Yes, ext. 5483 is on port 2 of the DLI8 card. Now you've got my curiosity up.

Very interesting, I have had many sites that have upgraded to OS 500's and they have reused the DLI8's and SLI8's etc from their previous system which is fine, but in a few cases I have had problems with extn's on the 8 circuit cards. I have always had a nagging feeling that there is an incompatibility with mixing 16 & 8 circuit cards, Samsung Tech Support assures me that this is not the case but I'm still not convinced. Anyway what I have done is to replace the DLI8 with a DLI16 and problems have gone.

PS - Do you have any idea's with my fault, click here