Export (0) Print
Expand All
Collapse the table of content
Expand the table of content
Expand Minimize

Troubleshooting UM.CallRouter Health Set

 

Applies to: Exchange Server 2013

Topic Last Modified: 2015-03-09

The Microsoft Exchange Unified Messaging (UM) Call Router health set monitors the overall health of the UM Call Router service.

If you receive an alert that specifies that UM is unhealthy, this indicates an issue that may prevent users from using the UM service in your organization. The UM health set is closely related to the following health sets:

Troubleshooting UM Health Set

Troubleshooting UM.Protocol Health Set

The UM.Protocol service is monitored by using the following probes and monitors

 

Probe Health Set Dependencies Associated Monitors

UMCallRouterTestProbe

UM.CallRouter

Active Directory Domain Services (AD DS)

UMCallRouterTestMonitor

For more information about probes and monitors, see Server health and performance.

It's possible that the service recovered after it issued the alert. Therefore, when you receive an alert that specifies that the health set is unhealthy, first verify that the issue still exists. If the issue does exist, perform the appropriate recovery actions outlined in the following sections.

  1. Identify the health set name and the server name in the alert.

  2. The message details provide information about the exact cause of the alert. In most cases, the message details provide sufficient troubleshooting information to identify the root cause. If the message details are not clear, do the following:

    1. Open the Exchange Management Shell, and then run the following command to retrieve the details of the health set that issued the alert:

      Get-ServerHealth <server name> | ?{$_.HealthSetName -eq "<health set name>"}
      

      For example, to retrieve the UM.CallRouter health set details about server1.contoso.com, run the following command:

      Get-ServerHealth server1.contoso.com | ?{$_.HealthSetName -eq "UM.CallRouter"}
      
    2. Review the command output to determine which monitor reported the error. The AlertValue value for the monitor that issued the alert will be Unhealthy.

    3. Rerun the associated probe for the monitor that is in an unhealthy state. Refer to the table in the Explanation section to find the associated probe. To do this, run the following command:

      Invoke-MonitoringProbe <health set name>\<probe name> -Server <server name> | Format-List
      

      For example, assume that the failing monitor is UMCallRouterTestMonitor. The probe associated with that monitor is UMCallRouterTestProbe. To run that probe on server1.contoso.com, run the following command:

      Invoke-MonitoringProbe UM.CallRouter\UMCallRouterTestMonitor -Server server1.contoso.com | Format-List
      
    4. In the command output, review the Result value of the probe. If the value is Succeeded, the issue was a transient error, and it no longer exists. Otherwise, refer to the recovery steps outlined in the following sections.

When you receive an alert from a health set, the email message contains the following information:

  • Name of the server that sent the alert

  • Time and date when the alert occurred

  • Authentication mechanism used, and credential information

  • Full exception trace of the last error, including diagnostic data and specific HTTP header information

    Note   You can use the information in the full exception trace to help troubleshoot the issue. The exception generated by the probe contains a Failure Reason that describes why the probe failed.

Sip Options to UM Call Router Service have failed

Determine whether the UM Call Router service is disabled. If the UM Call Router service is not started or disabled, restart the UM service.

More than 50% of Inbound Calls were Rejected by the UM Call Router over the Last Hour

Review the event logs on the Client Access server (CAS) to determine whether the UM objects, such as umipgateway and umhuntgroup, are configured correctly.

If the event logs do not contain enough information, you may have to enable UM event logs at the Expert level, and then review the UM trace log files.

More than {0}% of Missed Call Notification Proxy failed at UM Call Router over the Last Hour

Review the event logs on the CAS to determine whether the UM objects, such as umipgateway and umhuntgroup, are configured correctly.

If the event logs do not contain enough information, you may have to enable UM event logs at the Expert level, and then review the UM trace log files.

The Microsoft Exchange Unified Messaging Call Router certificate is nearing its expiration date

Renew the UM Call Router service certificate on the CAS.

Additional troubleshooting steps:

  1. Start IIS Manager, and then connect to the server that’s reporting the issue to determine whether the MSExchangeServicesAppPool application pool is running.

  2. In IIS Manager, click Application Pools, and then recycle the MSExchangeServicesAppPool application pool by running the following command from the Shell:

    %SystemRoot%\System32\inetsrv\Appcmd recycle MSExchangeServicesAppPool
    
  3. Rerun the associated probe as shown in step 2c in the Verifying the issue still exists section.

  4. If the issue still exists, recycle the IIS service by using the IISReset utility or by running the following command:

    Iisreset /noforce
    
  5. Rerun the associated probe as shown in step 2c in the Verifying the issue still exists section.

  6. If the issue still exists, restart the server.

  7. After the server restarts, rerun the associated probe as shown in step 2c in the Verifying the issue still exists section.

  8. If the probe continues to fail, you may need assistance to resolve this issue. Contact a Microsoft Support professional to resolve this issue. To contact a Microsoft Support professional, visit the Exchange Server Solutions Center. In the navigation pane, click Support options and resources and use one of the options listed under Get technical support to contact a Microsoft Support professional. Because your organization may have a specific procedure for directly contacting Microsoft Product Support Services, be sure to review your organization's guidelines first.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft