Using Cisco Unity 4.1 Build 4.1(1) w/on box exchange (VM only), the UnityMTA folder will start collecting VM messages and not deliver them to Exchange. Funny thing is that it only happens with unknown outside calls.
Just this morning I had about 6 messages in the UnityMTA folder and all of them were marked as being from unknown callers. When I dialed my extension from another Cisco phone and left a message it was delivered fine. When I called my extension with my cell phone and left a message it ended up in the UnityMTA folder and not delivered. After a reboot all the messages were sent and everything was back to normal.
No errors reported in Event Viewer at all.
What causes such behavior? I am constantly watching the MTA folder now incase Unity decides to not deliver messages again.
Right off hand my best guess is the "Unity Messaging System (server name)" account is missing or damaged - Unity should recreate the account if it's missing (it definitely does this when Unity is restarted). All outside caller messages are left from this account and if it's missing or damaged somehow and messages cannot be sent on behalf of this account, it'll be dropped into the MTA folder.
This would explain why sub to sub messages are working but outside caller messages are not. But that's just a guess based on the info here.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.