Sign up for Office 365
Learn more about Office 365
Currently, it seems like that we cannot add a Lync online account in Pidgin. Please understand that Pidgin is not developed by Microsoft and the information is limited for us. I will suggest using the Microsoft Lync 2010 Client to sign in Lync Online. You may download the Microsoft Lync Online for Enterprises Service Description.docx for more information.
K K, our Exchange admin, went straight to the core of the issue by asking about Pidgin; I'd like to back up a few steps and ask how he finds out this information:
1. What is our DOMAIN\user? For instance, if I am user janedoe, our company is Acme Manufacturing, and our OWA domain is at owa.acme.com, is our DOMAIN\user ACME\janedoe?
2. What is our server port? Example: exchange-pool1.mycompany.org:5061
3. What is our encryption type/protocol? SSL/TLS? TCP? UDP?
A detailed answer would be wonderful and we'd be very grateful; K K has many settings, but doesn't know what any of these particular settings are called in his admin panel.
Lync uses SIP right? Which other messengers are capable of using.....RIGHT?
How about you actually help your customers rather than just avoiding the questions and sending some worthless documents.
Pidgin and other 3rd party applications are not supported due to the proprietary coding that is used with Lync Online.
3rd party clients will not connect to Lync Online regardless of the settings you may try, because they do not contain the necessary proprietary coding.
Wow, thanks a ton for that very HELPFUL information.
Are there any plans to open up the proprietary code?
Why is MS locking people out from using a 3rd party chat utility? Everyone doing so knows that it wont be supported by MS, so it should be no hassle to you. Beside, MS's support is so bad we and every IT professional never call it because we get answers like the one you just provided.
Thanks for locking us into your Chat client, sure hope this has somehow strategicly placed you in a position to keep me buying Microsoft products.
This is just bad business on so many different levels its not funny.
1 out of 1 people found this post helpful.
Yes would like to get Pidgin working with Lync too. Try to get it working with SIPE http://sipe.sourceforge.net/ on Windows. Why? because Lync doesn't have spell checking.
Are there any plans to enable support for 3rd party clients that wish to connect to Lync Online? The lack of interoperability is quite unfortunate.
Microsoft's style indicates that they won't open to 3rd party. Can you ask apple to open iMessage to 3rd party?
You can acess Lync through web instead of client.
There are risks to open the protocol to other clients
Unfortunately the Lync Web App seems to have the same restrictions as the full client. The list of supported platforms is uninspiring. Personally, I think it would be great if the industry as a whole embraced interoperability as a Good Thing. I'm hoping that if enough people ask for it, Microsoft will open up the protocol.
Currently, there are several Lync clients which are developed for different platforms, such as Lync 2010 for Windows, Lync Web App, Lync for Mac and Lync Mobile.
At this point, you can submit your feedback about connecting Lync to third party clients to Microsoft via the link: http://mymfe.microsoft.com/Microsoft%20%20Online%20%20Services/Feedback.aspx?formID=210.
Microsoft Product Team will take all suggestions and feedback into consideration for future releases. Thank you for your understanding.
Pidgin now has semi-experimental support for connecting to Office 365. You will need Pidgin v2.10.1 or greater as well as the SIPE plugin v1.13.0 or greater. There is an FAQ for the SIPE plugin listing the required configuration settings and solutions to common issues. Good luck everyone!
P.S. if pool1.oconline.microsoftonline.com:443 does not work for you, try sipdir.online.lync.com:443
3 out of 3 people found this post helpful.
Thanks Chris. This worked perfectly.
may i please know how you got pidgin working?
i have tried to follow the one on FAQ, but when i login i get "Read Error"
i have pidgin 2.10.3 and pidgin-sipe 1.13.1
i have tried the following;
Auth Scheme: TLS-DSK
UCCAPI/4.0.7577.314 OC/4.0.7577.314 (Microsoft Lync 2010)
UCCAPI/4.0.7577.256 OC/4.0.7577.280 (Microsoft Lync 2010)
and i have also set this:
$ printenv | grep NSS
Thanks, finally I have an alternative that works.. The window blinking in lync was to much for me..
Last reply directed at Chris. Thanks again :)
This morning, I was trying to connect to Lync 2010 with Pidgin 2.10.6 and pidgin-sipe 1.14.1 (nsis-no-sspi). I'm using Windows 7.
I managed to finally get things working, after almost pulling my hair out, using the following configuration.
In Pidgin, add an Office Communicator account.
In Modify Account, the Basic tab:
Protocol: Office Communicator
Local alias: <my first name, or whatever you want>
In the Advanced tab:
Connection type: Auto
User Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010)
Authentication scheme: TLS-DSK
Leave everything else blank. There should not be a "single sign on" option present.
In the Proxy tab:
Proxy type: User Global Proxy Settings
With these settings in Pidgin, I was able to connect to Lync successfully through Pidgin 2.10.6, after installing the "pidgin-sipe-1.14.1-pidgin-2.10.6-win32-nsis-sspi.exe" executable, which I downloaded from sourceforge.net/.../sipe.
Hopefully this saves at least one poor soul a headache or two.
2 out of 2 people found this post helpful.
I have tried your exact settings as well as the settings for the previous person in this thread who reported it working. I even installed older pidgin and sipe versions to test with your exact versions. Still, I am getting the same error. The pidgin GUI says "Web ticket request to webdir0e-ext.online.lync.com/.../CertProvisioningService.svc failed" while the XML in the response from the server says: "The SIP URI in the claim type requirements of the web ticket request does not match the SIP URI associated with the presented credentials.".
Has anyone got this same error message and solved it?
Thank you Akatz! Your configuration works great with Pidgin 2.10.6 (libpurple 2.10.6), Pidgin SIPE Version: 1.13.1-2 and Office365 (Office2010) on Linux Mint KDE x64
Works like a charm!!!! Thanks a ton
Easy enough for an IT person, though I would not recommend for non-technical users. I only do this as I need to use multiple Lync logons.
1) Install Pidgen (I use adium on Mac)
2) install SIPE plugin (sourceforge.net/.../sipe)
3) In credentials use UPN email@example.com (not domain\username). Easily confused with email address - I recommend making sure you keep both the same
4) Under options, change authentication scheme to 'TLS-DSK'
5) change user agent to "UCCAPI/15.0.4481.1000 OC/15.0.4481.1000 (Microsoft Lync)" (assuming your tenant has been upgraded to Wave15 (aka Exchange 2013). This makes O365 think you are connecting with a Lync 2013 client.
No need to put in server details due to Lync auto-discover so long as you have correctly configured DNS settings for Office365 (details can be found in O365 Admin \ Domains). For those of you unlucky enough to be using DNS provider such as 1&1 where DNS SRV and TXT records can't be created, use server name of sipdir.online.lync.com
HOWEVER: I do not recommend primary Lync usage via the none-native full / web clients as you will be restricted you IM chat only (no audio, video and desktop sharing), and an contacts / groups you have will have to be maintained manually in Pidgen. In my case I use Lync for primary account and Adium for secondary.