NuPoint - Voicemail Port Problem

[rmeany]

Sorry if my question is poorly worded as I am rather new to working with Mitel and VoIP in general.

We have 19 lines on our NuPoint VMAS .. One line in particular is not picking up.  If I try to call that line directly it just rings forever (Actually, now I am getting DNDs, I am guessing because it appears to be ringing one of our main console's lines and the secretary must have figured out how to set it to DND)..  All 18 other lines work fine -  they get directed to the voice mail system before a single ring.

I would greatly appreciate some assistance in troubleshooting this..

[lundah]

The easiest solution would be to re-start NuPoint. There's also ways to re-start an individual port, either by re-loading it from the PBX or re-starting the processes on the NuPoint box itself, that varies a bit depending on the version.

[rmeany]

I don't want to disrupt service if at all possible.  Would you be able to point me in the right direction for figuring out how to go about restarting the service just for that particular line?

Mitel Applications Suite 5.0.61.0
Mitel Standard Linux 10.0.37
NuPoint unified messaging Build: 16.0.0.51.01

[lundah]

First thing to try would be to re-load the port from the 3300/MCD using Maintenance Command "load ipdevice <device number>". You can find the device number by doing "locate feature extension <port extension>".

If that doesn't work, you'll have to SSH in to the Nupoint text console, and exit out to the MSL shell. From there, you can do a "ps -ef |grep mitaiM" to pull up a list of the mitaiMonitor tasks for each port, then do a "kill -9 <pid>" on the pid (process ID) of the port in trouble. If that doesn't work, do the same process on the vmemo task instead of the mitaiMonitor. If that doesn't work, restart NuPoint.

[rmeany]

Thanks, I'll give that a try.

[rmeany]

Hmm.. The vMCD didn't work and SSHing into the vMAS brought up a server console that would not give me an option to exit out to linux.  I guess I'll just reboot the server after-hours and hope that works.

[bluewhite4]

If you ssh into the vMAS with a username of root instead of admin, it should take you to the linux console.

[rmeany]

That worked.. Thanks!

killing the vmemo process for that line resolved my issue.