Calls Initiated with Exchange Unified Messaging Subscriber Access or Auto-Attendant Do Not Connect or Are Not Routed Properly
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
If calls initiated with Exchange Unified Messaging Subscriber Access or Auto-attendant do not connect or are not routed properly, you can troubleshoot the issue as follows:
Use Exchange UM Integration Utility (Ocsumutil.exe) to verify that the name of the Office Communications Server Enterprise Voice location profile matches the fully qualified domain name (FQDN) of the SIP dial plan that is configured for Unified Messaging.
Verify that a Unified Messaging IP gateway is created for the Office Communications Server pool to which the calls are being routed. If not, use ExchUCutil.ps1 to create the gateway.
Verify that outbound dialing normalization rules that support the dialing patterns Unified Messaging sends to Office Communications Server are defined and that the location profile is configured to use those normalization rules.