Maybe with your CM wizardry you can just busy the voicemail trunk instead
Depending on MM release, you might have dialogic cards/hardware for PRI, or H323 trunking or SIP. AFAIK, there's nothing really scriptable in that regard except maybe stopping the MAS Service in windows if you wanted to work with that.
Haha, yes I'm using OSSI to busy out the trunks already. As we understand it, Modular Messaging will still try to send MWI sets through the MAS and it will still do it if the trunk is busied out. So this left us with lights that were out of sync.
So for maintenance, we have to busy the trunks AND disable the ports. It'd be nice to do both tasks with 1 click since we have to do it a few times a month with Microsoft Patching.
Let's say the trunk group members are busied out to MAS 2. And MAS 2 is now trying to set the light. The light won't get set because the trunk members are busied out - however MM thinks the light is set. That's where it gets out of sync.
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.