locked
remote lync call fails calling internal lync phone RRS feed

  • Question

  • Heres the problem

    the remote user can call any regular phone, but when he dial a internal lync user it rings but doesnt ring the desk then goes to VM, the internal user can call the remote user but the remote user cannot hear the internal user. no error on the servers, I get these when the internal to remote call happens.

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

    RequestUri:   sip:nsaboonchi@kitchell.com;opaque=user:epid:JfgdrUpIOFGBh7CbY6kY2QAA;gruu

    From:         sip:bmoore@kitchell.com;tag=c66f04dddc

    To:           sip:nsaboonchi@kitchell.com;tag=80a504f61d

    Call-ID:      82ab7db5e4c34e25a82e33109a1ee9d7

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

    v=0

    o=- 0 0 IN IP4 10.1.3.3

    s=session

    c=IN IP4 10.1.3.3

    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:

    0  (null)

    (null):  52094; reason="Instant Messaging conversation terminated on user inactivity";OriginalPresenceState="3000";CurrentPresenceState="3000";MeInsideUser="Yes";ConversationInitiatedBy="14";SourceNetwork="2";RemotePartyCanDoIM="Yes"

    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.

    Saturday, May 5, 2012 3:56 AM

Answers

  • The problem turned out to be the edge servers internal certificate recreate this certificate and reapply via the topology certificate deployment wizard
    • Marked as answer by Bmoore85016 Saturday, May 5, 2012 10:46 PM
    Saturday, May 5, 2012 10:46 PM

All replies

  • It looks like a routing or firewall problem with your edge server. Mybe some ports are not open from external over the edge to the internal user.

    here is a good link

    http://ucken.blogspot.de/2011/07/configuring-lync-for-external-access.html

    and check the external access with this link

    https://www.testocsconnectivity.com/

    regards Holger Technical Specialist UC

    Saturday, May 5, 2012 10:04 AM
  • I have looked at those items and turned the FW off and I pass the tests. it appears to be something internal. everything looks ok tracing with the ocs logger

    I can connect a remote lync call to a remote lync call it works

    I can connect a internal lync call to a remote lync call but the remote call cannot here the internal caller

    I can connect a internal lync call to a internal lync call it works

    If I call from a remote lync call to an internal lync call the internal caller doesnt see the call.

    Saturday, May 5, 2012 4:09 PM
  • The problem turned out to be the edge servers internal certificate recreate this certificate and reapply via the topology certificate deployment wizard
    • Marked as answer by Bmoore85016 Saturday, May 5, 2012 10:46 PM
    Saturday, May 5, 2012 10:46 PM