Exchange UM Auto Attendant cannot transfer calls to a phone or extension number in 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:

Log Name:      Application
Source:        MSExchange Unified Messaging
Date:          Date
Event ID:      1136
Task Category: UMCore
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Computer Name
Description:
An error occurred while transferring a call to "phone number". Additional information: The call transfer type is "Blind.", the transfer target is "phone number". Call ID: "call ID number". Referred by: "".

Log Name:      Application
Source:        MSExchange Unified Messaging
Date:          Date
Event ID:      1079
Task Category: UMCore
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Computer Name
Description:
The VoIP platform encountered an exception RequestUri=sip:SIP address:5066;transport=Tls RequestMessageType=NOTIFY
Microsoft.Rtc.Signaling.FailureRequestException:The transfer operation failed. For more information, refer to the message data in the exception.
   at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()
   at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult result)
   at Microsoft.Rtc.Collaboration.Call.EndTransferCore(IAsyncResult result)
   at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.BlindTransferSessionState.Call_TransferCompleted(IAsyncResult r)
   at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.SubscriptionHelper.<>c__DisplayClass67`1.<>c__DisplayClass6a.<WrapCallback>b__66()
   at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.<>c__DisplayClassf.<CatchAndFireOnError>b__b()
Detected at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at Microsoft.Rtc.Signaling.FailureRequestException..ctor(String message, Exception innerException, SipRequestData requestData)
   at Microsoft.Rtc.Collaboration.Call.CallTransferAsyncResult.Refer_StateChanged(Object sender, ReferStateChangedEventArgs e)
   at Microsoft.Rtc.Signaling.ReferStateChangedEventArgs.Microsoft.Rtc.Signaling.IWorkitem.Process()
   at Microsoft.Rtc.Signaling.WorkitemQueue.ProcessItems()
   at Microsoft.Rtc.Signaling.SerializationQueue`1.ResumeProcessing()
   at Microsoft.Rtc.Signaling.SerializationQueue`1.ResumeProcessingCallback(Object state)
   at Microsoft.Rtc.Signaling.QueueWorkItemState.ExecuteWrappedMethod(WaitCallback method, Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
 during the call with ID "9dbf5fb29bc340f3a4053b39ff4de2d1". This exception occurred at the Microsoft Exchange Speech Engine VoIP platform during an event-based asynchronous operation submitted by the server. The server will attempt to recover from this exception. If this warning occurs frequently, contact Microsoft Product Support.


Cause
This problem occurs because of a known issue in Skype for Business Server 2015.
Workaround
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:

Resolution
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).
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
خصائص

رقم الموضوع: 3069206 - آخر مراجعة: 06/25/2015 02:21:00 - المراجعة: 3.0

Skype for Business Server 2015

  • kbqfe kbsurveynew kbfix kbexpertiseinter KB3069206
تعليقات