locked
OCS to OCS R2 communication RRS feed

  • Question

  • I have a test OCS R2 up and running an when I move my account to it, no one on our OCS (RTM) implementation can intiate a conversation with me. I can initiate with them though. In addition, 2 OCS R2 users can't communicate with each other. Below are the validation results of an OCS->OCS R2 user.

    I have run the BPA and ensured all needed updates are on the OCS implementation.

    The OCS 2007 user is using OC  2.0.6362.0
    Th OCS R2 users are using 3.5.6907.0

    Seems I had the same issue back in LCS/OCS migration but some OCS updates fixed it. I am at a loss on this one. Any ideas?


    Maximum hops: 3
    Received a failure SIP response: User sip:ocsr2user@domain.com @ Server ocs.domain
    Received a failure SIP response: [
    SIP/2.0 500 The server encountered an unexpected internal error
    FROM: "OCS User"<sip:ocsuser@domain.com>;tag=7c96b8c169f3ce1cb2a;epid=epid11
    TO: <sip:ocsr2user@domin.com>;tag=C6031A13808AB1E3B8D54693B00F2880
    CSEQ: 12 INVITE
    CALL-ID: 7f3684b1df4b426b801024e9ec6132a6
    VIA: SIP/2.0/TLS 192.168.120.33:55670;branch=z9hG4bKa0340c5;ms-received-port=55670;ms-received-cid=11700
    CONTENT-LENGTH: 0
    AUTHENTICATION-INFO: NTLM rspauth="0100000001000000A4CEFC1C5F86DE23", srand="A1675E60", snum="7", opaque="61908B1C", qop="auth", targetname="ocs.domain", realm="SIP Communications Service"
    ms-diagnostics: 1;reason="Service Unavailable";source="ocsr2.domain";AppUri="http://www.microsoft.com/LCS/ApiModule";reason="The application specified an invalid static forwarding url"

    ]

    Suggested Resolution: Use the maximum hop count to determine the server that generated this error. For example, if the maximum hop value is 2, then it is likely that this error was generated by a server that is 1 (immediate target) or 2 hops away. Check whether the target user is a valid user and that the target user domain is trusted by the source user's pool. Check the connectivity between the source and target pools.
    Attempting to establish SIP dialog: Processing failed as one or more steps did not complete successfully
     

    Wednesday, February 11, 2009 11:33 PM