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.
Showing posts with label Lync. Show all posts
Showing posts with label Lync. Show all posts
Friday, 22 June 2018
Wednesday, 14 March 2012
Getting Pidgin and Microsoft Lync to work nicely.
In the Windows centric company that I work at we use Office Communicator. Therefore I use Pidgin and the SIPE/SIMPLE plugin to be able to communicate.
Recently, they've started changing the version of OC to the latest Lync version. All of a sudden, my Pidgin would fail logging in. I checked on a Windows system and I still couldn't use the Lync client so I figured things were in transition and I didn't bother too much with it.
However, someone came to ask me about it and when I tried the Window Lync client again, I suddenly was able to log in! I tried Pidgin again and it would tell me that I was using not the right version. So I started searching around. I found that: Microsoft allows administrators to block older version of OC from connecting to the server.
So I started searching a bit more and found that others had the same problem and were looking for a solution. I then stumbled upon a very useful link.
This page describes how to set the user-agent in Pidgin so that you could connect as a certain version of OC. However, when I tried the same version on the post, that version didn't seem to work. So I started searching for a newer version and I found it...
To get Pidgin to work use the following UserAgent:
UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
Tada! I'm able to chat again!
-P
Recently, they've started changing the version of OC to the latest Lync version. All of a sudden, my Pidgin would fail logging in. I checked on a Windows system and I still couldn't use the Lync client so I figured things were in transition and I didn't bother too much with it.
However, someone came to ask me about it and when I tried the Window Lync client again, I suddenly was able to log in! I tried Pidgin again and it would tell me that I was using not the right version. So I started searching around. I found that: Microsoft allows administrators to block older version of OC from connecting to the server.
So I started searching a bit more and found that others had the same problem and were looking for a solution. I then stumbled upon a very useful link.
This page describes how to set the user-agent in Pidgin so that you could connect as a certain version of OC. However, when I tried the same version on the post, that version didn't seem to work. So I started searching for a newer version and I found it...
To get Pidgin to work use the following UserAgent:
UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
Tada! I'm able to chat again!
-P
Subscribe to:
Posts (Atom)