Lync 2010 client cannot place calls to the Exchange Unified Messaging Auto Attendant

  Lync 2010 client is unable to place a call to the Exchange Unified Messaging (EUM) Auto Attendant (AA)

  The EUM AA that is associated with the Lync Server 2010 (LS 2010) pool was created with a display name that contains spaces.

The resolution for this issue requires that:

• The EUM AA that is associated with the LS 2010 pool  that has a display name with space characters in it
• Be removed and replaced with a EUM AA that has a display name with no space characters
• Followed by the needed configuration steps to integrate the EUM AA with the LS 2010 pool

This procedure can be accomplished by making changes from the following two locations:

• From the Exchange management Console (EMC) or from the Exchange Management Shell (EMS)
• From the LS 2010 front end server

To remove and replace the EUM AA use the instructions listed below:

Managing UM Auto Attendants

Once the EUM AA has been re-created use the following Exchange Powershell cmdlet from the EMS to associate the EUM Dial plan with the LS 2010 pool object:

 %Program Files%\...\Scripts\v14>.\ExchUcUtil.ps1

To make sure that the new EUM AA is recognized by the LS 2010 pool infrastructure:

1. On an LS 2010 Pool Front End Server open Windows Explorer and browse to the following folder: %Program Files%\Common Files\Microsoft Communications Server 2010\Support\
2. Double click on the OcsUmUtil.exe file to launch it
3. Click on the Load Data button on the Exchange UM Integration Utility dialog
4. Choose the Forest domain that is hosting the LS and EUM infrastructure from the Exchange UM Dial Plan Forest drop down selector
5. Use the Add or Edit buttons on the Exchange UM Integration Utility dialog to configure your new EUM AA
6. If your EUM dial plan for the LS 2010 pool supports a System Attendant (SA) configuration make sure that it is added with the EUM AA configuration in the Exchange UM Integration Utility dialog.
7. When the configuration is complete close the Exchange UM Integration Utility dialog

The error message that the Lync 2010 client provides when the call to the EUM AA fails appears to be non - essential.

To confirm that this is the issue that is occurring:

1. Download the Lync Server 2010 Resource Kit Tools and install them onto the Windows client that hosts the Lync 2010 client
2. On the Lync 2010 client that is providing the error turn on the client logging feature that is available the General tab through the Lync 2010  client's Tools, Options menu
3. Check Turn logging on in Lync checkbox
4. Click on the OK button
5. Use the Lync 2010  client to dial into the EUM AA to re-create the error message
6. Exit out of the OC client
7. Use Windows Explorer on the Windows client to locate %Program Files%\Lync Server 2010 \ResKit\Tracing folder
8. Double-click on the Snooper.exe file to launch the Snooper SIP capture utility
9. Use Snooper to locate and open the %userprofile%\Tracing\communicator-uccpapi-0.uccapilog
10. Use the search feature of Snooper.exe to search for "The application specified an invalid request-uri"
11. The results of the search should be similar to the SIP response packet information that is listed below:

Trace-Correlation-Id: 3157480233 Instance-Id: 000046EA Direction: outgoing;source="local" Peer: 10.0.0.122:49382 Message-Type: response Start-Line: SIP/2.0 400 Bad request From: "Thomas Anderson"<sip:thomas@contoso.com>;tag=d188533aa4;epid=d01f1abc1f To: <sip:+59999@contoso.com;user=phone>;tag=1B2988822268927BC8E1B9B1FA6A0096 CSeq: 1 INVITE Call-ID: 6260c8dc7bf74c68b02287145d211093 Authentication-Info: TLS-DSK qop="auth", opaque="F952C736", srand="54B4DF14", snum="15",  rspauth="8f86570efd6df642296ea281242bdc684db93fb1", targetname="ocsserver.contoso.com", realm="SIP Communications  Service", version=4 Via: SIP/2.0/TLS 10.0.0.122:49382;ms-received-port=49382;ms-received-cid=1C2C00 ms-diagnostics: 1;reason="Service Unavailable";AppUri="http%3A%2F%2Fwww.microsoft.com%2FLCS %2FExumRouting";reason="The application specified an invalid request-uri";source="ocsserver.contoso.com" Server: RTC/4.0 Content-Length: 0 Message-Body: � $$end_record

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.