locked
Event ID's 1079 & 1136 = Hangups?

    Question

  • Can someone confirm that Event ID's 1079 & 1136 in tandem are quite often the result of a caller hanging up after the auto attendant has initiated the tranfer to an extension?

    We have been experiencing a few call issues with Lync, so I have been looking at my Lync and UM logs quite a bit. This combination of errors show up very frequently in my event logs. I can generate the same errors by letting AA initiate a call to an extension then hanging up after a few rings.

    My only concern would be that some of them are not due to this issue so I was wondering if there was any information in the events that might make it easy to spot?

    Saturday, March 03, 2012 2:10 AM

All replies

  • Hi,

    Can you please post the event details.

    Have set the Exchange Diagonastic Logging to High or Expert level,the Lowering it will solve the issue.

    Saturday, March 03, 2012 5:39 PM
  • Below is the full text of both events. All logging levels are and have been on the "Lowest" level.

    Log Name:      Application
    Source:        MSExchange Unified Messaging
    Date:          3/6/2012 10:33:20 AM
    Event ID:      1136
    Task Category: UMCore
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    An error occurred while transferring a call to "2758". Additional information: The call transfer type is "Blind.", the transfer target is "phone number", and the caller ID is: "899a14e6-5e05-4f88-a674-0c798d12bd05".
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange Unified Messaging" />
        <EventID Qualifiers="32772">1136</EventID>
        <Level>3</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-03-06T16:33:20.000000000Z" />
        <EventRecordID>42141</EventRecordID>
        <Channel>Application</Channel>
        <Computer></Computer>
        <Security />
      </System>
      <EventData>
        <Data>Blind.</Data>
        <Data>phone number</Data>
        <Data>2758</Data>
        <Data>899a14e6-5e05-4f88-a674-0c798d12bd05</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MSExchange Unified Messaging
    Date:          3/6/2012 10:33:20 AM
    Event ID:      1079
    Task Category: UMCore
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:     
    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 "899a14e6-5e05-4f88-a674-0c798d12bd05". 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.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange Unified Messaging" />
        <EventID Qualifiers="32772">1079</EventID>
        <Level>3</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-03-06T16:33:20.000000000Z" />
        <EventRecordID>42140</EventRecordID>
        <Channel>Application</Channel>
        <Computer></Computer>
        <Security />
      </System>
      <EventData>
        <Data>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.&lt;&gt;c__DisplayClass5f`1.&lt;&gt;c__DisplayClass62.&lt;WrapCallback&gt;b__5e()
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.&lt;&gt;c__DisplayClassd.&lt;CatchAndFireOnError&gt;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</Data>
        <Data>899a14e6-5e05-4f88-a674-0c798d12bd05</Data>
      </EventData>
    </Event>

    Tuesday, March 06, 2012 4:49 PM
  • I have exactly same issue. When caller press "0" during hearing greeting on voicemail, caller get "Sorry, the call cannot be transferred...." and it come back to voicemail. At this moment 2 warning Events are generated on Exchange server - 1079 and 1136, exactly as shown above. Looks like serious issue and many people experience the same issue.

    Any solution for this one?

    Thursday, September 13, 2012 2:19 PM
  • Ok, here is an update: problem is fixed!

    I gave up and decided to open Microsoft case for this. The guy from India was very professional and helped to find root cause and resolve issue under 30 minutes.

    Root cause: apparently SSL certificate used by UM service role should have Subject Name the same as FQDN of the UM server. When Exchange and Lync talk to each other during call transfer thing, they need to have a handshake secure channel established. If SN on SSL does not match FQDN of the UM server - no honey!

    In my case I was using one SSL with 20 SAN names in it - Lync, Exchange, external/internal names etc. Even though all looks good, it did not work. Since Exchange and Lync are internal and trust AD, here is what I did:

    1. Requested new SSL for each of my UM servers (MMC --> get SSL online from AD CA) with Server and Client authentication purposes.

    2. Re-assigned UM service role from my Commercial SSL certificate to new AD-based certificate

    3. Re-started Unified Messaging service on all UM servers

    Now everything is working. Knowing how many people having this issue, I would assume that this can be potential solution for other people too, so I will copy/paste this information into other threads as well.

    My issue is now resolved. It was a good experience though.

    • Proposed as answer by lync15 Friday, September 14, 2012 7:26 PM
    Friday, September 14, 2012 7:26 PM
  • Just an additional note, if the certs are correct and you still get these errors, be sure to check that "Refer Support" is set to "None" under Trunk Configuration in the Lync Server Control Panel.

    References: http://support.microsoft.com/kb/2508284 & http://matthewcevans.com/blog/2013/03/16/lync-2010-to-lync-2013-migration-issue-with-dial-in-conferencing-and-sip-trunk-with-refer/

    Thursday, December 05, 2013 1:39 PM