Weird federation issue RRS feed

  • Question

  • I have just finish setting a full deployment of OCS R2 environnement.

    Everything works great.
    We have federated with Microsoft and it also works great.

    Now, my problem is that I am unable to federate with any other OCS organization...beside Microsoft.

    The weird thing, is that the other OCS company are also federated with Microsoft....so federation works...but not within each other.

    To recap:

    Company A : OCS R2
    Company B :OCS R2
    Company C: OCS

    A and B are federated
    B and C are federated
    But A and C are not able to federate??

    Both A and C are Open for federation and are using Public Certificate.

    Thanks for any light on this one.



    Friday, March 20, 2009 8:34 PM


All replies

  • My guess would be certificate issues
    A or C EDGE may not have correct root Certs installed
    You can run a debug session when adding a federated contact
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Sunday, March 22, 2009 10:17 PM
  • Thanks for your reply

    Could be a cert issue, but here is a snip of a debug session.

    Company A = cnww.com     is using UC Entrust Public Certificate
    Company C = Alphamosaik.com    is using  UC Digicert Public Certificate

    Thanks for your help

    TL_INFO(TF_PROTOCOL) [0]0DD8.0294::03/23/2009-01:18:55.629.000020ba (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
    Instance-Id: 00002A5F
    Direction: outgoing
    Peer: MTL-WW-IIS02.companyA.com:50880
    Message-Type: response
    Start-Line: SIP/2.0 504 Server time-out
    From: "Jean-Philippe Breton"<sip:Jean-Philippe.Breton@companyA.com>;epid=97253C84C2;tag=45ecabc82d
    To: <sip:dany.bolduc@companyC.com>;tag=2E198B77AC05E7EC8C5B2E66C1652E3F
    CSeq: 65 SUBSCRIBE
    Call-ID: 0293a2e3a0254629b9d6f08338d2d255
    ms-edge-proxy-message-trust: ms-source-type=EdgeProxyGenerated;ms-ep-fqdn=mtl-ww-edgeim01.companyA.com;ms-source-verified-user=verified;ms-source-network=federation
    Via: SIP/2.0/TLS;branch=z9hG4bK9416a5c3;ms-received-port=50880;ms-received-cid=41900
    ms-diagnostics: 1007;reason="Temporarily cannot route";source="sip.companyA.com";ErrorType="Failure reading or writing data on connection";WinsockFailureDescription="The peer forced closure of the connection";WinsockFailureCode="10054(WSAECONNRESET)";Peer="ocsfed.companyC.com"
    Content-Length: 0
    Message-Body: –

    Monday, March 23, 2009 1:35 AM
  • Problem solved.

    I asked company C to update their Root TRusted Autorities.

    Entrust has changed their Root Authority.



    • Marked as answer by JP BretonMVP Monday, March 23, 2009 10:49 PM
    Monday, March 23, 2009 10:49 PM