Event Logs
Event logs are
important for troubleshooting Microsoft Exchange unified messaging.
Each of the different aspects of a Unified Messaging server generate
their own set of error messages. The tables of events show the errors
and events that could be generated for each of the following categories:
Call answering
Fax answering
Subscriber access
Auto Attendant
Administrative
System
Performance
The event log
messages are very detailed and specific to many conditions, making it
very easy to understand, audit, troubleshoot, and instrument the Unified
Messaging server.
Table 10 shows the error events that can be generated for call answering.
Table 10. Call Answering Errors and Events
| Description | Event Type |
|---|
| A diverted call was received for extension that is not enabled for unified messaging. | Informational |
| The
call is being refused because Active Directory is not available. The
call is from calling party calling-number and dialed called-number. | Warning |
| The
call is being refused because the bridgehead server is unavailable. The
call is from calling party calling-number and dialed called-number. | Warning |
| The bridgehead server is not available at the point of submission. The message is being stored locally. | Warning |
| The
call is being refused because the spooler has reached the maximum of n
messages. The call is from calling party calling-number and dialed
called-number. | Warning |
| Mailbox is unavailable. A greeting is being synthesized for this mailbox. | Informational |
| The session was terminated because the message is too long. | Informational |
| The caller was not able to leave a message because the target mailbox is full. | Informational |
| The message was not delivered because it is shorter than the minimum message length. | Informational |
Table 11 shows the error events that can be generated for fax calls.
Table 11. Fax Answering Errors and Events
| Description | Event Type |
|---|
| A fax tone was detected for mailbox, which is not enabled for fax. | Informational |
| A fax tone was detected on a system that is not enabled for fax. The call was for mailbox. | Informational |
| A fax tone was detected after a voice mail message was recorded. Two messages will be submitted for mailbox. | Informational |
| A
fax tone was detected, but the call is being dropped because the number
of concurrent fax calls has reached the maximum allowed. The call was
for mailbox. | Warning |
| A fax protocol error caused the call to terminate prematurely. The call was for mailbox. | Warning |
| The bridgehead server is not available at the point of submission. The message is being stored locally. | Warning |
| The
call is being refused because the spooler has reached the maximum of n
messages. The call is from calling party calling-number and dialed
called-number. | Warning |
| The fax call was refused because the target mailbox is full. | Informational |
Table 12 shows the error events that can be generated for fax calls.
Table 12. Subscriber Access Errors and Events
| Description | Event Type |
|---|
| The user failed to log on n times. The mailbox is now locked out. | Warning |
| The call-id was disconnected because the logon failed n times for mailbox. | Informational |
| User was disconnected after n incorrect responses. | Informational |
| The message that user attempted to send failed because their mailbox is full. | Informational |
| User reset their PIN. | Informational |
| User attempted to access their mailbox, which is locked out. | Informational |
| User failed to log on because their PIN checksum has been tampered with. | Warning |
| Language associated with mailbox is not installed. | Warning |
Table 13 shows the error events that can be generated by the Auto Attendant.
Table 13. Auto Attendant Errors and Events
| Description | Event Type |
|---|
| The caller was disconnected after n incorrect responses. | Informational |
| The referenced critical audio file was missing. | Error |
| The referenced audio file was missing. | Warning |
| The language referenced by the automated attendant is not installed. | Warning |
| The Auto Attendant name referenced an operator extension that is missing. | Error |
Table 14
shows the administrative events that can be generated by the Unified
Messaging server. These events make it easy to track what administrative
changes are being made within the UM system.
Table 14. Administrative Errors and Events
| Description | Event Type |
|---|
| The account for user was enabled. | Informational |
| The account for user was disabled. | Informational |
| The settings for user were modified. | Informational |
| The account was locked out. | Warning |
| The account was reenabled. | Informational |
| The PIN for user was changed. | Informational |
| User PIN policies were changed. | Informational |
| A server property was changed for server. | Informational |
| A dial plan property was changed for dial plan dial plan. | Informational |
| A new dial plan object dial plan was created. | Informational |
| Dial plan dial plan was removed. | Informational |
| An IP gateway property was changed for gateway. | Informational |
| A new IP gateway object gateway was created. | Informational |
| Gateway was removed. | Informational |
| Auto attendant AA was removed. | Informational |
| A UMAutoAttendant property was changed for auto attendant auto attendant. | Informational |
| A new auto attendant auto attendant was created. | Informational |
Table 15 shows the system error events that can be generated by the Unified Messaging server.
Table 15. Unified Messaging System Errors and Events
| Description | Event Type |
|---|
| The service is starting. | Informational |
| The service failed to start. The startup operation returned an error. | Error |
| The service started successfully. | Informational |
| The service started, but no IP gateway is defined for the dial plans associated with this server. | Warning |
| The service started, but the server is not associated with any dial plans. | Warning |
| Communication was established with IP gateway x. | Informational |
| The attempt to communicate with IP gateway x failed. | Error |
| TTS operation for language is being initialized. | Informational |
| TTS for language was initialized. | Informational |
| TTS for language failed. | Error |
| The Fax service was loaded. | Informational |
| Auto Attendant name is enabled. | Informational |
| Auto Attendant name is missing audio prompts. | Warning |
| The Operator extension is missing. | Warning |
| The UM server is preparing to shut down and is not accepting new calls. | Informational |
| The service is being stopped. | Informational |
| The service could not be stopped. | Warning |
| The UM server is shutting down immediately. X current calls will be disconnected. | Warning |
| The UM service encountered an unhandled exception during call ID. The call has been disconnected. | Error |
| The conversion request was denied because the TTS concurrent sessions limit was exceeded. | Warning |
| The TTS engine threw an exception. | Error |
| TTS engine error. TTS failed to convert text. | Error |
| A new call arrived without any call signaling information. | Warning |
| A UM working process is shutting down and not processing new calls. | Informational |
| A UM working process is shutting down immediately and dropping x existing calls. | Error |
| A new UM server worker process was created. | Informational |
Table 16 shows the performance warning events that can be generated by the Unified Messaging server.
Table 16. Unified Messaging Performance Errors and Events
| Description | Event Type |
|---|
| The
operation has exceeded 4 seconds. The calling number was X, the called
number was Y. The mailbox Z was performing the operation. | Warning |
| TTS conversion failed to return audio within x seconds. | Warning |
Removing the First UM Server in a Dial Plan
The unified
messaging prompt publishing point for a dial plan is automatically set
at the time that the first Unified Messaging server joins the dial plan.
Before you can remove the first Unified Messaging server, you need to
migrate all of the custom prompts and then set the new server as the
prompt publishing point.
For each dial plan that
has a prompt publishing point on the server to be removed, run the
following Exchange Management Shell command:
Set-UMDialPlan -Identity <Dial_Plan_Name> -PromptPublishingPoint
<UNC_Path_to_PromptPublishingPoint_Share_On_New_Server>
Then
copy all of the contents of the old Universal Naming Convention (UNC)
path to the new UNC path. The first Unified Messaging server can now be
removed safely.
