I have a MLM007 and the system just stop working. I can do a reset on the front of the MLM007 and the voice mail will restart and work for 2-4 days. I get the ERROR Log NO I-VMS PORT IN SERV. I have replaced the power supply for the system. Any ideas?
When you swapped out the 007 card - did everything work OK? versus before - with the previous drive? Or - did you have the same problem? If so, it appears that maybe it is the 2-port expansion module that is the culprit - even though you said it "passed" the port test. I guess I would also double check in system programmming to make sure that all voice mail ports are listed in your VM Calling Group. Is 7159 an extension?
You can go back to a 2-port. The #2 port (it's always the last one in the VM module)will turn on and off the messqge lights. If you have a lot of users you are effectively limited to 1 port, at times, available to answer calls. Was there any difference in the original reported problem after you swapped drives?
I just change the card out today. All is working ok.
I reused the old hard dirve.
I change the power supply (about 2 weeks ago) the VM worked for about 5 days then the same problem, just would go down. That is when I ran the test of ports/disk. No problems with the test.
You will have one less port. It is also usually the last port that turns on and off the message lights - and does outcalling - so I think we are back to a problem with your middle insert module. If you another one - I would swap them and see if the problem reoccurs.
I don't think it can turn on and off message lights if you removed it from the calling group. Referesh my memory - what did you do? Did you take the original hard drive and place it in a different 007 MLM? Did you move the old port card too? Or is this with a different port card? If so, then it could still be a software corruption issue on the drive.
OK - so you could still have a port card issue. If you have a spare or one you can borrow - swap it out and see if the problem goes away. If not, then the hard drive is the culprit (probably corrupted software).
I put the 4th port in a seperate calling group and set it up as IntegrtdVMI. This seem to be working. It turns off and on the vm message light.
My idea is that if the vm port need to be in a calling group (IntegrtdVMI) this will work. It will not be used for answering vm coverage but can turn on and off lights.
What do you think?
Their traffic in the main vm use only the first 3 ports. Under the reports I only see about 3 calls a day for the 4th port. The other port have many calls. Port 1 being the largest follow by the other 2 with reduce numbers. Port 3 only has about 20 calls per day
If it works - great! I assume you don't use "outcalling". But, it still doesn't answer the question of where the original problem was - the drive software or the middle port card insert. You pretty much excluded the motherboard and 1st two ports by swapping modules. I wonder what would happen - with the same setup you have now - if you switched back to the original 007 module - probably no change.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.