Friday 22 June 2018

Pidgin Part 3 - Or how I learned to ha... dislike Lync

The company is migrating to MS Teams in the near future. This is actually great and seems to work with Linux quite well, even if there isn't an official client for Linux. If Microsoft were to actually make a full Teams client for Linux, that would be the first official application I'd be running on my Linux laptop.

That said, we haven't actually fully moved to Teams, and are actually still using Lync (while moving to Skype-for-Business i.e. Lync 2016) in the nearer future. I'm still on the old Lync server and now, for some reason, my Pidgin-Sipe client has stopped working.

I cannot seem to connect to the server and I haven't found out why yet.

Currently, when running Pidgin with the --debug flag I get the following.

(14:03:26) sipe: sipe_http_request_response_unauthorized: init context target 'HTTP/server.domain.com' token '<NULL>'
(14:03:26) sipe: sipe_http_request_response_unauthorized: authentication failed, throwing away context

Obviously, I'm not giving out the server name.

It's a different error than having an incorrect password, so I'm not sure what the problem is. (Yet.)

If anyone happens on this blog and has more input or an idea, please add it in the comments.