OCS Front End Validation Failed RRS feed

  • Question

  • Hi All,
    I have deployed OCS 2007 SE edition with one Edge server and whenever I run the Validation tool on Front End or Edge Server, I got following error:

    Attempting to establish SIP dialog from user1@domain.com to user2@domain.com using ocs.domain.com   Maximum hops: 3
    Received a failure SIP response: User sip:user2@domain.com @ Server ocs.domain.com
    Received a failure SIP response: [
    SIP/2.0 500 The server encountered an unexpected internal error
    FROM: "User1"<sip:user1@domain.com>;tag=45ea582e5deea28f776f;epid=epid01
    TO: <sip:user2@domain.com>;epid=epid11;tag=47136F9B2F3B7AFF87619B0BE64E196A
    CALL-ID: b48a40784e4342a787bdc72582f64304
    VIA: SIP/2.0/TLS;branch=z9hG4bKca17aac;ms-received-port=3567;ms-received-cid=5D00
    AUTHENTICATION-INFO: NTLM rspauth="0100000000000000A6F0DC785D141815", srand="A84B120E", snum="3", opaque="F08D2391", qop="auth", targetname="ocs.domain.com", realm="SIP Communications Service"
    ms-diagnostics: 1;reason="Service Unavailable";source="ocs.doamin.com";ErrorType="Security association encoded into the route set has not yet been fully established";HRESULT="C3E93C2F(SIPPROXY_E_UNKNOWN_USER_OR_EPID)"


    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

    Very very thanks in advance for any help.

    Thursday, October 23, 2008 12:22 PM

All replies

  • Do you have the certificate configured on the OCS Server?

    R. Kinker
    MCSE 2003 (Messaging), MCTS - LCS 2005, MCTS - OCS 2007

    Friday, October 24, 2008 8:29 AM
  • Yes,
    I have configured Windows CA certificates on OCS Front End and Edge  Server internal interface. I have also configured comodo certificates on Access Edge and Web Conferencing public interface.

    Communicator is working find from internal as well as external and people able to do 1-1 and Conf. This error is coming on Front End as well as Edge validation tool.

    Ankit Singhal
    Friday, October 24, 2008 9:14 AM
  • targetname="ocs.domain.com", realm="SIP Communications Service"
    ms-diagnostics: 1;reason="Service Unavailable";source="ocs.doamin.com";


    Unless this was a mistake in the post, if you are using a lab with the actual name of domain.com then you might have a typo somewhere in your OCS configuration.

    Friday, October 24, 2008 11:02 PM
  • Sorry Jeff,
    This was a typo in the post. Actual domain name is some thing else.
    Thursday, October 30, 2008 5:02 AM