locked
Some Federated contacts drop IM RRS feed

  • Question

  • I am federated with several companies, including Microsoft. MS works great. Two of my federated partners are having trouble with IMs. I'll focus on one of them.

    Presence seems to work most of the time. When an IM call is started the IM comes through (inbound to me) and the chat window opens with the message. When they reply, there is a delay. I can send messages until their side produces a 504 error on the chat window. Once that comes up, I can no longer send messages.

    Here is the main message from the debug on my Edge...

    Start-Line: SIP/2.0 481 Call Leg/Transaction Does Not Exist

    This is the debug from their Edge...

    Start-Line: SIP/2.0 504 Server time-out

    ms-diagnostics: 1007;reason="Temporarily cannot route";source="ocs01.company.com";ErrorType="Connect Attempt Failure";WinsockFailureDescription="The peer did not respond to the connection attempt";WinsockFailureCode="274C(WSAETIMEDOUT)";Peer="ocs02.company.com"

     

    ocs1 is the front-end

    ocs2 is the edge

    Friday, February 1, 2008 5:50 AM

All replies

  • I have the same issue over here, exact the same error message.


    Did you already find a solution?

    Thursday, February 28, 2008 2:15 PM
  • Up

     

    I have the same error

     

    Monday, September 15, 2008 1:32 PM
  •  

    I have the same issue just opposite direction.

    We arr running OCS 2007 and trying to get Federation with LCS 2005 SP1 to work(other organization).

    Have no problem federating with other OCS environments.

     

    Any ideas will be greatly appreciated.

     

     

    Thanks

    Miro

    Tuesday, September 30, 2008 11:58 PM
  • If this is the only federated system you are having problems with then it's safe to say the problem is on their end, and since it works initially then their configuration is probably OK as it sounds like network connectivity issues.

    Thursday, October 2, 2008 1:25 PM
    Moderator
  •  

     

     

    I’m having the same problem.

     

    From my company’s domain i can federate with MS and some of my other partners plus pim. And it all works fine. From now on called A

    But from this one partner i cannot get federation to work. and do get some error messages in the logging tools.

    From now on called B

     

    But it works partially.

    Presence: users in B can see presence of users in A but not the other way around (or actually it works like every 15 min for 2 minutes until I try to send a im.)

    Users in A can see presence of all other federated users in the other companies

     

    IM: user in B can send to user in A but not the other way around.

    Users in A can send to all other federated contacts.

     

     

     

    Error message in company B edge server

    TL_INFO(TF_PROTOCOL) [2]0988.0F6C::11/19/2008-14:52:22.203.000016d7 (SIPStack,SIPAdminLog::TraceProtocolRecord:1224.idx(122))$$begin_record

    Instance-Id: 00000329

    Direction: outgoing;source="external edge";destination="internal edge"

    Peer: directorserver.b.local:3036

    Message-Type: response

    Start-Line: SIP/2.0 481 Call Leg/Transaction Does Not Exist

    From: "Tommy Clarke"<sip:tclarke_ext@B.com>;tag=0625d1ff20;epid=31b2eff54a

    To: "" <sip:tommy.clarke@A.se>;epid=45dfa31162;tag=68129290f7

    CSeq: 3 INFO

    Call-ID: 1cb4589d42b241d3a69e644c84c06c74

    ms-edge-proxy-message-trust: ms-source-type=AutoFederation;ms-ep-fqdn=edgeserver;ms-source-verified-user=verified;ms-source-network=federation (note that the edge server is not in its FQDN here its servername)

    Via: SIP/2.0/TLS 10.159.18.60:3036;branch=z9hG4bK4606EF75.92FF92A0;branched=FALSE;ms-received-port=3036;ms-received-cid=39600

    Via: SIP/2.0/TLS 10.159.18.104:4841;branch=z9hG4bK10E0303F.51C13811;branched=FALSE;ms-received-port=4841;ms-received-cid=64B00

    Via: SIP/2.0/TLS 10.159.18.101:2393;ms-received-port=2393;ms-received-cid=459800

    User-Agent: UCCP/2.0.6362.97 OC/2.0.6362.97 (Microsoft Office Communicator)

    Content-Length: 0

    ms-diagnostics: 1011;reason="Ms-Diagnostics header not provided by previous hop";source="sip.externalB.com";Domain="externalA.se";PeerServer="edge.externalA.se"

    Message-Body:

     

     

    Error message from company A edge server

     

    TL_INFO(TF_PROTOCOL) [0]070C.0E88::11/19/2008-15:02:12.497.0000b76d (SIPStack,SIPAdminLog::TraceProtocolRecord:1224.idx(122))$$begin_record

    Instance-Id: 0005D1EC

    Direction: incoming;source="internal edge";destination="external edge"

    Peer: internalocs.A.local:5061

    Message-Type: response

    Start-Line: SIP/2.0 481 Call Leg/Transaction Does Not Exist

    From: "Tommy Clarke"<sip:tclarke_ext@B.com>;tag=3cd3028fd6;epid=31b2eff54a

    To: "" <sip:tommy.clarke@A.se>;epid=45dfa31162;tag=95a9099866

    CSeq: 3 INFO

    Call-ID: e0db809e4eb7462e8039429a374d6ffd

    Via: SIP/2.0/TLS 192.168.130.9:1361;branch=z9hG4bK2D0D15D6.163D22A0;branched=FALSE;ms-received-port=1361;ms-received-cid=1A8300

    Via: SIP/2.0/TLS 217.151.205.116:2602;branch=z9hG4bK612CAAE0.13C8F26A;branched=FALSE;ms-internal-info="baoa1yEEQ6oqVAhbxt4o6pTC9xLjUTyPJqBWPFLwAA";ms-received-port=2602;ms-received-cid=3F5A00

    Via: SIP/2.0/TLS 10.159.18.60:3036;branch=z9hG4bKD1FFEBE4.F2E52E7C;branched=FALSE;ms-received-port=3036;ms-received-cid=39600

    Via: SIP/2.0/TLS 10.159.18.104:4841;branch=z9hG4bK9D55A015.BD7A51AE;branched=FALSE;ms-received-port=4841;ms-received-cid=64B00

    Via: SIP/2.0/TLS 10.159.18.101:2393;ms-received-port=2393;ms-received-cid=459800

    User-Agent: UCCP/2.0.6362.97 OC/2.0.6362.97 (Microsoft Office Communicator)

    Content-Length: 0

    ms-diagnostics: 1011;reason="Ms-Diagnostics header not provided by previous hop";source="internalocs.A.local";Domain="externalA.se";PeerServer=""

    Message-Body:

    $$end_record

     

    Wednesday, November 19, 2008 3:34 PM
  •  

    it appears we are missing a lot here.  Is there is any way to get a more detailed log.  Show just the Call Leg failure - dosent help much.  There is usually something leading up to that.  Routing Errors, TLS Errors, Via headers incorrect.

     

    --geoff

    Wednesday, November 26, 2008 1:28 AM
  • I located my problem to a missconfigured DNS server. And that was why traffic was only going oneway.

    Wednesday, November 26, 2008 10:42 AM
  • What was your DNS issue?  We are having the same issue trying to federate with Microsoft (pretty sure that it is on our end on that one) and are getting the same 481 error.  Similar but not quite the same behavior.
    Wednesday, December 17, 2008 9:40 PM
  • I know this is a pretty old post but I am experiencing the exact same issue here, however any existing federation contacts I had setup through Microsoft, AIM and other vendors work just fine.

    Any input on those DNS fixes?

    Thanks.
    Tuesday, March 3, 2009 11:36 PM
  • We are still having the issue as well.  Any more info on the DNS issues?
    Thursday, April 30, 2009 7:36 PM