locked
Cant transfer calls using Auto Attendant Key Mappings RRS feed

  • Question

  • Hi All  ,

    I have configured auto attendant to transfer to an extension using key maping  . But when I dial the option or says the phase  , AA cant transfer the call  .  If I dial the extension directly through AA call get transferred and connected  .

    I see the following warnings on Exchange UM  ,

    Log Name:      Application
    Source:        MSExchange Unified Messaging
    Date:          16/08/2012 11:30:31 AM
    Event ID:      1136
    Task Category: UMCore
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      server name
    Description:
    An error occurred while transferring a call to "9420". Additional information: The call transfer type is "Blind.", the transfer target is "phone number", and the caller ID is: "f3e49ab4-84f5-4461-853f-f9c67c52d57f".

    ---------------------------------------------------------------------------------------------------------------

    Log Name:      Application
    Source:        MSExchange Unified Messaging
    Date:          16/08/2012 11:30:31 AM
    Event ID:      1079
    Task Category: UMCore
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      <server name>
    Description:
    The VoIP platform encountered an exception Microsoft.Rtc.Signaling.OperationFailureException: Failed to transfer, successful refer notification not received
       at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()
       at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult result)
       at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult result, String operationId)
       at Microsoft.Rtc.Collaboration.Call.EndTransferCore(IAsyncResult result)
       at Microsoft.Rtc.Collaboration.AudioVideo.AudioVideoCall.EndTransfer(IAsyncResult result)
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.BlindTransferSessionState.Call_TransferCompleted(IAsyncResult r)
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.SubscriptionHelper.<>c__DisplayClass5f`1.<>c__DisplayClass62.<WrapCallback>b__5e()
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.<>c__DisplayClassd.<CatchAndFireOnError>b__9()
       Detected at System.Environment.get_StackTrace()
       at Microsoft.Rtc.Signaling.OperationFailureException..ctor(String message)
       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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
    FailureReason = 0 during the call with ID "f3e49ab4-84f5-4461-853f-f9c67c52d57f". This exception occurred at the Microsoft Exchange Speech Engine VoIP platform during an event-based asynchronous operation submitted by the Unified Messaging server. The Unified Messaging server will attempt to recover from this exception. If this warning occurs frequently, contact Microsoft Product Support.

    Thursday, August 16, 2012 1:50 AM

All replies

  • Hi,

    Please try to remove the check mark from the, Enable refer support option in the Lync Trunk Configuration to test the issue.


    Regards,

    Kent Huang

    TechNet Community Support ************************************************************************************************************************ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.


    • Edited by Kent-Huang Friday, August 17, 2012 3:30 AM
    Friday, August 17, 2012 3:29 AM
  • Hi Kent  ,

    Thanks for the reply  .  I dont have the refer support enable on Trunk Configuration  .

    regards,

    TR

    Friday, August 17, 2012 6:58 AM
  • Hi,

    Here is a similar issue just for your reference:

    http://social.technet.microsoft.com/Forums/en-US/exchangesvrunifiedmessaging/thread/cb9b8c7b-7888-4800-9443-612614991b9f/


    Regards,

    Kent Huang

    TechNet Community Support ************************************************************************************************************************ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.


    • Edited by Kent-Huang Thursday, August 30, 2012 6:56 AM
    • Proposed as answer by Kent-Huang Friday, August 31, 2012 8:52 AM
    Thursday, August 30, 2012 6:56 AM
  • Any resolution on this?  I'm having the same problem since migrating from lync 2010 to 2013...
    Sunday, December 2, 2012 2:56 AM