Office Communicator cannot place calls to the Exchange Unified Messaging (EUM) Auto Attendant (AA).
This issue occurs because the EUM AA that is associated with the Office Communications Server (OCS) pool was created by using a display name that contains spaces.
To resolve this issue, the following actions must be taken:
The EUM AA that is associated with the OCS pool that has a display name that contains space characters must be removed and then replaced with an EUM AA that has a display name that contains no space characters.
The configuration steps that are needed to integrate the EUM AA with the OCS pool must be followed.
To do this, you will make changes from the following two locations:
Exchange Management Console (EMC) or from the Exchange Management Shell (EMS)
Communications Server front-end server
To remove and then replace the EUM AA, use the following instructions:
To make sure that the new EUM AA is recognized by the OCS pool infrastructure, follow these steps:
On an OCS Pool Front End Server, open Windows Explorer, and then browse to the following folder:
%Program Files%\Common Files\Microsoft Office Communications Server 2007\Support\
Double-click the OcsUmUtil.exe file to start it.
In the Exchange UM Integration Utility dialog box, click Load Data.
From the Exchange UM Dial Plan Forest drop-down selector, select the forest domain that is hosting the OCS and EUM infrastructure.
Use the Add or Edit button in the Exchange UM Integration Utility dialog box to configure the new EUM AA.
If the EUM dial plan for the OCS pool supports a System Attendant (SA) configuration, make sure that the SA configuration is added together with the EUM AA configuration in the Exchange UM Integration Utility dialog box.
When the configuration is complete, close the Exchange UM Integration Utility dialog box.
The error message that the OC client provides when the call to the EUM AA fails seems to be nonessential. To confirm that this is the issue that is occurring with the OC client, follow these steps:
Download the OCS 2007 R2 Resource Kit Tools, and then install them onto the Windows client that hosts the OC client.
On the OC client that is providing the error, turn on the client logging feature that is available on the General tab through the OC client's Tools, Options menu.
Click to select the Turn logging on in Communicator check box.
Use the OC client to dial in to the EUM AA to re-create the error message.
Exit the OC client.
Use Windows Explorer on the Windows client to locate the following folder:
%Program Files%\Office Communications Server 2007 R2\ResKit\Tracing
Double-click the Snooper.exe file to start the Snooper SIP capture utility.
Use Snooper to locate and then open the following file:
Microsoft Exchange Server 2010 Enterprise, Microsoft Exchange Server 2007 Enterprise Edition, Microsoft Exchange Server 2007 Standard Edition, Microsoft Exchange Server 2010 Standard, Microsoft Office Communications Server 2007 R2 Standard Edition, Microsoft Office Communications Server 2007 R2 Enterprise Edition, Microsoft Office Communicator 2007 R2, Microsoft Office Communicator 2007, Microsoft Office Communications Server 2007 Enterprise Edition, Microsoft Office Communications Server 2007 Standard Edition