MWL don't come on

[cycochris]

It's a Legend 7.0 that was having all sorts of problems. It was having voicemail problems and processor issues that included the MWL not coming on.
Well, I replaced the processor and the voicemail and restored back to a known good restore point. That fixed everything but the MWL.
I refreshed the MWL, I cleared the MWL, and I pushed the VM reset. No joy.
Outcalling works perfectly, which was one of the original problems. I mention this because I think it uses the same port as MWL.

Any Suggestions?

 

[tdaugirdas]

Make sure all of voice mail ports are in the voice mail calling group. If you added any ports - they may not be. Test the last 2 VM ports directly - see if they answer. Make sure the voice mail calling group is linear and set as integrated voice mail. If there is a high volume of outcalling - it will delay meaasge light updates - because it is the same port.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[cycochris]

It is a 2 port MLM 007. They are both in the calling group.
It is set to linear and Integrated VM. I called both ports and they both answer.

In the office they have 8 people and only 2 use outcalling. They don't have a heavy call volume at all.

 

[tdaugirdas]

Well, it is that second port that should be doing all the work. Try this, reset or refresh the message lights and, at the same time, watch for activity on the 2nd vm port (it should turn red than green within 30 seconds or so. If the port does not do anything - then something is wrong with the voicemail software. Try leaving a test message for any extension with the MWL light off (even if you have to clear it at that phone) - again watch for activity on the 2nd port and see if the message light turns on. If nothing happens - then you probably have some corrupt software on the MLM hard drive. It sounds like you have tried pretty much everything else.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[cycochris]

I guess what my hang up is the fact that this is the second MLM007 that this problem has occured.
It has a new processor and a new VM.
Is there anyway the cabinet could cause this?

 

[ttech]

It could possibly be a bad TTR in another card in the system. you may want to test them.

 

[cycochris]

That is a little beyond my experience. Could you tell me how to do that?

 

[jgideon]

from another post:

to quote samh30:

Testing Touch-Tone Receivers

The 016 (T/R), 016 ETR, 400 GS/LS, and 412 LS-ID-TDL modules each provide
four touch-tone receivers (TTRs). The 008 OPT, 012 T/R, 800 DID, 800 GS/LS-ID
and MERLIN Messaging System modules each provide two TTRs. The 0X24 TDL module provides
eight touch-tone recivers.

To test TTRs, follow these steps:

1. Pick up the handset of a touch-tone single-line telephone that is connected to one of the
modules that provide TTRs.

2. Dial *04 and the 2-digit number (starting with 01) of the TTR that you want to test.
You should hear a busy tone if the receiver is in use.
You will hear a reorder tone if you misdialed or addressed a
receiver not in your system. (This can happen if, for example, you dialed 07 and your system has
only one 016 (T/R) module and one 800 GS/LS-ID module, for a total of six TTRs.)

3. If you hear reorder tone, try again.
If you hear dial tone after one to three seconds of silence, proceed with this test.

4. Dial 123456789*0#. You should hear a dual-tone multifrequency (DTMF)
signal as each button is pressed.
When you finish dialing, you should hear a 3-beep confirmation tone.

5. Repeat the test for each TTR.

Good Luck.

http://www.samhassan.com

 

[cycochris]

1. Pick up the handset of a touch-tone single-line telephone that is connected to one of the
modules that provide TTRs."

They have 2 408mlx, 800 DID, and mlm 007. Ca
Can the test be done from a MLX phone?

 

[tdaugirdas]

I believe you can only do the test from a single-line phone connected to an 012 or 016 module - which you do not have. Ypu could also check the processor error logs and see if they shows any TTR related errors. Have you tried the tests in my second post? What were the results?

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[cycochris]

When I cleared the MWL the 2nd port did turn red. But when I left a message it didn't turn red.

 

[cycochris]

Also, I added a 012 board to the system to see if I could a) add more ttr's and b) test the existing ttr's.

 

[tdaugirdas]

I am not sure the TTR issue will affect the working of the last port - except maybe every once in a while. It sounds like the software could be defective on your MLM. You said it was new. Was it a "used" unit or a trully new one? If used was it fully defaulted before you started programming? Did you run the port and hard disk tests? If not, I would suggest you do all of the above, i.e., connect via hyperterminal, run the port and hard disk tests, then reinitialize the software. Then do the minimal programming necessary to get the vm on line and see if it works correctly with respect to the MWLs.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[cycochris]

I tested all the ttr's and got two tones on all 6 (with the 012). I left a message and the 2nd port did light and it did when I cleared the lights as well.

The mlm007 that I put in was refurbished, but was defaulted. I did not test the hard drive or the ports..

 

[tdaugirdas]

When you left a message - and the 2nd port lit red briefly - did that turn on the message light at the phone? When you deleted the message, did the 2nd port briefly lite red and "turn off" the message light at the phone? If not, I suggest you do the what I mentioned in the previous post. After choosing shutdown from the menu, run the port test first, then the hard disk test. If there are sector errors on the drive - it may well mean corrupted software. If you have no hard drive errors, reinitialize the software, restart the module and test it out again.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[cycochris]

No, then message waiting light never came on at all. However, I could make it come on using feature 53. And off again using feature *53.

 

[tdaugirdas]

OK - so the voice mail is not sending the codes - either at all or not correctly. Time to do what I suggested to test the voicemail module - or return it for another one.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[tdaugirdas]

I know it is probably a dumb question, but I would double-check the voice mail setup in system programming - to make sure all is still correct, i.e., vm calling group 770 with correct hunt/group type and members, cover group 30 with all extensions needing vm coverage in it. 770 providing coverage for 30, etc.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[cycochris]

I checked it and all the basic programming is intact. I just tested thier original voicemail on my test system and it passed all the(hyper-teminal)tests. It sends the MWL just like it should. I'm going back over there with their old one and am going to give it a try.

Byt the way, is there a way to copy the information from the hard drive on the mlm007 to a different mlm007? Just curious.

 

[tdaugirdas]

If the drive is intact and has no sector errors - yes - it is possible to copy - but difficult - because of the proprietary software involved and weird BIOS settings. If it is a simple setup - you are better off reprogramming.

If you have a spare "known good" 007 in your shop - swap hard drives only and retest. If it works - then the software on the "refurbished" unit is corrupted. Or pull the drive and bring it with you. If the same problems occur with either hard drive module at your customer site - it could be a bad slot and/or processor problem.

Tom Daugirdas,
President
STCG, Inc.
stcg.com