Export (0) Print
Expand All

Unified Messaging Call Answering Errors and Events

Exchange 2010
 

Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2009-09-23

Microsoft Exchange Server 2010 Unified Messaging (UM) generates call answering events in Event Viewer so that you can troubleshoot and verify the performance of the call answering components, features, and services. Event Viewer tracks the following kinds of events in the following order based on importance:

  1. Error events
  2. Warning events
  3. Informational events

The following table provides a list of the call answering events that you can use to troubleshoot and monitor Unified Messaging.

Call answering events

Event ID Category Event type Logging Value or description Class

1004

UMCore

Information

LogAlways

A call was received with the following parameters: Calling Party: "%1", Called Party: "%2", Diversion Information: "%3", Call ID "%4".

Call Answering

1006

UMCore

Information

LogAlways

The Unified Messaging server has received a call from "%1", with user extension "%2" and a call ID of "%3".

Call Answering

1021

UMCore

Warning

LogAlways

The Unified Messaging server rejected an incoming call with the ID "%1". Reason: "%2"

Call Answering

1081

UMCore

Warning

LogAlways

The Unified Messaging server failed to receive an incoming call for user "%1" during the call with ID "%2" because a Hub Transport server is currently busy or not available. 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 is available.

Call Answering

1082

UMService

Error

LogAlways

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.

Call Answering

1109

UMCore

Warning

LogAlways

The Unified Messaging server has received an inbound call that has an invalid extension "%1" for UM dial plan "%2". The call ID is "%3".

Call Answering

1146

UMCore

Warning

LogAlways

The Unified Messaging server was unable to resolve the caller ID "%1" to a user in Active Directory or personal contact before attempting to submit voice mail to the Hub Transport server. The recipient of the message was "%2". More information: "%3"

Call Answering

1153

UMCore

Information

LogAlways

The Unified Messaging server received an incomplete number of digits for the extension number with ID "%1". The number of digits received was %2. This does not match the number of digits that was configured on dial plan "%3", which is %4. Because the number of digits does not match the number configured on the dial plan, the Unified Messaging server will send this call to the dial plan pilot number.

Call Answering

1169

UMCore

Warning

LogAlways

The user with extension "%1" is not enabled for Unified Messaging.

Call Answering

1170

UMCallData

Information

LogAlways

Call data: %1

Call Answering

 © 2010 Microsoft Corporation. All rights reserved.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft