Merlin Messaging Issues/Version ?'s

[gatorbeetle]

Let me start by saying I am a computer person, not a phone person. I am learning, but not fast enough apparently.

We have a Merlin Magix system. WinSPM says it is Magix 2.2. Last night our Merlin Messaging card (labeled C17649) stopped working. Right now I have gotten it to clear the errors, busy out, restore, reset, and I re-booted the system. That fixed the problem of the port card in the next slot not working, but still no VM.

There was a "meat grinder" sort of noise upon startup. I think the HDD on the board might be frying itself.

I need to figure out what verson of MM I have. WinSPM inventory lists it as "Hardware Vintage:57" I think the system is Ver 2.5, but I cannot find much out on the net for sale as Ver 2.5.

If I got a ver. 1.1 MM card, would my system be compatible? Would my current 8 port lic card still be valid?

We are going to an Office IP in about a month. Of course something like this happens now.

Any info would be appreciated!!!

Rob

 

[gatorbeetle]

Make that a 617C49 card.

 

[gatorbeetle]

Ok, I'll just keep replying to myself. This card seems to be a Ver 2.5, but could have been upgraded to 4.0, is there any way to determine that? Does it matter if my Magix system is reporting it is 2.2?

 

[Telecomboy]

Any version of Merlin Messaging will work with your Magix processor. The port card will work as well. If you have visual display of messages in your display (new 1 old 2) then you had to have had atleast a R2.5 to support this. Otherwise, any release should work for you.

 

[tdaugirdas]

To check the vintage - dial into the admin mailbox, enter your password and press 7 - it will give you the firmware and software release.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[gatorbeetle]

Yes, we have the visual display of message count.

Is it possible to replace the HDD in these cards and restore from the card?

 

[gatorbeetle]

Thanks, Tom, but the VM system is acting like all ports are full, it will not let me dial in. I will look at what WinSPM says a little more closely for the card.

 

[tdaugirdas]

WinSPM won't tell you much. Try restarting the VM (and it does sound like your drive has crashed - at least partially). See if you can get in to the admin mailbox - to check vintage. If not - you need to get a new hard drive and maybe send in the module to upgrade the firware/software at the same time - if you want Release 4.0

I assume you did not do a backup via the LAN interface - in which case the messaging will need to be reprogrammed from scratch.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[gatorbeetle]

I have in the past backed it up with the LAN interface, just not sure how long ago.

When you say "restart VM" do you mean busy out-restore-reset? Because I have done that. If there is another way, please advise.

Thanks for the responses so far.

 

[tdaugirdas]

Turn the whole system off - and back on again - and pray.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[gatorbeetle]

Ok, I just ran the backup on Standard SPM in WinSPM. Does that cover the MM system as well, or is there something else I need to try for that?

 

[tdaugirdas]

The messaging can ONLY be fully backed up thru the LAN connection to a PC. A very limited configuration can be saved to the port license card.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[gatorbeetle]

Understood. I have run a backup through the LAN port on the Magix system (the processor is where I believe the port is, it is labeled ADMIN) thru WinSPM.

Does that also backup the messaging side of things?

 

[gatorbeetle]

Nevermind, I think I just answered my own question. I found the Messaging software on the Avaya CD, and installed it. I tried to access the port on the MM card to set an IP, so that I could access the LAN port. It advised that it could not connect, C: drive failure.

 

[gatorbeetle]

Ok, well, the part is on order, and a service call scheduled. I looked at the install and setup, and I don't even want to attempt it. i could probably make it work, but don't want to take the chance of a SNAFU (in the true definition of the word) and something not going off right, or it taking two days to complete.

Thanks to everyone for your help!! Much appreciated. I'll be counting the days until we get into the Office IP system.

 

[tdaugirdas]

That will be an INTERESTING project! Much more complex and tedious programming-wise than the Magix - and then, of course, there are the "bugs" to contend with.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[kmefford]

Tom I'd agree that the IP Office is more complex but beyond basic button programming, the Magix is VERY tedious to program. The "bugs" aren't a big problem if the tech installing the system know's what he's doing.

Since Gatorbeetle says he's more of a "computer person" once he's been trained on system administration, I would guess he will like the programming interface MUCH more.

 

[gatorbeetle]

I have always been a hardware/software/data guy. Our IT Chief quit last March, and I was thrown into his place...at least the raise was nice.

I am self taught for the most part with WinSPM on our Magix system. This is actually the first problem I was unable to troubleshoot and fix...although I had a gut feeling the board was bad from jump.

I have been introduced to the new system's GUI, and like what I see so far. Our install is being done by our telecom provider. They have alot of experience with much bigger shops than ours, plus we are going to get fully trained. I'm looking forward to it!

 

[kwing112000]

You should love the IPO. I have done all the Avaya line and all I install now is the IPO. Like Kmefford says as long as you have a good tech that puts it in then you shouldnt have any issues. With your computer background you should not have any issues with programming.

 

[gatorbeetle]

I really appreciate all the help and encouragement! Nice to find a friendly forum for once.