FYI, Avaya eventually discovered the source of this issue. It seems that it takes a while for the MSS to synchronize with the server that that runs the Me features. So you can't simultaneously reboot the MSS and Me features servers, but must do them sequentially.
We haven't been able to...
Call Me, Notify Me, MWI, and Mailbox Monitor are all running only on that MAS.
We just installed SP11 Monday morning, and some users had their Me features stop working, as usual, since we had to reboot that MAS.
Thank you for the advice. I'm not sure if we can implement moving these services to an MAS with ports due to other reasons, but I will see if we can try it.
Our supplementary server no longer has tracing, but is listed as a MAS that has no ports. This service was moved to the offline store...
We have 3 MASs that take calls, one that runs the Call Me, Notify Me, and MWI, and an offline store. Installing SP11 this weekend, so we expect it to break some subscribers' rules again. Avaya is going to capture before-and-after data, but I don't know specifically what they are going to capture.
Just curious if anyone else has experienced an issue like this. We are running MM3.1 SP10 with MSS. Whenever we reboot the server that runs these features, some people's features stop working. We haven't found any consistency in the users.
The rules LOOK like they are intact. The way we fix...
My understanding is that the email address is for MM's purposes. If you want email notifications, you can use the Notify Me feature in WSO.
Depending on your needs, you might want to set up 2222 as a secondary extension under 1111. Then you don't need a mailbox for 2222 at all. Any voicemail...
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.