locked
Calls hitting the attendant are not being disconnected after X amount of time or x amount of errors RRS feed

  • Question

  • Setup is

    Exchange 2010

    Lync Server 2010

    Dial Plan is configured:

    Input failure before disconnect - 3

    Error log is logging 2 events for each bad extension entry:

    1136 & 1079

    but after 3 attempts it does not disconnect the call, it allows for attempt after attempt

    I think the issue is that the attempt is passed to lync and then when it fails and the call returns to UM, it is considered a new transaction.  See logs below

    1st 1079

    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 "462c04a826ff4e319889041cc836bdb1". 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.

    2nd 1136

    An error occurred while transferring a call to "8788". Additional information: The call transfer type is "Blind.", the transfer target is "phone number", and the caller ID is: "462c04a826ff4e319889041cc836bdb1". 

    Monday, January 28, 2013 8:06 PM