The Unified Messaging server was unable to submit messages to a Hub Transport server because there is no Hub Transport server available to process the request with UM header file "%1". Make sure that there is a Hub Transport server located in the same Active Directory site as the UM server. In addition, make sure that the Microsoft Exchange Transport service is started on the Hub Transport server.
The Unified Messaging server updated the custom prompt cache for UM dial plan "%1". The name of the file that was updated ...
The Unified Messaging server was unable to create a message for the fax call with ID "%1". The following invalid media details ...
The Unified Messaging server was unable to issue a Session Initiation Protocol (SIP) Option request to the IP/VoIP gateway ...
The Unified Messaging server was unable to resolve the caller ID "%1" to a user in Active Directory or personal contact before ...
The Unified Messaging server was unable to submit messages to a Hub Transport server because there is no Hub Transport server ...
The Unified Messaging Service was unable to read the UM Worker Process retire time from the configuration data. The UM Worker ...
The Unified Messaging Worker Process (UMWorkerProcess.exe) encountered an unhandled exception "%1" during an incoming call ...
The Unified Messaging Worker Process has finished updating the speech grammar files for UM dial plans that are associated ...
The Unified Messaging Worker Process has started grammar generation for Automatic Speech Recognition. The log file is "%1". ...