We recently had an issue with NuPoint where all the voicemail ports went to a RNA state. Upon contacting vendor support for this issue, I was advised to reboot the MAS (MiCollab 7.1.0.35) server to reactivate the ports. Although this resolved the issues we were experiencing, no root cause was determined at the time. I've been asked by my manager whether we should do a scheduled reboot of the MAS (and other virtual servers in our Mitel environment) to hopefully prevent this from occurring again? Is there guidance or a best practice in the Mitel world that suggests a regularly scheduled reboot is needed and or beneficial?
I would say no... scheduled reboots are not required or recommended under normal circumstances. I have MiCollab servers that have been running for well over a year without a hiccup, and MBG's that have been running for several years.
Mitel MAS or MiCollab servers run Mitel Standard Linux, which is based on CentOS Linux... an extremely stable, enterprise grade Linux distribution. Linux in general does not need to be rebooted even for upgrades or patches, except if the kernel changes. There are *nix systems running out there with uptimes of 10+ years.
That said, properly rebooting the server should not have any negative effect on operation or performance either. Be sure you are maintaining regular backups though, just in case, although this has nothing to do with rebooting, it is just good practice.