Merlin Mail Error

[ronlanderson]

This is Merlin Mail MM04 version 2.2 running (or not) with a Legend R3 processor and MLX phones.

All message waiting lights had been stuck on. We turned them off using message-delete from the displays. Then they were all stuck off. Other than that the VM was working great.

So I thought I would power everything down and power it back up to see if the light problem got corrected. The phone system came back fine, but the VM never came back up.

I hooked my laptop to it and this is what was being displayed at system startup:

ACCESS MANAGER(tm) is ready for 8 users.
Initializing message reminders.
8Incompatible linecard ROM
The PXSC program has detected an error that will not allow it to continue.
Please note the error description and contact maintenance personnel.
Error: error code 0
Error context: No response from VIOS
Press any key to continue:

Which is where it stopped. Just wondering if anyone knows what any of this means, cuz I sure don't. :)

Thanks!

[Cephas]

This is Merlin Mail MM04 version 2.2 running (or not) with a Legend R3 processor and MLX phones.

All message waiting lights had been stuck on. We turned them off using message-delete from the displays. Then they were all stuck off. Other than that the VM was working great.

So I thought I would power everything down and power it back up to see if the light problem got corrected. The phone system came back fine, but the VM never came back up.

I hooked my laptop to it and this is what was being displayed at system startup:

ACCESS MANAGER(tm) is ready for 8 users.
Initializing message reminders.
8Incompatible linecard ROM
The PXSC program has detected an error that will not allow it to continue.
Please note the error description and contact maintenance personnel.
Error: error code 0
Error context: No response from VIOS
Press any key to continue:

Which is where it stopped. Just wondering if anyone knows what any of this means, cuz I sure don't. :)

Thanks!

It means nothing good that is for sure. I've seen this before. Try rebooting the voicemail unit again, but be prepared to replace your voicemail, now or later...

[ronlanderson]

Thanks for the reply! Of course, this thing ran flawlessly at my house for months while I was setting the whole system up. Then the week after I install it at our church this happens.

I've been giving this some thought, and It appears to me that the VM is really just a 386 computer with a couple of speialized boards for the line ports. If I'm correct then there's basically three things thac can go wrong:
1) Hard drive
2) Something with the motherboard (memory, bios, processor, etc)
3) One of the line port boards

It doesn't appear to be the hard drive or the motherboard, since it boots up fine and the program begins to run. So I'm thinking it's running into a bad card (is that what a VIOS is?). Am I close or all wet? Even if I'm right on, are those line cards available?

[ronlanderson]

Hey Cephas,

I'd left the VM off since Friday night. I turned it on tonight and it booted right up. It's above a suspended ceiling and the A/C doesn't really get into there too much. It was beastly hot up there Friday. So in the hope that it might have been the heat, I'm venting it.

The message waiting lights still aren't ever coming on. I'm not sure if that's better than never having them off or not. :) Is this maybe an issue with the Legend programming?

[Cephas]

Ack! As you pointed out, it's a computer. Would you install their server in a hot dusty location? :-)


Not sure about the message waiting lights. Verify the huntgroup is set to integrated VMS, but one would think it wouldn't function at all really if that were the case... hmmm.

Let me think on that one.

Peter

[ronlanderson]

How about this. I happened to notice that the first extension in the hunt group was connected to VM port 2 and the second extension into VM port 1. I switched them and the lights started working. Make sense, or was this a coincidence?

[Cephas]

Makes some sense. On many 3rd party vms's you specify the last port to be the only one to turn MWL's on/off, streching my brain to try and recall if that is the case on the old merlin mails. Either way - I suspect if you troubleshoot you will find you have a port that is not propery connected (no DT).


Peter