Delayed MWI

[JasonTaylor]

I've taken 1 of my 30 voicemail ports out of the VM hunt group to use as a RAD for an announcement. 

Since then users are complaining of delayed MWI, probably because the last port is no longer in the hunt group, so there is a delay until it gets to the next available port to send MWI.

I can't work out what's the fix?  If I change VM port capacity from 30 to 29, won't that remove my last VM/Rad port?

[JasonTaylor]

This is embedded voicemail on vMiVB

[JasonTaylor]

From reading from a few different forums it looks like the last VM port is always the default MWI port, so I've just configured a different port as the RAD and put the last one back into the Hunt Group.

[Dogbreath]

This was my experience also but official documentation for this behaviour has eluded me.

[acejavelin]

If you are using the embedded voice mail, never use the first or last port for anything but the voicemail hunt group.

I can't find the documentation to support it in the current documentation, but older versions stated this clearly... It has been this way since the days of the old Mitel Messenger card in the SX-200.

Failure to do this will result in delayed, or even none at all, MWI.