none
Exchange OWA integrated with Lync - OWA client disconnected from Lync after few minutes

    Question

  • Hello,

    We have a 2 node load balanced (via haproxy) CAS array that is integrated with Lync 2010. We are able to login to OWA on both of the CAS servers and can view other online users, send IMs, change status, etc everything with Lync integration seems to be working.

    The problem occurs when OWA is left idle for somewhere between 3-10 minutes. At some point in that period of time OWA seems to lose it's connection to the Lync front end server. The user signed into Lync via OWA shows up as offline to the rest of the users (using the Lync client), however in OWA the user still sees their status as available and other contacts still show up in the contact list with whatever status they had when the connection was lost.

    When the OWA user tries to send a message they receive 'This message couldn't be delivered to all recipients because some recipients are offline or don't want to be disturbed.' and when they try to change their status 'Your presence couldn't be changed. Please try again later.' is displayed.

    Changing from public/shared computer at login to private computer does not seem to matter.

    All exchange servers are Exchange Enterprise 2010 SP2 on Windows Server 2008 R2 Datacenter
    - 1xEdge Transport
    - 2xCAS/HT
    - 3xMailbox w/DAG
    Lync servers are Lync 2010 Enterprise on Windows Server 2008 R2 Datacenter
    - 1xFront End with A/V and mediation colocated
    - 1xMonitoring/Archiving

    Thanks for any help.

    Thursday, April 26, 2012 4:53 PM

Answers

  • This problem turned out to be related to a client timeout on the load balancer. We had the timeout set to 30 seconds and have now changed it to 60 minutes. We saw that after OWA was logged in and Lync IM was working in and out of OWA about 3-7 minutes later the load balancer would timeout a connection that the client did not respond to in a timely fashion. This timeout would occur several times (according to logs) and then the OWA user would show up as disconnected to the rest of the Lync clients even though everything looked fine in OWA.

    After changing this timeout value I have tested logging into OWA several times from a couple of computers and have not been disconnected yet. In fact my current test has been running for almost 1 hr 30 min. Still working with MS to determine why this timeout is breaking the OWA->Lync connection and why the OWA client isn't responding before the timeout occurs.

    • Marked as answer by Bay College Thursday, May 03, 2012 3:22 PM
    Thursday, May 03, 2012 3:22 PM

All replies

  • Hi,

    Can you enable logging on Frontend server and share the logs ?

    1. Enable S4 and Sipstack logging on FE.
    2. Reproduce the issue on outlook webapp.
    3. Filter the session on snooper and look for any errors?

    Thanks

    Saleesh


    If answer is helpful, please hit the green arrow on the left, or mark as answer.

    Friday, April 27, 2012 8:40 AM
  • Hi Bay,

    You can try to reproduce the failure, and do some troubleshooting with Lync Server Logging Tool first.

    For troubleshooting Lync and OWA integration, please refer to this article. Hope helps.


    Noya Lau

    TechNet Community Support

    Friday, April 27, 2012 9:41 AM
  • Hi Saleesh,

    I have turned on logging and after this issue occurs and sending an IM or changing the status via OWA does not generate any logs so it acts like the OWA client is completely disconnected from Lync. When I sign out of OWA and back in a message is displayed on the contact list that I am currently signed out. Once I click to sign back in everything connects and IMs/status changes work fine again.

    After reconnecting in OWA I enabled S4 and SIPStack logging. There were many events generated, but one second before the OWA user shows up as disconnected this series of events is in the logs (internal hostnames and IPs replaced):

    TL_INFO(TF_PROTOCOL) [0]09B8.1E70::04/27/2012-11:59:42.964.0006f7e9 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 1170120232
    Instance-Id: 00001B80
    Direction: incoming
    Peer: casarray.baycollege.edu:40640
    Message-Type: request
    Start-Line: SUBSCRIBE sip:lyncPool.baycollege.edu:5061;transport=tls;ms-fe=lyncFESrv.ADFQDN.edu SIP/2.0
    From: "owaclient"<sip:owaclient@baycollege.edu>;epid=5159B5D572;tag=8295a96c0
    To: <sip:owaclient@baycollege.edu>;tag=0B4E7B65
    CSeq: 54 SUBSCRIBE
    Call-ID: 03d2046828f34775b3edd233980892ad
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TLS CASHT_IPAddr:40640;branch=z9hG4bK7282d927
    CONTACT: <sip:owaclient@baycollege.edu;opaque=user:epid:KDAVPvdrmle8z1BfMEBBkQAA;gruu>;text;audio;video;image
    CONTENT-LENGTH: 0
    EVENT: vnd-microsoft-roaming-contacts
    EXPIRES: 0
    SUPPORTED: ms-dialog-route-set-update
    SUPPORTED: com.microsoft.autoextend
    SUPPORTED: ms-piggyback-first-notify
    SUPPORTED: ms-benotify
    SUPPORTED: gruu-10
    USER-AGENT: RTCC/3.5.0.0 OWA/14.02.0283.003
    Message-Body: –
    $$end_record

    TL_INFO(TF_DIAG) [0]09B8.1054::04/27/2012-11:59:42.980.0006ffb5 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: 03d2046828f34775b3edd233980892ad
    SIP-CSeq: 54 SUBSCRIBE
    Peer: casarray.baycollege.edu:40640
    Data: destination="casarray.baycollege.edu"
    $$end_record

    TL_INFO(TF_PROTOCOL) [0]09B8.1054::04/27/2012-11:59:42.980.0006fff0 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 1170120232
    Instance-Id: 00001B81
    Direction: outgoing;source="local"
    Peer: casarray.baycollege.edu:40640
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: "owaclient"<sip:owaclient@baycollege.edu>;epid=5159B5D572;tag=8295a96c0
    To: <sip:owaclient@baycollege.edu>;tag=0B4E7B65
    CSeq: 54 SUBSCRIBE
    Call-ID: 03d2046828f34775b3edd233980892ad
    Contact: <sip:lyncPool.baycollege.edu:5061;transport=tls;ms-fe=lyncFESrv.ADFQDN.edu>
    Via: SIP/2.0/TLS CASHT_IPAddr:40640;branch=z9hG4bK7282d927;ms-received-port=40640;ms-received-cid=50000
    Expires: 0
    Supported: ms-benotify
    Content-Length: 0
    Message-Body: –
    $$end_record

    TL_INFO(TF_PROTOCOL) [0]09B8.1E70::04/27/2012-11:59:42.980.00070212 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3068326657
    Instance-Id: 00001B82
    Direction: incoming
    Peer: casarray.baycollege.edu:40640
    Message-Type: request
    Start-Line: SUBSCRIBE sip:lyncPool.baycollege.edu:5061;transport=tls;ms-fe=lyncFESrv.ADFQDN.edu SIP/2.0
    From: "owaclient"<sip:owaclient@baycollege.edu>;epid=5159B5D572;tag=f428743be
    To: <sip:owaclient@baycollege.edu>;tag=6C3D0080
    CSeq: 56 SUBSCRIBE
    Call-ID: 213db2d29391471fb4545e7dc68a618f
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TLS CASHT_IPAddr:40640;branch=z9hG4bK12031dd
    ACCEPT: application/vnd-microsoft-roaming-self+xml
    CONTACT: <sip:owaclient@baycollege.edu;opaque=user:epid:KDAVPvdrmle8z1BfMEBBkQAA;gruu>;text;audio;video;image
    CONTENT-LENGTH: 0
    EVENT: vnd-microsoft-roaming-self
    EXPIRES: 0
    SUPPORTED: ms-dialog-route-set-update
    SUPPORTED: com.microsoft.autoextend
    SUPPORTED: ms-piggyback-first-notify
    SUPPORTED: ms-benotify
    SUPPORTED: gruu-10
    USER-AGENT: RTCC/3.5.0.0 OWA/14.02.0283.003
    Message-Body: –
    $$end_record

    TL_INFO(TF_DIAG) [0]09B8.1054::04/27/2012-11:59:42.980.000709df (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: 213db2d29391471fb4545e7dc68a618f
    SIP-CSeq: 56 SUBSCRIBE
    Peer: casarray.baycollege.edu:40640
    Data: destination="casarray.baycollege.edu"
    $$end_record

    TL_INFO(TF_PROTOCOL) [0]09B8.1054::04/27/2012-11:59:42.980.00070a1a (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3068326657
    Instance-Id: 00001B83
    Direction: outgoing;source="local"
    Peer: casarray.baycollege.edu:40640
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: "owaclient"<sip:owaclient@baycollege.edu>;epid=5159B5D572;tag=f428743be
    To: <sip:owaclient@baycollege.edu>;tag=6C3D0080
    CSeq: 56 SUBSCRIBE
    Call-ID: 213db2d29391471fb4545e7dc68a618f
    Contact: <sip:lyncPool.baycollege.edu:5061;transport=tls;ms-fe=lyncFESrv.ADFQDN.edu>
    Via: SIP/2.0/TLS CASHT_IPAddr:40640;branch=z9hG4bK12031dd;ms-received-port=40640;ms-received-cid=50000
    Expires: 0
    Supported: ms-benotify
    Content-Length: 0
    Message-Body: –
    $$end_record

    TL_INFO(TF_PROTOCOL) [0]09B8.1E70::04/27/2012-11:59:42.980.00070c5a (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 334779111
    Instance-Id: 00001B84
    Direction: incoming
    Peer: casarray.baycollege.edu:40640
    Message-Type: request
    Start-Line: SUBSCRIBE sip:lyncPool.baycollege.edu:5061;transport=tls;ms-fe=lyncFESrv.ADFQDN.edu SIP/2.0
    From: "owaclient"<sip:owaclient@baycollege.edu>;epid=5159B5D572;tag=80bcd36eac
    To: <sip:owaclient@baycollege.edu>;tag=84670080
    CSeq: 55 SUBSCRIBE
    Call-ID: d0aac0a02ebb41188c44e374f52fa948
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TLS CASHT_IPAddr:40640;branch=z9hG4bK589220e0
    CONTACT: <sip:owaclient@baycollege.edu;opaque=user:epid:KDAVPvdrmle8z1BfMEBBkQAA;gruu>;text;audio;video;image
    CONTENT-LENGTH: 0
    EVENT: presence
    EXPIRES: 0
    SUPPORTED: ms-dialog-route-set-update
    SUPPORTED: com.microsoft.autoextend
    SUPPORTED: ms-piggyback-first-notify
    SUPPORTED: ms-benotify
    SUPPORTED: eventlist
    SUPPORTED: gruu-10
    USER-AGENT: RTCC/3.5.0.0 OWA/14.02.0283.003
    REQUIRE: adhoclist,categorylist
    Accept: application/msrtc-event-categories+xml,application/xpidf+xml, application/rlmi+xml, text/xml+msrtc.pidf, application/pidf+xml, multipart/related
    Message-Body: –
    $$end_record

    TL_INFO(TF_DIAG) [0]09B8.1054::04/27/2012-11:59:42.980.0007149c (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: d0aac0a02ebb41188c44e374f52fa948
    SIP-CSeq: 55 SUBSCRIBE
    Peer: casarray.baycollege.edu:40640
    Data: destination="casarray.baycollege.edu"
    $$end_record

    TL_INFO(TF_PROTOCOL) [0]09B8.1054::04/27/2012-11:59:42.980.000714d7 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 334779111
    Instance-Id: 00001B85
    Direction: outgoing;source="local"
    Peer: casarray.baycollege.edu:40640
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: "owaclient"<sip:owaclient@baycollege.edu>;epid=5159B5D572;tag=80bcd36eac
    To: <sip:owaclient@baycollege.edu>;tag=84670080
    CSeq: 55 SUBSCRIBE
    Call-ID: d0aac0a02ebb41188c44e374f52fa948
    Contact: <sip:lyncPool.baycollege.edu:5061;transport=tls;ms-fe=lyncFESrv.ADFQDN.edu>
    Via: SIP/2.0/TLS CASHT_IPAddr:40640;branch=z9hG4bK589220e0;ms-received-port=40640;ms-received-cid=50000
    Expires: 0
    Supported: ms-benotify
    Content-Length: 0
    Message-Body: –
    $$end_record

    TL_INFO(TF_PROTOCOL) [0]09B8.1E70::04/27/2012-11:59:42.980.000716c9 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3451801877
    Instance-Id: 00001B86
    Direction: incoming
    Peer: casarray.baycollege.edu:40640
    Message-Type: request
    Start-Line: REGISTER sip:baycollege.edu SIP/2.0
    From: <sip:owaclient@baycollege.edu>;epid=5159B5D572;tag=4c292bc6e9
    To: <sip:owaclient@baycollege.edu>
    CSeq: 2 REGISTER
    Call-ID: 442adb3491fd40b4b78e4f341fbe628a
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TLS CASHT_IPAddr:40640;branch=z9hG4bK48e622f3
    CONTACT: <sip:casarray.baycollege.edu:5075;ms-fe=CASHTSrv.ADFQDN.edu;transport=Tls;ms-opaque=ccb1e2c36efbb620>;+sip.instance="<urn:uuid:3e153028-6bf7-579a-bccf-505f30404191>";text;audio;video;image
    CONTENT-LENGTH: 0
    EVENT: Registration
    EXPIRES: 0
    SUPPORTED: gruu-10
    SUPPORTED: ms-forking
    SUPPORTED: msrtc-event-categories
    USER-AGENT: RTCC/3.5.0.0 OWA/14.02.0283.003
    Message-Body: –
    $$end_record

    TL_INFO(TF_DIAG) [0]09B8.1E70::04/27/2012-11:59:42.995.00072393 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: 442adb3491fd40b4b78e4f341fbe628a
    SIP-CSeq: 2 REGISTER
    Peer: casarray.baycollege.edu:40640
    Data: destination="casarray.baycollege.edu"
    $$end_record

    TL_INFO(TF_PROTOCOL) [0]09B8.1E70::04/27/2012-11:59:42.995.000723d6 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 3451801877
    Instance-Id: 00001B87
    Direction: outgoing;source="local"
    Peer: casarray.baycollege.edu:40640
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: "owaclient"<sip:owaclient@baycollege.edu>;epid=5159B5D572;tag=4c292bc6e9
    To: <sip:owaclient@baycollege.edu>;tag=22CB3806F8BB1D44482364264ABFD8AA
    CSeq: 2 REGISTER
    Call-ID: 442adb3491fd40b4b78e4f341fbe628a
    Via: SIP/2.0/TLS CASHT_IPAddr:40640;branch=z9hG4bK48e622f3;ms-received-port=40640;ms-received-cid=50000
    Expires: 0
    Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft-roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft-provisioning-v2
    Supported: adhoclist
    Server: RTC/4.0
    Supported: msrtc-event-categories
    Supported: ms-keepalive-deregister
    Supported: ms-userservices-state-notification
    Content-Length: 0
    Message-Body: –
    $$end_record

    TL_INFO(TF_DIAG) [0]09B8.1054::04/27/2012-11:59:43.058.00072a62 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Routed a request on behalf of an application
    SIP-Start-Line: BENOTIFY sip:LyncClient_IPAddr:62133;transport=tls;ms-opaque=fdf0a329d1;ms-received-cid=D200;grid SIP/2.0
    SIP-Call-ID: 5bba21a0f95941539e8b76000e1104ec
    SIP-CSeq: 37 BENOTIFY
    Peer: LyncClient_IPAddr:62133
    Data: destination="lyncclient@baycollege.edu";application="http://www.microsoft.com/LCS/UserServices"
    $$end_record

    TL_INFO(TF_PROTOCOL) [0]09B8.1054::04/27/2012-11:59:43.058.00072aad (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 258650171
    Instance-Id: 00001B88
    Direction: outgoing;source="local"
    Peer: LyncClient_IPAddr:62133
    Message-Type: request
    Start-Line: BENOTIFY sip:LyncClient_IPAddr:62133;transport=tls;ms-opaque=fdf0a329d1;ms-received-cid=D200;grid SIP/2.0
    From: <sip:lyncclient@baycollege.edu>;tag=84670080
    To: <sip:lyncclient@baycollege.edu>;tag=c2a384b326;epid=794f213204
    CSeq: 37 BENOTIFY
    Call-ID: 5bba21a0f95941539e8b76000e1104ec
    Via: SIP/2.0/TLS LyncFE_IPAddr:5061;branch=z9hG4bK235BCA11.A1D5D0E9AA405DFF;branched=FALSE
    Authentication-Info: TLS-DSK qop="auth", opaque="D6E751AB", srand="37EFC18D", snum="114", rspauth="48a679024228c2910fd1ef19d3f14c535f2852e5", targetname="lyncFESrv.ADFQDN.edu", realm="SIP Communications Service", version=4
    Max-Forwards: 70
    Content-Length: 576
    Require: eventlist
    Content-Type: application/msrtc-event-categories+xml
    Event: presence
    subscription-state: active;expires=29837
    Message-Body: ----****MESSAGE BODY DELETED****----
    $$end_record

    It looks like there are four requests sent from OWA to Lync and then the Lync server sends out the disconnected notification to the Lync Client as I stopped the logging immediately after the Lync Client showed the owaclient as offline. Thanks for looking.

    Friday, April 27, 2012 1:15 PM
  • I just went through the logs , i couldn't find anything unusual. Presence subscription request and ackowlege is proper.

    Do you have session expiry or timeout set on LB or firewall device ?

    Thanks
    Saleesh


    If answer is helpful, please hit the green arrow on the left, or mark as answer.

    Friday, April 27, 2012 3:12 PM
  • Nope, we are inside of the firewall and the only thing on the LB is after 60m of inactivity to expire the client's entry in the sticky table.

    Friday, April 27, 2012 3:26 PM
  • This problem turned out to be related to a client timeout on the load balancer. We had the timeout set to 30 seconds and have now changed it to 60 minutes. We saw that after OWA was logged in and Lync IM was working in and out of OWA about 3-7 minutes later the load balancer would timeout a connection that the client did not respond to in a timely fashion. This timeout would occur several times (according to logs) and then the OWA user would show up as disconnected to the rest of the Lync clients even though everything looked fine in OWA.

    After changing this timeout value I have tested logging into OWA several times from a couple of computers and have not been disconnected yet. In fact my current test has been running for almost 1 hr 30 min. Still working with MS to determine why this timeout is breaking the OWA->Lync connection and why the OWA client isn't responding before the timeout occurs.

    • Marked as answer by Bay College Thursday, May 03, 2012 3:22 PM
    Thursday, May 03, 2012 3:22 PM