I've had this trouble before and I can't figure out what the fix was.

I have a repartee 7.45 VBPC DNIC for Mitel. As far as I can tell, I've done everything but the m/w light will not come on. I can see the ports go off hook and dial the *41150Q where *4 is the feature access code, 1 is for m/w on and 150 is the extension and I think Q is hang up. but no lights.
It also dials to turn off the lamp after I check the message.

In the phone system setup form, *41,X,Q is the string for m/w on and *42,X,Q is the string for m/w off. I've dialed each port individually and they all answer. Ports 4-8 are set to A/D. 1-3 are just Ans.

I've made a test phone with the same Mitel Class of Service as the voicemail and I can light/extinguish the lamps just fine. For some reason the vm dials the string but the lamp does not light.

isnt there supposed to be a # before the Q???

Do you mean an actual number or a # sign?

If I only put in the setup form *41, the mail dials out *41150Q which is correct (150 is the extension).

I forgot you mentioned that in your previous post. There has to be something with the port itself. Can you unplug the analog port from the voicemail and dial the codes? Does it light the lamp that way?

I tested from one of the actual v/m ports and the lamp lit up on the destination phone. these are digital phones

what actually happened was the voicemail began locking up the disk was really 'grinding' and i believed the hdd to be on its last legs so i made a new hard disk with a clean install of the software. The old hard drive lights the lamps perfectly but the new drive attempts to the light the lamps but doesn't happen. I spent most of the day checking all of the settings from one drive to other.

could there be some software that somehow got left out when i made a clean install of the o/s and the s/w?

does a new drive need some sort of activation code?

i'm grasping at ideas here and pulling my hair out.

1.) Make sure that the dongle is tightly attached to the parallel port.

2.) Watch the "banner" screen, and make a test call. One of the ports will be marked either A/D or A/L. A moment after you leave your message, this port (usually the last one) will go offhook and send your string "*41150Q." Make sure that the string you see is the right string.

2a.) If the string doesn't ever appear, the port may be locked up. Login. Press F3 until that port has >> next to it, then hit F4. The port will say "Local Connect." Hit F4 again. The port should go back to A/D, but this should reset the port, and all of the waiting message lamp signals should start streaming through.

2b.) If you do 2a. and don't see any message lamp signals, login, then page down until you see the ports. Highlight one of the ones that says "Ans" and type "A/D."

This port should become active and start streaming message lamps. Do another test call.

Finally, login, and then page down until you see "message waiting lamp reset = no"

Change this to "yes."

This will cause all message lamps to reset. You'll see your A/D ports pumping out message lamp signals. Normally this is done at 2 AM or something, but you'll want to let it run, to match lamps with mailboxes. If this is during normal business hours, people may report lamps going on and off. Tell them that this is normal, and wait for it to finish.

Hope that helps.

If not, you may want to redo your new HDD... Maybe do a "diskcopy" with an identical drive, or else use "xcopy32 /k/r/y/c/h/e/f *.* " (unconditional copy of all files).

Enjoy.
xcopy32 /

Use your butt set and monitor the port as it's trying to light the lamp. What do you hear? Also, in the Switch setup screen did you copy exactly what is there from the old drive? You can also try hooking the old drive into IDE 2 and use the XCOPY command to copy the VMAIL directory of the old drive to the new. But mind the drive letters as they will change if you use this method.

those are great points, thanks! This is a digital port so i don't think i can monitor it with a buttset.

The vmail will go off hook and dial the correct string to light the lamps.

The old hdd works correctly and it is interesting to note that it takes about 2-3 seconds for the port to light the lamp.

The new drive goes off hook and dials the string very quickly (1 second). So I've even changed the timers in the switch setup form to slow that down and put a , in the string but it doesn't help

if I do a disk copy, say of only the VMAIL directory, is that drive letter going to permanently change once I take out the old drive or would it go back to E once I'm done?

I don't have an identical drive. I have a 3.2 Gb maxtor as my new drive (brand new) and the old one was 2.1 Gb Quantum. Will this matter if I do the xcopy32 of everything?

The drive letter will go back to E: when you remove the second drive. It doesn't matter if the new drive is larger. It's actually better that way.

well, i have a diskjockey (disk to disk duplicator) and I tried that but it did not work because i believe there are bad sectors on the old drive. that xcopy32/PC stuff makes me a little hesitant, and i was ready to do it.

BUT I got it to work! I found some Y2k upgrade disks with a Y2k dongle, so thought I'd give those a shot.

I did the Y2k update (it never asked for the dongle) and rebooted and yes, now I have message waiting lamps! Weird but, I'll take it.

thanks guys. boo yah ka sha!

You have to be carefull with Mitel. First of all you have to make sure that only one and the same port is turning MW light ON & OFF. Secondly make sure that the port not in Hunting group and move all other ports to COS that has Message Send future Disable. Sometime with Repartee you have to adjust length off ring because Mitel won't respond on short ring. That is why with the test set you have no problem but with the port you do, even you see port is sending the right string.

everything seems to working fine, but i noticed that i lost power one night and the system did not reboot correctly. It's on a good UPS but I got an error message that Drive E was not shut down correctly and CHKDSK /f must be performed. I did the chkdsk /f and now it's working fine but my concern is that if this happens in the future and i'm not there or close-by.

is there and OS/2 command, option or feature that has to be enabled OR is this common with Repartee (but I've never had that other repartees)?

I think one of the batch files contains the call for chkdsk. Try autoexec.bat or one of the .bat files.