SebD Posted May 28, 2015 Posted May 28, 2015 (edited) WARNING - Skype for Business Server 2015 has a normalization/matching bug - problem for those with Exchange Auto Attendants This is a known issue that is being worked on by MS, fix is expected in q3 2015. Post with updates on this issue is here Original post is below Hi All, I have just upgraded Lync server 2013 to Skype for Business 2015 and now when trying to dial response groups through my UM auto attendant they fail with "The call cannot be transferred, returning to the main menu... The call cannot be transferred, returning to the main menu" and then the phone call cuts out. Calls to the response groups directly from an internal phone work fine, and so does dialling an individual users extension. It's just when trying to call from outside to a response group. Anybody got any ideas? (I'm going to update exchange to CU8 tonight as we are on an older rollup and hope that it helps) Many thanks, Seb EDIT: It seems like it's not able to recognise the extension, if i dial an extension that i know doesnt exist (like 9999) i get the same error in the logs. If i dial 5052 i get straight through to a person, but if i dial 5050 which is set up as a response group it fails. EDIT 2: I have checked that the cert assigned to UM and UMCallRouter has the correct subject name. I have also checked that refer support is set to none. Log Name: Application Source: MSExchange Unified Messaging Date: 28/05/2015 13:45:32 Event ID: 1079 Task Category: UMCore Level: Warning Keywords: Classic User: N/A Computer: EXCHANGESERVER Description: The VoIP platform encountered an exception RequestUri=sip:mail.*******:5065;ms-fe=EXCHANGESERVER.********;transport=Tls;ms-opaque=b287473ddc086244 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.b__66() at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.<>c__DisplayClassf.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 "c9914db6-4969-4b04-b535-847330e53579". 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. Event Xml: 1079 3 2 0x80000000000000 3985108 Application EXCHANGESERVER.********* RequestUri=sip:mail.******:5065;ms-fe=EXCHANGESERVER.*****;transport=Tls;ms-opaque=b287473ddc086244 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.b__66() at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.<>c__DisplayClassf.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() c9914db6-4969-4b04-b535-847330e53579 Edited May 28, 2015 by SebD
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now