Experienced an issue where voicemail functionality was not working for Lync users homed on a SBA after creating a new Exchange UM dial plan, policy, and auto attendant. Lync and Exchange UM integration had already been configured and was working for all other pools including central and branch sites.
The following error was appearing in the Event Logs of the Lync SBA:
Log Name: Application
Source: MSExchange Unified Messaging
Date: 9/10/2013 3:08:52 PM
Event ID: 1400
Task Category: UMCore
Level: Warning
Keywords: Classic
User: N/A
Computer: <ExUM FQDN>
Description:
The following UM IP gateways did not respond as expected to a SIP OPTIONS request.
Transport = TLS, Address = <SBA FQDN>, Port = 5061, Response Code = 0, Message = This operation has timed out.
Transport = TLS, Address = <SBA FQDN>, Port = 5061, Response Code = 0, Message = This operation has timed out.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange Unified Messaging" />
<EventID Qualifiers="32772">1400</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-09-10T22:08:52.000000000Z" />
<EventRecordID>467540</EventRecordID>
<Channel>Application</Channel>
<Computer>ExUM FQDN</Computer>
<Security />
</System>
<EventData>
<Data>Transport = TLS, Address = <SBA FQDN>, Port = 5061, Response Code = 0, Message = This operation has timed out.
Transport = TLS, Address = <SBA FQDN>, Port = 5061, Response Code = 0, Message = This operation has timed out.
</Data>
</EventData>
</Event>
The following is the error that was appearing in SIP Traces from OCS Logger:
15003;reason="The specified Exchange Unified Messaging dial plan is unknown";source="<SBA FQDN>";dialplan="<ExUM DialPlan>";appName="ExumRouting"
Resolution:
Step 1: Please install the following hotfix on all servers running Windows Server 2008 R2. Without this hotfix, the OCS server is not able to establish a TLS connection with the Exchange 2010 server installed on Windows Server 2008 R2. The reason being that an application or service that calls the InitializeSecurityContext function together with the ISC_REQ_EXTENDED_ERROR flag may encounter a TLS/SSL negotiation failure on a computer that is running Windows Server 2008 R2 or Windows 7
http://support.microsoft.com/kb/975858/
Step 2: Run Windows Updates and install all the updates.