Buddies disappeared at every shutdown

Help
Moonjara
2014-01-31
2014-02-05
  • Moonjara
    Moonjara
    2014-01-31

    Hi,

    I'm on Debian Linux 3.2. I used pidgin on my computer for quite a long time now. Recently I went on Windows to use Lync for a meeting. Since that moment my list of buddies went empty at every shutdown of Pidgin... My buddies can still see me and I can talk with them but I don't see them, my list is completly empty.

    I installed Sipe 1.18 and it doesn't change anything... Does anyone have an idea to help me?

    Thanks for your help.
    It's a great tool!

    Moon

     
    • Stefan Becker
      Stefan Becker
      2014-01-31

      My guess is that your company uses Lync 2013. The Windows client triggered moving of your contact list from the old location to UCS, which is a new feature in Lync 2013. SIPE supports UCS in newer versions.

      BTW: is your email address different from your Lync account name? If yes, then your system probably doesn't have EWS autodiscovery redirect configured and therefore you'll have to set your email by hand in the advanced tab. If Exchange calendar integration has never worked for you with SIPE, then this is the root cause for that too.

      Without the --debug log I can't tell why it doesn't work in your case. To shorten it I would suggest to let Pidgin run without any other accounts online for about 5 minutes. Don't start any IMs during that time. And please make sure to mask any passwords you see in the log.

      Please don't copy & paste the log. Either use the attachment feature or provide a link to a pastebin page.

       
  • KwikSilvr
    KwikSilvr
    2014-01-31

    Start pidgin with --debug and capture the logs to a file. You will probably want to replace names, domains and password to protect the innocent ;-)

    It's covered in the FAQ

     
  • Moonjara
    Moonjara
    2014-02-03

    @Stefan : Sorry I didn't see your post.

    Here is my debug file.

    I can't figure out how to configure my pidgin to connect. A friend uses pidgin too but everything works fine for him..

    Thanks for your help.

     
    Attachments
    • Stefan Becker
      Stefan Becker
      2014-02-03

      You have set up your Pidgin to use a proxy and that seems to cause the EWS autodiscover in SIPE to fail:

      (11:36:34) sipe: sipe_ews_autodiscover_url: trying 'https://Autodiscover.domain.com/Autodiscover/Autodiscover.xml'
      ...
      (11:36:34) proxy: Attempting connection to 10.69.0.1
      (11:36:34) proxy: Connecting to autodiscover.domain.com:443 via 10.69.0.1:3128 using HTTP
      ...
      (11:36:34) proxy: Connection attempt failed: Erreur de connexion au proxy HTTP 504.
      ...
      (11:36:34) sipe: sipe_ews_autodiscover_url: trying 'http://Autodiscover.domain.com/Autodiscover/Autodiscover.xml'
      ...
      (11:36:34) proxy: Connecting to autodiscover.domain.com:80 via 10.69.0.1:3128 using HTTP
      ...
      MESSAGE START <<<<<<<<<< HTTP - 2014-02-03T10:36:34.555837Z
      HTTP/1.0 400 Bad Request
      ...
      (11:36:34) sipe: sipe_ews_autodiscover_url: trying 'https://domain.com/Autodiscover/Autodiscover.xml'
      ...
      (11:36:34) proxy: Attempting connection to 10.69.0.1
      (11:36:34) proxy: Connecting to domain.com:443 via 10.69.0.1:3128 using HTTP
      ...
      (11:36:37) proxy: Connection attempt failed: Erreur de connexion au proxy HTTP 504.
      ...
      (11:36:37) sipe: sipe_ews_autodiscover_request: no more methods to try!
      

      Please go to the account settings for the SIPE account, switch to the Proxy tab and select No Proxy as proxy type. Or switch Proxy off completely in Pidgin.

       
    • Stefan Becker
      Stefan Becker
      2014-02-03

      If you still see the same failure in the log after switching off the proxy, then EWS autodiscover for your installation is broken/not configured. Then you will have to enter the address of the EWS server, i.e. most likely your email server, in the SIPE account settings.

      Guessing from the log, your account is a BPOS or Office365 account, so I would be surprised that EWS autodiscover isn't configured.

       
      Last edit: Stefan Becker 2014-02-03
      • Moonjara
        Moonjara
        2014-02-05

        I switched off the proxy, but it doesn't change. I tried several things but I can't see how to let it in auto discover mode.
        My email is on Office365 and I use the same address to connect on Pidgin, maybe it can help. Can you precise me how to set up the advanced config tab to let it autodiscover and find everything.

        At the moment the config is :
        Server : sipdir.online.lync.com:443
        Connection Type : Auto
        User Agent : UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
        Authentification Scheme : TLS-DSK

        I did another debug.log without proxy.

        Thanks for your help

         
        Attachments
        • Stefan Becker
          Stefan Becker
          2014-02-05

          EWS autodiscover actually works correctly now:

          (20:11:01) sipe: sipe_ews_autodiscover_parse: as_url = 'https://outlook.office365.com/EWS/Exchange.asmx'
          (20:11:01) sipe: sipe_ews_autodiscover_parse: ews_url = 'https://outlook.office365.com/EWS/Exchange.asmx'
          (20:11:01) sipe: sipe_ews_autodiscover_parse: oab_url = 'https://outlook.office365.com/OAB/3cfbe8f8-575d-463a-9410-4c002f5f8281/'
          (20:11:01) sipe: sipe_ews_autodiscover_parse: oof_url = 'https://outlook.office365.com/EWS/Exchange.asmx'
          (20:11:01) sipe: ucs_ews_autodiscover_cb: EWS URL 'https://outlook.office365.com/EWS/Exchange.asmx'
          

          but your buddy list is just empty :-)

          MESSAGE START <<<<<<<<<< HTTP - 2014-02-05T19:11:08.821044Z
          HTTP/1.1 200 OK
          ...
          <?xml version="1.0" encoding="utf-8"?>
          ...
           <GetImItemListResponse ResponseClass="Success" ...
            <Personas xmlns="..."/>
           ...
           </GetImItemListResponse>
          

          I can only assume that the transfer from the old place to UCS got aborted and therefore the transfer was incomplete.

          Just go ahead and re-add your buddies with SIPE...