Always offline

Help
Drumbo
2014-02-12
2014-03-30
  • Drumbo

    Drumbo - 2014-02-12

    Hi,

    I currently use this plugin to connect to Reuters Messenger using Adium 1.5.9. Recently I upgraded my mac from SL to Mavericks and since then Adium always appears as offline to everybody - even tho I am online and can send messages. Once I have sent a message to someone - they can reply, in all other circumstances their clients simply say I am offline. If I login using my windows client (the native TR app), and then log back in to adium - I will appear as online for a while, but after a period (haven't figured out what that period is), adium will start using 150% of my CPU and I will again appear as offline to everyone.

    If anyone can help regarding this - it would be highly appreciated.

    Thanks

     
  • Drumbo

    Drumbo - 2014-02-14

    Anyone have any ideas?

     
  • KwikSilvr

    KwikSilvr - 2014-02-15

    Start adium in debug mode and get some logs, please?

     
  • Drumbo

    Drumbo - 2014-02-17

    Hi,

    Thanks for coming back to me. Attached is the log of me changing my status from available to away and back again. In both instances I always appear offline to colleagues.

     
  • Stefan Becker

    Stefan Becker - 2014-02-17

    Looks like your server does not understand SIPE's status update messages:

    MESSAGE START >>>>>>>>>> SIP - 2014-02-17T12:57:03.380435Z
    SERVICE sip:***USERNAME***@reuters.net SIP/2.0
    ...
    CSeq: 1 SERVICE
    User-Agent: Purple/2.10.7 Sipe/1.18.0 (macosx-x86_64; )
    Call-ID: 6152g88ACaF8CFiE5EBmB9D4t449Bb4C75xBEB0x
    Contact: <sip:***USERNAME***@reuters.net:55977;maddr=10.12.199.64;transport=tls>
    ;proxy=replace
    Content-Type: application/SOAP+xml
    ...
    MESSAGE START <<<<<<<<<< SIP - 2014-02-17T12:57:03.428508Z
    SIP/2.0 504 Server Time-out
    To: <sip:***USERNAME***@reuters.net>
    ...
    CSeq: 1 SERVICE
    Call-ID: 6152g88ACaF8CFiE5EBmB9D4t449Bb4C75xBEB0x
    ...
    Original-Error: Unknown service command s
    

    I guess SIPE is no longer compatible to Reuters Messaging. You'll need to downgrade to the SIPE version which you were using before upgrading to Mavericks.

     
  • Drumbo

    Drumbo - 2014-02-18

    Thanks for the update Stefan. Not sure why it is no longer compatible as it worked with SL (I dropbox my adium2.0 library folder (so plugins etc) for use across machines). When I updated to Mavericks - all I simply did as symlink the DB folder back to the library - so I would have expected it to work. Will try the older version

     
  • Sparhawk

    Sparhawk - 2014-03-10

    Well have exactly the same problem and downgrade didnt work :(
    I see everyone offline, but ppl see me, online.. even groupchat works etc.. any suggestions?

    Thanks

     
  • Sparhawk

    Sparhawk - 2014-03-17

    well no solution for this one?

     
  • Sparhawk

    Sparhawk - 2014-03-20

    oh and for me its not adium but pidgin

     
  • KwikSilvr

    KwikSilvr - 2014-03-29

    Sparhawk: you're describing a different issue than the original poster. Your debug log seems like it isnt go through autodiscovery correctly. Try putting in the correct email services URL manually in options

     
  • Stefan Becker

    Stefan Becker - 2014-03-29

    Sparhawk: yes, your problem is completely different and you shouldn't have used this thread at all. Your log shows that you have the same problem as discussed in [d21ebf11].

    Your Office 365 account has a contact list that has been migrated to UCS. UCS requires EWS to work, but the log shows that EWS autodiscover fails for your account (157.56.252.185:80 i.e. autodiscover-emeacentral.outlook.com:80 connects but doesn't answer your request). BTW: that also means that your calendar information isn't published, i.e. other Lync users won't see when you are busy.

    I can think of three reasons why EWS autodiscover isn't working:

    • your email address on that Office 365 account is different than your Office 365 account, i.e. it is not Ma...Ma...@nwt...,
    • your company Office 365 is broken, i.e. the EWS has not been set up for the nwt... domain, or
    • your network has some kind of blocking mechanism for plain HTTP connection (https:// connections obviously work fine or otherwise you wouldn't be able to connect to your account at all).
     

    Related

    Forums: d21ebf11


    Last edit: Stefan Becker 2014-03-30
    • Stefan Becker

      Stefan Becker - 2014-03-30

      All further discussions will happen in [d21ebf11].

       

      Related

      Forums: d21ebf11

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks