The Unified Messaging server failed to receive an incoming call for the user with DistinguishedName "%1" during the call with ID "%2" because the UM pipeline is full with the maximum number of allowed messages. This could be because a Hub Transport server or the user's Mailbox server is currently busy or unavailable. To correct this error, make sure that there is at least one Hub Transport server installed in the same Active Directory site as the Unified Messaging server and that a Hub Transport server and the Mailbox server are available.
The Unified Messaging server failed to exchange the required certificates with an IP gateway to enable Transport Layer Security ...
The Unified Messaging server failed to process the message with header file "%1" within "%2" minutes. The UM server will ...
The Unified Messaging server failed to process the message with header file "%1" within "%2" minutes. The UM server will ...
The Unified Messaging server failed to receive an incoming call for the user with DistinguishedName "%1" during the call ...
The Unified Messaging server failed to receive an incoming call for the user with DistinguishedName "%1" during the call ...
The Unified Messaging server failed to register for directory change notifications on the 'Servers' container. The Unified ...
The Unified Messaging server failed to register for directory change notifications on the 'Servers' container. The Unified ...
The Unified Messaging server failed to register for directory change notifications on the 'UM AutoAttendant' container. The ...
The Unified Messaging server failed to register for directory change notifications on the 'UM AutoAttendant' container. The ...