locked
OCS R2 Communicator Error - ms-diagnostics: 1011;reason="Ms-Diagnostics header not provided by previous hop";source="OCSR2POOL";Domain="SIPDOMAIN";PeerServer="LCS2005POOL" RRS feed

  • Question

  • I recently deployed a test OCSR2 pool in my enviroment.  Along side a LCS2005 Pool as well as a OCSR1 pool.  We are of course migrating to a production R2 enviroment but I did find this error very odd.

    User sees the contact presence unknown.

    Event Viewer log of user on R2 Pool...

    _____________________________________________________________________________________________________________________________________________________

    A SIP request made by Communicator failed in an unexpected manner (status code 80ef025b). More information is contained in the following technical data:

    RequestUri: sip:R1USER@SIPDOMAIN

    From: sip:R2USER@SIPDOMAIN;tag=2632234ac3

    To: sip:R1USER@SIPDOMAIN;tag=def6da5533

    Call-ID: XXXX

    Content-type: application/sdp;call-type=im

    v=0

    o=- 0 0 IN IP4 x.x.x.x

    s=session

    c=IN IP4 x.x.x.x

    t=0 0

    m=message 5060 sip null

    a=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/x-ms-ink application/ms-imdn+xml text/x-msmsgsinvite

    Response Data:

    603 Decline

    ms-diagnostics: 1011;reason="Ms-Diagnostics header not provided by previous hop";source="OCS07R2Pool";Domain="SIPDOMAIN";PeerServer="LCS2005Pool"

     

    Resolution:

    If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.

    ______________________________________________________________________________________________________________________________________________________

    In my research I have only found the "Ms-Diagnostics header not provided by previous hop" during a public access edge server scenario.  This is all internal and we do not have access edge servers deployed. 

    According to (http://technet.microsoft.com/en-us/library/bb964037.aspx)

    1011

    AP receives an error response. In this scenario, we are unable to get more information about the error because it came from a federated partner. Since they will not return any details about the error, we cannot either. The most common error codes that this probably applies to are 404, 480, 481, and 504.

    404, 480, 481, 504

    Federated peer server


    Ms Header error 1011 is again on a Access Edge server. 

    How am I seeing this error on a local R2 Communicator client on the OCS2007R2 Pool trying to contact someone in the LCS2005 Pool?

    Tuesday, March 31, 2009 6:48 PM