WinSPM PC Shuts Down System

[ThePhoneMn]

I was hoping someone has run into this issue...

Customer has WinSPM connected via COM port to Admin port on Magix, and WinSPM works fine. When this user shuts off his computer, the whole phone system locks up. The system is still up and running, but no incoming/outgoing calls and all the VM lights flash on the 4400 sets. Customer turns PC back on, the phone system works again. I unplugged the SPM cable from the COM port and shut down the system and everything is ok. This is a single cabinet Magix R3.0 V7.0... Here is the error log, any suggestions?

A Transient Errors:

A Message ss/pp Cnt First Last Code
A DUART STREAMING INT 00/00 099 12/31 12:06:23 01/04 13:03:44 0013
A SOFTWARE WARM START 00/00 099 12/31 12:06:23 01/04 13:03:44 0004
A CARD INSERTED/REMOVED 04/00 099 12/31 12:06:23 01/04 13:03:44 000B
A SOFTWARE COLD START 00/00 099 12/31 12:06:24 01/04 13:03:45 0003

Error log definition of Duart Streaming Int:
0013 DUART STREAMING INT:
Processor problem.
or
The system was powered down incorrectly; for example, carrier 2 was powered down before carrier 1. If errors
exist because of the improper powerdown, no action is required.

 

[tdaugirdas]

Not sure why the phone system locks up - rather unusual! The vm lights flashing - is what happens when the system is restarted. So, maybe the customer THINKS the system is locked up - whern it is just going through a restart - which should not take very long. Looking at your error log - it looks like the customer restarted the system - intentionally or not. I assume this customer is logging off (disconnecting) from WinSPM when he/she is finished. If not, you should instruct them to do so properly. It is possible - I guess - that shutting down the computer without having properly disconnected from WinSPM is sending the processor a signal that a module has been removed/inserted - thus the warm/cold restart. Why is the customer regularly connected anyway?

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[ThePhoneMn]

Just a little more clarification on this scenario...

- WinSPM is not running when this happens
- The system will not come back up until the PC is turned back on

I have been working on Merlins since Legend R5, and never have seen this, I thought I would throw it on the wall here and see if anything sticks.
Thanks for the response though...

 

[tdaugirdas]

Well-then I would suspect something is wrong with the "admin" port on the processor OR the serial port on the PC - sending some kind of signal it should not be. I would try resetting the admin port from maintenance - and see if the same problem happens again. I guess it could also be a problem with this particular PC's serial port.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[IPStanding]

phoneman,
i once had a similiar problem. after lots of troubleshooting we finally pinpointed the problem to an in line surge protector on the admin port. it was a little tripp lite RJ45 grounded protector. hope it helps.

 

[merlinman]

In all my years with this product, (From before there was a LEGEND).

If I were to try to figure this out, I would connect a different PC to the port and see if it also causes the failure.

Since you say it happens even without WINSPM Running, then you shouldn't even need to load WINSPM on this substitue PC.

 

[HiDesert]

I have never heard of the WinSPM or the DOS version having
any affect on the Legend processor.
From the Legend 2.1 to the current release of Magix...never
a problem...almost sounds like corrupt processor software.
If the problem is corrupt processor software...any backup
file you have of this system...will also have the problem.
You may have to program a processor from the start.
just a thought!!!!

 

[tdaugirdas]

Have you reset the admin port as suggested - and tried to connect again? Have you tried connecting a different PC - say a laptop - to see if the same problem occurs? This would narrow the issue to either a PC serial port problem - or the processor admin port. If a processor issue, then HiDesert's suggestion may be worth a try - or you can experiment by replacing the processor with one with the same software load.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[t3chhelp]

What kind of 355a adaptor are you using. I have seen this issue before when the customer uses a self made adaptor and not one bought from Avaya. The one from Avaya has special diodes which does not cause this problem. When using self made adaptor, problem will happen, when using Avaya adaptor, on same PC, no problems.