Hello,
We are running Exchange 2013 CU 3 and Lync 2013 rollup 8. For the most part, UM is working smoothly. Callers are able to call our main number (auto attendant) and transfer to a user's extension. No problem.
We have configured a Lync response group to serve as our operator...and this is where the issue begins. If we configure the response group with a five digit extension like our regular users, and set the operator extension as that 5 digit number, the auto attendant replies "Sorry, I couldn't transfer your call." If I switch the response group to a full E164 number and enter that as the operator extension (minus the +, of course) it works. While the response group is configured with the 5 digit extension, I can call it from within Lync without issue by extension...the problem only surfaces when the auto attendant tries to transfer. The application log on the UM server throws two events:
1136, MSExchange Unified Messaging
Log Name: Application
Source: MSExchange Unified Messaging
Date: 1/29/2015 9:37:20 AM
Event ID: 1136
Task Category: UMCore
Level: Warning
Keywords: Classic
User: N/A
Computer: xxxxx
Description:
An error occurred while transferring a call to "52000". Additional information: The call transfer type is "Blind.", the transfer target is "phone number". Call ID: "a29b56c9-35e5-4e1b-b199-a4d389cd54ee". Referred by:"".
Log Name: Application
Source: MSExchange Unified Messaging
Date: 1/29/2015 9:37:20 AM
Event ID: 1079
Task Category: UMCore
Level: Warning
Keywords: Classic
User: N/A
Computer: xxxx
Description:
The VoIP platform encountered an exception RequestUri=sip:xxxxx:5066;transport=Tls;ms-opaque=4c80a8b56130406c 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 "a29b56c9-35e5-4e1b-b199-a4d389cd54ee". 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.
Any ideas? Everything I've found seems to suggest disabling refer support within Lync, but that's already done---and on the whole, the issue is only affecting transfers to a response group via 5 digit extension.
Thanks in advance :)