Exchange UM Auto Attendant cannot transfer calls to a phone or extension number in Skype for Business Server 2015

Applies to: Skype for Business Server 2015

Consider the following scenario:
  • You upgrade to or install Microsoft Skype for Business Server 2015.
  • Your Exchange Unified Messaging (UM) Auto Attendant (AA) contact is hosted on a Skype for Business Enterprise Edition Pool or Standard Edition server.
  • An incoming PSTN (external caller) call reaches the UM Auto Attendant and is blind transferred to a Skype for Business user or to an RGS that does not have a dedicated DID number.
In this scenario, the call fails, and your Gateway server may generate a 404 error message. The calling party may also hear the following announcement from the AA:

"Call cannot be transferred, returning to the main menu."
Internal Lync users can still successfully transfer calls to the user or RGS.

Additionally, you may observe the following errors logged in the event log on your Exchange UM server:


This problem occurs because of a known issue in Skype for Business Server 2015.


To work around this issue, move your Exchange UM AA object to a previous version of Microsoft Lync Server (Microsoft Lync Server 2013 or Microsoft Lync Server 2010).

To move your Exchange UM contact objects, run the following Move-CsExUmContact cmdlet:

Get-CsExUmContact | Where-Object {$_.AutoAttendant -eq $True} | Move-CsExUmContact -Target FQDN
For more information, see the following TechNet topic:


To resolve this problem, install the June 2015 cumulative update 6.0.9319.55 for Skype for Business Server 2015 (Front End server and Edge server).


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.